make doc-build-all does not work

The README says to run make doc-build-all. I consistently get an error about a missing settings64.sh file.
make doc-build DOC=pb;  make doc-build DOC=ug;
make[1]: Entering directory '/home/dbrumley/git/github/iobundle/iob-cache'
make fpga-build FPGA_FAMILY=CYCLONEV-GT;  make fpga-build FPGA_FAMILY=XCKU;
make[2]: Entering directory '/home/dbrumley/git/github/iobundle/iob-cache'
make -C ./hardware/fpga/quartus/CYCLONEV-GT build
make[3]: Entering directory '/home/dbrumley/git/github/iobundle/iob-cache/hardware/fpga/quartus/CYCLONEV-GT'
../build.sh "iob_cache" "../../../../submodules/INTERCON/hardware/src/merge.v ../../../../submodules/INTERCON/hardware/src/split.v ../../../../submodules/MEM/hardware/regfile/sp_reg_file/iob_sp_reg_file.v ../../../../submodules/MEM/hardware/ram/2p_ram/iob_2p_ram.v ../../../../submodules/MEM/hardware/fifo/bin_counter.v ../../../../submodules/MEM/hardware/fifo/sfifo/iob_sync_fifo.v ../../../../submodules/MEM/hardware/ram/sp_ram/iob_sp_ram.v ../../../../hardware/src/back-end-axi.v ../../../../hardware/src/back-end-native.v ../../../../hardware/src/cache-control.v ../../../../hardware/src/cache-memory.v ../../../../hardware/src/front-end.v ../../../../hardware/src/iob-cache-axi.v ../../../../hardware/src/iob-cache.v ../../../../hardware/src/onehot-to-bin-encoder.v ../../../../hardware/src/read-channel-axi.v ../../../../hardware/src/read-channel-native.v ../../../../hardware/src/replacement-policy.v ../../../../hardware/src/write-channel-axi.v ../../../../hardware/src/write-channel-native.v" "../../../../submodules/INTERCON/hardware/include ../../../../hardware/include" "DUMMY" "5CGTFD9E5F35C7"
../build.sh: line 5: /nios2eds/nios2_command_shell.sh: No such file or directory
make[3]: *** [../../fpga.mk:15: iob_cache_0.qxp] Error 127
make[3]: Leaving directory '/home/dbrumley/git/github/iobundle/iob-cache/hardware/fpga/quartus/CYCLONEV-GT'
make[2]: *** [Makefile:28: fpga-build] Error 2
make[2]: Leaving directory '/home/dbrumley/git/github/iobundle/iob-cache'
make[2]: Entering directory '/home/dbrumley/git/github/iobundle/iob-cache'
make -C ./hardware/fpga/vivado/XCKU build
make[3]: Entering directory '/home/dbrumley/git/github/iobundle/iob-cache/hardware/fpga/vivado/XCKU'
../build.sh "iob_cache" "../../../../submodules/INTERCON/hardware/src/merge.v ../../../../submodules/INTERCON/hardware/src/split.v ../../../../submodules/MEM/hardware/regfile/sp_reg_file/iob_sp_reg_file.v ../../../../submodules/MEM/hardware/ram/2p_ram/iob_2p_ram.v ../../../../submodules/MEM/hardware/fifo/bin_counter.v ../../../../submodules/MEM/hardware/fifo/sfifo/iob_sync_fifo.v ../../../../submodules/MEM/hardware/ram/sp_ram/iob_sp_ram.v ../../../../hardware/src/back-end-axi.v ../../../../hardware/src/back-end-native.v ../../../../hardware/src/cache-control.v ../../../../hardware/src/cache-memory.v ../../../../hardware/src/front-end.v ../../../../hardware/src/iob-cache-axi.v ../../../../hardware/src/iob-cache.v ../../../../hardware/src/onehot-to-bin-encoder.v ../../../../hardware/src/read-channel-axi.v ../../../../hardware/src/read-channel-native.v ../../../../hardware/src/replacement-policy.v ../../../../hardware/src/write-channel-axi.v ../../../../hardware/src/write-channel-native.v" "../../../../submodules/INTERCON/hardware/include ../../../../hardware/include" "DUMMY" "xcku040-fbva676-1-c"
../build.sh: line 3: /settings64.sh: No such file or directory
make[3]: *** [../../fpga.mk:15: iob_cache.edif] Error 1
make[3]: Leaving directory '/home/dbrumley/git/github/iobundle/iob-cache/hardware/fpga/vivado/XCKU'
make[2]: *** [Makefile:28: fpga-build] Error 2
make[2]: Leaving directory '/home/dbrumley/git/github/iobundle/iob-cache'
make[1]: *** [Makefile:31: fpga-build-all] Error 2
make[1]: Leaving directory '/home/dbrumley/git/github/iobundle/iob-cache'
make[1]: Entering directory '/home/dbrumley/git/github/iobundle/iob-cache'
make fpga-build FPGA_FAMILY=CYCLONEV-GT;  make fpga-build FPGA_FAMILY=XCKU;
make[2]: Entering directory '/home/dbrumley/git/github/iobundle/iob-cache'
make -C ./hardware/fpga/quartus/CYCLONEV-GT build
make[3]: Entering directory '/home/dbrumley/git/github/iobundle/iob-cache/hardware/fpga/quartus/CYCLONEV-GT'
../build.sh "iob_cache" "../../../../submodules/INTERCON/hardware/src/merge.v ../../../../submodules/INTERCON/hardware/src/split.v ../../../../submodules/MEM/hardware/regfile/sp_reg_file/iob_sp_reg_file.v ../../../../submodules/MEM/hardware/ram/2p_ram/iob_2p_ram.v ../../../../submodules/MEM/hardware/fifo/bin_counter.v ../../../../submodules/MEM/hardware/fifo/sfifo/iob_sync_fifo.v ../../../../submodules/MEM/hardware/ram/sp_ram/iob_sp_ram.v ../../../../hardware/src/back-end-axi.v ../../../../hardware/src/back-end-native.v ../../../../hardware/src/cache-control.v ../../../../hardware/src/cache-memory.v ../../../../hardware/src/front-end.v ../../../../hardware/src/iob-cache-axi.v ../../../../hardware/src/iob-cache.v ../../../../hardware/src/onehot-to-bin-encoder.v ../../../../hardware/src/read-channel-axi.v ../../../../hardware/src/read-channel-native.v ../../../../hardware/src/replacement-policy.v ../../../../hardware/src/write-channel-axi.v ../../../../hardware/src/write-channel-native.v" "../../../../submodules/INTERCON/hardware/include ../../../../hardware/include" "DUMMY" "5CGTFD9E5F35C7"
../build.sh: line 5: /nios2eds/nios2_command_shell.sh: No such file or directory
make[3]: *** [../../fpga.mk:15: iob_cache_0.qxp] Error 127
make[3]: Leaving directory '/home/dbrumley/git/github/iobundle/iob-cache/hardware/fpga/quartus/CYCLONEV-GT'
make[2]: *** [Makefile:28: fpga-build] Error 2
make[2]: Leaving directory '/home/dbrumley/git/github/iobundle/iob-cache'
make[2]: Entering directory '/home/dbrumley/git/github/iobundle/iob-cache'
make -C ./hardware/fpga/vivado/XCKU build
make[3]: Entering directory '/home/dbrumley/git/github/iobundle/iob-cache/hardware/fpga/vivado/XCKU'
../build.sh "iob_cache" "../../../../submodules/INTERCON/hardware/src/merge.v ../../../../submodules/INTERCON/hardware/src/split.v ../../../../submodules/MEM/hardware/regfile/sp_reg_file/iob_sp_reg_file.v ../../../../submodules/MEM/hardware/ram/2p_ram/iob_2p_ram.v ../../../../submodules/MEM/hardware/fifo/bin_counter.v ../../../../submodules/MEM/hardware/fifo/sfifo/iob_sync_fifo.v ../../../../submodules/MEM/hardware/ram/sp_ram/iob_sp_ram.v ../../../../hardware/src/back-end-axi.v ../../../../hardware/src/back-end-native.v ../../../../hardware/src/cache-control.v ../../../../hardware/src/cache-memory.v ../../../../hardware/src/front-end.v ../../../../hardware/src/iob-cache-axi.v ../../../../hardware/src/iob-cache.v ../../../../hardware/src/onehot-to-bin-encoder.v ../../../../hardware/src/read-channel-axi.v ../../../../hardware/src/read-channel-native.v ../../../../hardware/src/replacement-policy.v ../../../../hardware/src/write-channel-axi.v ../../../../hardware/src/write-channel-native.v" "../../../../submodules/INTERCON/hardware/include ../../../../hardware/include" "DUMMY" "xcku040-fbva676-1-c"
../build.sh: line 3: /settings64.sh: No such file or directory
make[3]: *** [../../fpga.mk:15: iob_cache.edif] Error 1
make[3]: Leaving directory '/home/dbrumley/git/github/iobundle/iob-cache/hardware/fpga/vivado/XCKU'
make[2]: *** [Makefile:28: fpga-build] Error 2
make[2]: Leaving directory '/home/dbrumley/git/github/iobundle/iob-cache'
make[1]: *** [Makefile:31: fpga-build-all] Error 2
make[1]: Leaving directory '/home/dbrumley/git/github/iobundle/iob-cache'
make: *** [Makefile:51: doc-build-all] Error 2

rdata is a front-end (facing the CPU) signal, meaning the CPU receives data from the cache using it.
wdata is another front-end for writing to the cache.
The CPU is either reading or writing, not both.
For reading one word from the cache, have the address ready and assert valid during one cycle.
If the ready signal is high in the next cycle, rdata has the requested word; you may immediately (combinatorially) de-assert the valid signal if you do not need to read another word. Or you can keep reading words in pipeline by keeping valid high and changing the address every cycle.
If the data is not in the cache, ready will not be asserted in the next cycle. Then hold the valid and address signals until ready is high; meanwhile, the word is read from the external memory (back-end) and placed in the cache.
To write, the process is similar. ready high in the next cycle means the word has been written to the cache; ready low means you need to wait with valid high and the same address until ready is high again; meanwhile, the data is written to the back-end.
As long as the data is in the cache, consecutive (pipelined) reads and writes are supported, one word per clock cycle.
I hope this helps.

documentation can now be generated on branch build-dir

TY! :) 👍 🥇

FYI: We have a blog post on fuzzing iob-cache to check coverage. Joint work with Micron.
I've not seen much in fuzzing verilog, and it may be of interest.  There is no expectation of finding vulnerabilities. However, it can radicallyi reduce the cost of building tests that cover nodes and edges in your design.
https://forallsecure.com/blog/running-iob-cache-in-mayhem

Hi David, Thanks, I saw your blog post -- very interesting
In fact, you may find vulnerabilities :-) ...


Create HTTPS SecurityGruop in CloudFormation environment template

In environment.yml CloudFormation template the current SecurityGroup is only set up to support HTTP port 80 traffic. We should add to or change the SecurityGroupIngress property to include HTTPS port 443 traffic by default.
We need to discuss what defaults we expect for the PublicLoadBalancer construct and how we plan to enable HTTPS.

I believe HTTPS support is now provided via custom resources.


NKNUSDT on binance is not there

the pair NKNUSDT on binance is not available.

also pair DOCKUSDT is missing


Apply for membership

Hi there, I'd like to be a member of oam community.
https://github.com/kubevela/catalog/pull/191
https://github.com/kubevela/kubevela/pull/3285
Thanks.

cc @wonderflow

invited, thanks for your contributions!


Improve About Us Page

Description
The current About Us page only shows small icons of the contributors.

I was thinking of a way of making cards which show their Github (and Linkdedln) profile info when hovered. An example can be found as shown:

I would like to work on this if approved.

We are planning to remove the about page and move this part to the home page

So can I work on implementing the said idea in the Home Page itself? Or do you have other plans for the same.

https://github.com/rohitdasu/projectmate/issues/190

can i work on this issue?

hi @ginabeki this task is duplicate one. you can find the new task in #190

closing this issue as we have another one related to this.


[Feature request] Device tracker popup

Hi guys!
I was thinking, perhaps it would be a good idea to open a popup with a big map when you click on the device tracker tile and if one has coordinates. What do you think? @akloeckner @rchl

Sounds like a neat enhancement. Are you thinking, just a fullscreen DEVICE_TRACKER tile with fixed zoom setting (=should be easy with popups right now)? Or an actual embedded map (= not sure how that would be done)?

Sounds like a neat enhancement. Are you thinking, just a fullscreen DEVICE_TRACKER tile with fixed zoom setting (=should be easy with popups right now)? Or an actual embedded map (= not sure how that would be done)?

I think a fixed zoom full screen would be enough for everyone.

I think a fixed zoom full screen would be enough for everyone.

How about something like this?
                  {
                     type: TYPES.DEVICE_TRACKER,
                     id: 'device_tracker.ak_honor',
                     position: [3,0],
                     map: 'mapbox',
                     zoomLevels: [9,13],
                     slidesDelay: 2,
                     action: function(item, entity) {
                        this.$scope.openPopup(item, entity);
                     },
                     popup: {
                        classes: ['-popup-landscape'],
                        styles: {},
                        items: [{
                           type: TYPES.DEVICE_TRACKER,
                           id: 'device_tracker.ak_honor',
                           map: 'mapbox',
                           zoomLevels: [6],
                           position: [0,0],
                           width: 5, height: 4,
                           classes: ['-item-fullsize'],
                           customStyles: {
                              width: null,
                              height: null,
                              top: null,
                              left: null,
                           },
                           action: false,
                           secondaryAction: false,
                        }]
                     }
                  }

We'd have to change this function, to use cacheInItem, then:
https://github.com/resoai/TileBoard/blob/a057d2a146492eb62faaa9d819ef723efcaa42cb/scripts/controllers/main.js#L320
(Probably should anyways, in case someone wants multiple different tiles of the same tracker...)
Probably, we'll also want to add some magic to retrieve the actual fullsize tile size, here:
https://github.com/resoai/TileBoard/blob/a057d2a146492eb62faaa9d819ef723efcaa42cb/scripts/controllers/main.js#L195
(Currently, the bogus width and height determine the image resolution.)

How about something like this?
                  {
                     type: TYPES.DEVICE_TRACKER,
                     id: 'device_tracker.ak_honor',
                     position: [3,0],
                     map: 'mapbox',
                     zoomLevels: [9,13],
                     slidesDelay: 2,
                     action: function(item, entity) {
                        this.$scope.openPopup(item, entity);
                     },
                     popup: {
                        classes: ['-popup-landscape'],
                        styles: {},
                        items: [{
                           type: TYPES.DEVICE_TRACKER,
                           id: 'device_tracker.ak_honor',
                           map: 'mapbox',
                           zoomLevels: [6],
                           position: [0,0],
                           width: 5, height: 4,
                           classes: ['-item-fullsize'],
                           customStyles: {
                              width: null,
                              height: null,
                              top: null,
                              left: null,
                           },
                           action: false,
                           secondaryAction: false,
                        }]
                     }
                  }

We'd have to change this function, to use cacheInItem, then:
https://github.com/resoai/TileBoard/blob/a057d2a146492eb62faaa9d819ef723efcaa42cb/scripts/controllers/main.js#L320
(Probably should anyways, in case someone wants multiple different tiles of the same tracker...)
Probably, we'll also want to add some magic to retrieve the actual fullsize tile size, here:
https://github.com/resoai/TileBoard/blob/a057d2a146492eb62faaa9d819ef723efcaa42cb/scripts/controllers/main.js#L195
(Currently, the bogus width and height determine the image resolution.)

Yeah, width, height, position and styles for all popups... perhaps we could could have all of them as defaults, but great otherwise!

Yeah, width, height, position and styles for all popups... perhaps we could could have all of them as defaults, but great otherwise!

perhaps we could could have all of them as defaults

:-) we definitively should.
I think, it should be relatively easy to turn this stub into a PR. Unfortunately, I'm caught up in other projects currently. But if you are willing to start developing a feature, I'll happily offer test and feedback!
I would consider the following locations as blueprints for the new popup:
Default action: https://github.com/resoai/TileBoard/blob/a057d2a146492eb62faaa9d819ef723efcaa42cb/scripts/globals/constants.js#L435
Opening function: https://github.com/resoai/TileBoard/blob/a057d2a146492eb62faaa9d819ef723efcaa42cb/scripts/controllers/main.js#L1615
Popup definition: https://github.com/resoai/TileBoard/blob/a057d2a146492eb62faaa9d819ef723efcaa42cb/scripts/globals/constants.js#L300

perhaps we could could have all of them as defaults

:-) we definitively should.
I think, it should be relatively easy to turn this stub into a PR. Unfortunately, I'm caught up in other projects currently. But if you are willing to start developing a feature, I'll happily offer test and feedback!
I would consider the following locations as blueprints for the new popup:
Default action: https://github.com/resoai/TileBoard/blob/a057d2a146492eb62faaa9d819ef723efcaa42cb/scripts/globals/constants.js#L435
Opening function: https://github.com/resoai/TileBoard/blob/a057d2a146492eb62faaa9d819ef723efcaa42cb/scripts/controllers/main.js#L1615
Popup definition: https://github.com/resoai/TileBoard/blob/a057d2a146492eb62faaa9d819ef723efcaa42cb/scripts/globals/constants.js#L300

Unfortunately I barely have any time myself and I did not even setup new env after changing project structure.

Unfortunately I barely have any time myself and I did not even setup new env after changing project structure.

Oh, and that was quite awhile ago... let's just stash the idea for latter then...

Oh, and that was quite awhile ago... let's just stash the idea for latter then...


google-auth is orphaned

Details

Read the Docs project URL: https://readthedocs.org/projects/google-auth
Build URL (if applicable):
Read the Docs username (if applicable): theacodes

Expected Result
A description of what you wanted to happen
I should be able to manage the google-auth project.
Actual Result
A description of what actually happened
It appears to be orpaned and has no maintainers. This probably happened as a result of me deleting my old account as detailed in #4576.
I'm happy to verify my identity via whatever means y'all want.

This probably happened as a result of me deleting my old account as detailed in #4576.

I'm almost sure that this was the case. I'm re-adding you as maintainer.

@theacodes done! You should have access to the project now. I'm closing the issue, but feel free to reopen if it does not work as you expects. Thanks!

All seems well, thank you!


fix: load new version of translation files

On production, new files aren't loading because of cache

https://github.com/ngx-translate/core/issues/1143#issuecomment-559705117


Slow login for new users

Describe the problem
Netbird interface is slow to load for new users logging in for the first time. (4-5 minutes)
To Reproduce
Launch Netbird from Authentik.
Expected behavior
The netbird gui will load promptly for the user
Additional context
Based on the logs from the management docker I believe this is a problem with the sqlite database.
These entries flood the management server logs:
management-1  | 2024-01-15T21:23:00Z ERRO management/server/event.go:53: received an error while storing an activity event, error: database is locked
management-1  | 2024-01-15T21:23:00Z ERRO management/server/event.go:53: received an error while storing an activity event, error: database is locked
management-1  | 2024-01-15T21:23:00Z ERRO management/server/event.go:53: received an error while storing an activity event, error: database is locked

If I had to guess there may be too many groups in the token for the sqlite db to deal with.
I am sending the user's groups with the claim (include claims in id_token).

Hi @mlsmaycon,
Sure thing.

Do you have JWT group sync enabled?
Yes

are your events in the activity tab repeated?
Yes. For example, when I login I see all the
"Group xyz added to user"
There are several groups naturally, but it does repeat groups of the same name.

Can you enable debug logs and share the management service logs? To do that you need to update the docker-compose.yml and add the flag "--log-level", "debug" to the service’s command section. Then you can run docker compose logs management > management-service.log 2>&1
That log has been attached (I sanitized the hostnames and IP addresses only)

management-service.log

Thanks @TSJasonH, after reviewing the log, I can only see an issue with your event.db used for activity events.
Could you share the number of groups in your JWT, a screenshot of your account settings > Groups configuration page and run the following checks for us?

Confirm that your jwt groups are associated with your user and the peers that belong to it.
Then disable JWT group sync( that won't remove any group).
Create a single group and add it to your user.
Validate that it is stored by login out and login in again
Check for duplicates events in your activity events

Hello @TSJasonH we were able to reproduce the issue and will work on a fix

Hello @TSJasonH the PR #1486 will fix the issue with duplicated events.
For the database size, you have a few options, but unfortunately, they all involve removing data.

You can delete the events.db file, and lose activity events until now, here are the steps for that:

# find the local path for the management volume
docker volume inspect netbird-mgmt | jq '.[].Mountpoint'
# stop the service
docker compose stop managmeent
# Move the events file to a backup location
mv <VOLUME PATH>/events.db ./events.db.backup
# start the service
docker compose stop managmeent

clean the group add events with sqlite3 command, which might be the best option as keep most of the relevant events:

# install sqlite3
# find the local path for the management volume
docker volume inspect netbird-mgmt | jq '.[].Mountpoint'
# stop the service
docker compose stop managmeent
# do a backup of events file
cp <VOLUME PATH>/events.db ./events.db.backup
# run sqlite3
sqlite3 <VOLUME PATH>/events.db
# run the delete statement
delete from events where activity = 20;
# exit sqlite3
# start the service
docker compose stop managmeent

Hello @TSJasonH, the fix is included in the release 0.25.5. Please upgrade and perform the database cleanup as suggested.

The "delete from events where activity = 20;" command completed without issues but didn't seem to actually shrink the size of the db file at all. I ended up just renaming the old one and allowing a new one to be created (no big deal on the data loss for me since this isn't in production yet).
Additionally the last docker command has "stop" where I think you meant to write "start" for the management container.
I can confirm that groups were applied properly now when logging into the interface, and it didn't take an extended period of time to complete.
Thanks!

I see; I believe we missed a vacuum command to shrink the database file after deleting the rows.


Make Wallaroo default targets configurable

allows for overriding default targets in rules/Makefiles
which inherit the base Wallaroo Makefile/rules
has no impact on the wallaroo targets unless turned off

ref #

@aturley @jdeaver @jtfmumm I just need a single person to confirm that the default targets (make build or make test  should suffice) work as expected with this change

@aturley Can you try running make test on this branch for outside verification? I ran into problems not specific to this branch I need to look into.


Support maxLength for string attributes

Check if the text given for a string attribute exceeds a certain limit.
Example configuration:
attributes:
  field1: !string {}
  field2: !string {maxLength: 15}

Looks good :-)

Thanks.

Wouldn't it make sense to send the maxLength information to the client when requesting the capabilities.json?
The client textfields could use this information to validate before triggering the print request.


Sw jenkins fix

I made some fixes to get hls memcopy to run on tul2,

Peek and poke makes no sense, i can add snap_maint to make sure the card is configured.

Please approve again, i added snap_maint()


pythonPackages.numba: 0.51.0 -> 0.52.0

Motivation for this change
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 114572 run on x86_64-linux 1

12 packages marked as broken and skipped:

python37Packages.arviz
python37Packages.dftfit
python37Packages.pygbm
python37Packages.pymc3
python38Packages.arviz
python38Packages.dftfit
python38Packages.pygbm
python38Packages.pymc3
python39Packages.arviz
python39Packages.dftfit
python39Packages.pygbm
python39Packages.pymc3

8 packages failed to build and already failed to build on hydra master:

python37Packages.shap: plain log  |  pretty log
python38Packages.shap: plain log  |  pretty log
python39Packages.awkward: log was empty
python39Packages.clifford: log was empty
python39Packages.datashader: log was empty
python39Packages.pynndescent: log was empty
python39Packages.shap: log was empty
python39Packages.stumpy: log was empty

13 packages failed to build and are new build failures:

python39Packages.dask-ml: log was empty
python39Packages.fastparquet: log was empty
python39Packages.graspologic: log was empty
python39Packages.gumath: log was empty
python39Packages.hyppo: log was empty
python39Packages.librosa: log was empty
python39Packages.numba: plain log  |  pretty log
python39Packages.pygmo: log was empty
python39Packages.resampy: log was empty
python39Packages.sparse: log was empty
python39Packages.stytra: log was empty
python39Packages.tensorly: log was empty
python39Packages.timezonefinder: log was empty

41 packages built:

python37Packages.awkward
python37Packages.clifford
python37Packages.dask-ml
python37Packages.datashader
python37Packages.fastparquet
python37Packages.graspologic
python37Packages.gumath
python37Packages.hyppo
python37Packages.librosa
python37Packages.llvmlite
python37Packages.numba
python37Packages.phik
python37Packages.pygmo
python37Packages.pynndescent
python37Packages.resampy
python37Packages.sparse
python37Packages.stumpy
python37Packages.stytra
python37Packages.tensorly
python37Packages.timezonefinder
python38Packages.awkward
python38Packages.clifford
python38Packages.dask-ml
python38Packages.datashader
python38Packages.fastparquet
python38Packages.graspologic
python38Packages.gumath
python38Packages.hyppo
python38Packages.librosa
python38Packages.llvmlite
python38Packages.numba
python38Packages.phik
python38Packages.pygmo
python38Packages.pynndescent
python38Packages.resampy
python38Packages.sparse
python38Packages.stumpy
python38Packages.stytra
python38Packages.tensorly
python38Packages.timezonefinder
python39Packages.llvmlite

The following issues got detected with the above build packages.
Please fix at least the ones listed with your changed packages:

python37Packages.datashader:

warning: duplicate-check-inputs
Dependencies listed in propagatedBuildInputs should not be repeated in checkInputs.
Detected duplicates:

python3.7-pandas-1.1.5

Near pkgs/development/python-modules/datashader/default.nix:68:3:
   |
68 |   checkInputs = [
   |   ^

Near pkgs/development/python-modules/datashader/default.nix:47:3:
   |
47 |   propagatedBuildInputs = [
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/duplicate-check-inputs.md

python37Packages.llvmlite:

Please consider this feature to be alpha.
A substituteInPlace with an unmatched pattern got detected:
substituteStream(): WARNING: pattern '-static-libstdc++' doesn't match anything in file 'ffi/Makefile.linux'

Please check the offending substituteInPlace for typos or changes in source.
warning: stale-substitute
Stale substituteInPlace detected.
substituteStream(): WARNING: pattern '-static-libstdc++' doesn't match anything in file 'ffi/Makefile.linux'
See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/stale-substitute.md

python37Packages.phik:

warning: python-include-tests
Add a checkPhase for tests, or at least pythonImportsCheck.
See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/python-include-tests.md

python37Packages.pygmo:

warning: python-include-tests
Add a checkPhase for tests, or at least pythonImportsCheck.
See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/python-include-tests.md

python37Packages.resampy:

warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/resampy/default.nix:32:3:
   |
32 |   meta = with lib; {
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python37Packages.stytra:

warning: unclear-gpl
gpl3 is a deprecated license, check if project uses gpl3Plus or gpl3Only and change meta.license accordingly.
Near pkgs/development/python-modules/stytra/default.nix:82:5:
   |
82 |     license = lib.licenses.gpl3;
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/unclear-gpl.md

python37Packages.tensorly:

warning: duplicate-check-inputs
Dependencies listed in propagatedBuildInputs should not be repeated in checkInputs.
Detected duplicates:

python3.7-nose-1.3.7

Near pkgs/development/python-modules/tensorly/default.nix:28:3:
   |
28 |   checkInputs = [ pytest nose pytorch ];
   |   ^

Near pkgs/development/python-modules/tensorly/default.nix:25:3:
   |
25 |   propagatedBuildInputs = [ numpy scipy sparse ]
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/duplicate-check-inputs.md

python37Packages.timezonefinder:

warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/timezonefinder/default.nix:28:3:
   |
28 |   meta = with lib; {
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python38Packages.datashader:

warning: duplicate-check-inputs
Dependencies listed in propagatedBuildInputs should not be repeated in checkInputs.
Detected duplicates:

python3.8-pandas-1.1.5

Near pkgs/development/python-modules/datashader/default.nix:68:3:
   |
68 |   checkInputs = [
   |   ^

Near pkgs/development/python-modules/datashader/default.nix:47:3:
   |
47 |   propagatedBuildInputs = [
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/duplicate-check-inputs.md

python38Packages.llvmlite:

Please consider this feature to be alpha.
A substituteInPlace with an unmatched pattern got detected:
substituteStream(): WARNING: pattern '-static-libstdc++' doesn't match anything in file 'ffi/Makefile.linux'

Please check the offending substituteInPlace for typos or changes in source.
warning: stale-substitute
Stale substituteInPlace detected.
substituteStream(): WARNING: pattern '-static-libstdc++' doesn't match anything in file 'ffi/Makefile.linux'
See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/stale-substitute.md

python38Packages.phik:

warning: python-include-tests
Add a checkPhase for tests, or at least pythonImportsCheck.
See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/python-include-tests.md

python38Packages.pygmo:

warning: python-include-tests
Add a checkPhase for tests, or at least pythonImportsCheck.
See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/python-include-tests.md

python38Packages.resampy:

warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/resampy/default.nix:32:3:
   |
32 |   meta = with lib; {
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python38Packages.stytra:

warning: unclear-gpl
gpl3 is a deprecated license, check if project uses gpl3Plus or gpl3Only and change meta.license accordingly.
Near pkgs/development/python-modules/stytra/default.nix:82:5:
   |
82 |     license = lib.licenses.gpl3;
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/unclear-gpl.md

python38Packages.tensorly:

warning: duplicate-check-inputs
Dependencies listed in propagatedBuildInputs should not be repeated in checkInputs.
Detected duplicates:

python3.8-nose-1.3.7

Near pkgs/development/python-modules/tensorly/default.nix:28:3:
   |
28 |   checkInputs = [ pytest nose pytorch ];
   |   ^

Near pkgs/development/python-modules/tensorly/default.nix:25:3:
   |
25 |   propagatedBuildInputs = [ numpy scipy sparse ]
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/duplicate-check-inputs.md

python38Packages.timezonefinder:

warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/timezonefinder/default.nix:28:3:
   |
28 |   meta = with lib; {
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python39Packages.datashader:

python39Packages.llvmlite:

Please consider this feature to be alpha.
A substituteInPlace with an unmatched pattern got detected:
substituteStream(): WARNING: pattern '-static-libstdc++' doesn't match anything in file 'ffi/Makefile.linux'

Please check the offending substituteInPlace for typos or changes in source.
warning: stale-substitute
Stale substituteInPlace detected.
substituteStream(): WARNING: pattern '-static-libstdc++' doesn't match anything in file 'ffi/Makefile.linux'
See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/stale-substitute.md

python39Packages.pygmo:

python39Packages.resampy:

python39Packages.stytra:

python39Packages.tensorly:

python39Packages.timezonefinder:

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 114572 run on x86_64-linux 1

8 packages marked as broken and skipped:

python37Packages.arviz
python37Packages.dftfit
python37Packages.pygbm
python37Packages.pymc3
python38Packages.arviz
python38Packages.dftfit
python38Packages.pygbm
python38Packages.pymc3

2 packages failed to build and already failed to build on hydra master:

python37Packages.shap: log was empty
python38Packages.shap: log was empty

41 packages built:

python37Packages.awkward
python37Packages.clifford
python37Packages.dask-ml
python37Packages.datashader
python37Packages.fastparquet
python37Packages.graspologic
python37Packages.gumath
python37Packages.hyppo
python37Packages.librosa
python37Packages.llvmlite
python37Packages.numba
python37Packages.phik
python37Packages.pygmo
python37Packages.pynndescent
python37Packages.resampy
python37Packages.sparse
python37Packages.stumpy
python37Packages.stytra
python37Packages.tensorly
python37Packages.timezonefinder
python38Packages.awkward
python38Packages.clifford
python38Packages.dask-ml
python38Packages.datashader
python38Packages.fastparquet
python38Packages.graspologic
python38Packages.gumath
python38Packages.hyppo
python38Packages.librosa
python38Packages.llvmlite
python38Packages.numba
python38Packages.phik
python38Packages.pygmo
python38Packages.pynndescent
python38Packages.resampy
python38Packages.sparse
python38Packages.stumpy
python38Packages.stytra
python38Packages.tensorly
python38Packages.timezonefinder
python39Packages.llvmlite


why not support baichuan-7b?

Here is the instruction on adding new models https://vllm.readthedocs.io/en/latest/models/adding_model.html
I guess it relies on the community to support more models beyond defaults


Fixes #3749 Digraph FadeOut

Overview: What does this pull request change?
This pull request resolves issue #3749 in which edges do not FadeOut properly when using DiGraph. The default updater in the DiGraph class used the edge constructor .become to attach the edges to the vertices. I replaced the updater to function more similarly to the Graph updater which moves the endpoints of the Line. Also, noticed that Line::set_points_by_ends did not project onto the bounding box of start and end so I updated the behavior to match the constructor and the type hints to align with usage in the example scenes.

Documented behavior of Line::set_points_by_ends
Updated type hints in Line
Altered edge updaters in graph.py to use Line::set_points_by_ends instead of .become

Links to added or changed documentation pages

https://manimce--3786.org.readthedocs.build/en/3786/reference/manim.mobject.geometry.line.Line.html#manim.mobject.geometry.line.Line.set_points_by_ends
Further Information and Comments

Fixes #3749

Reviewer Checklist

[ ] The PR title is descriptive enough for the changelog, and the PR is labeled correctly
[ ] If applicable: newly added non-private functions and classes have a docstring including a short summary and a PARAMETERS section
[ ] If applicable: newly added functions and classes are tested

@chopan050 Thanks for the edit!
Side note: I'm interested in helping with the rewrite, do you know how I could get into that?

Side note: I'm interested in helping with the rewrite, do you know how I could get into that?

Any help is greatly appreciated! Simply join #dev-chat on the Manim Discord server, or the [manim/experimental] post on #development, and say that you're interested in helping. Somewhere in that post there's a list of the current tasks we have to do in experimental.

Feel free to ping me on Discord (I'm still @JasonGrace2282 ) if you want me to walk you through where we are right now in the rewrite :)
I'm always glad to have more people interested


Warning on Blank App created with Project Reunion 0.8 RC

Describe the bug
We're seeing the following warning on an app created with the Project Reunion 0.8 RC
Package 'Microsoft.ProjectReunion.InteractiveExperiences 0.8.0-rc' was restored using 'net5.0-windows10.0.19041, .NETCoreApp,Version=v3.1, .NETCoreApp,Version=v3.0, .NETCoreApp,Version=v2.0, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8, net5.0-windows10.0.17763, net6.0-windows10.0.17763, .NETFramework,Version=v4.6.1' instead of the project target framework 'UAP,Version=v10.0.17763'. This package may not be fully compatible with your project.
Steps to reproduce the bug

Create a new Blank App, Packaged (WinUI 3 in Desktop) or open the attached SampleApp
Build it

=> See warning
Version Info

NuGet package version:
Example: [Microsoft.ProjectReunion 0.8.0-rc] -->

Windows 10 version
Saw the problem?

Insider Build (xxxxx)

May 2020 Update (19041)
Yes

November 2019 Update (18363)

May 2019 Update (18362)

October 2018 Update (17763)

I am also getting this warning with ProjectReunion.InteractiveExperiences 0.8.0 and 0.8.1 on May 2020 Update (19041)

Thanks for the report, the warning is harmless. We'll have the issue addressed in the next preview of the 1.0 SDK.

The issue was addressed in WindowsAppSDK 1.0. @sibille let us know if you're still encountering the warning. Thanks again for the report.


MudTooltip: Event Reactions - Hover, Focus and Click Arrangements

Description
Fixes #4564.
First of all, we needed to wait popover fix to see true effects on server-side mobile. It's done, so we can discuss it now.
So why we need this?
With #4086 Focus event added to the tooltip, but that may be a problem for some situations, because there is no other option to prevent it.
Here is an example. The "GitHub Repository" tooltip doesn't close when you open a new tab and turn the page, because it still has focus and for current situation no way to prevent this.
https://user-images.githubusercontent.com/78308169/169671640-9c24f2bf-ccff-4ed7-b6b3-ec3390183ec7.mp4
Examples can be multiplied. So instead of force users to certain scenarios, adding options could make sense. The other argument, we still can not guarantee to certainly working tooltip/popover for all server-side/wasm projects. So this PR raises the probability of creating workarounds if we have side effects or something other with .net 7 in future.
So its not a breaking change. Tooltip still shows on focus and hover, but now we have options that ShowOnHover and ShowOnFocus. For the upper example, users can set ShowOnFocus="false" to disable the tooltip.
Or, users still want the tooltip with hover. This time they can use ClickBehavior="TooltipClickBehavior.ClickToHide". With this, tooltip shows on focus, but when user click on it, it disappears. It will solve the problems like upper example.
This PR doesn't have a touch addition. I think touch is a more general thing and should be discussed to adding whole library. But users can play with parameters to have their own touch reaction.
The result of this PR:
https://user-images.githubusercontent.com/78308169/169671882-c7c0b390-d87f-466e-a46d-8cf296eaa242.mp4
https://user-images.githubusercontent.com/78308169/169671888-bdb3541c-9674-4700-a4ed-4fb20bcb0b5b.mp4
How Has This Been Tested?
Tested visually with Server-Side and WASM and the touch versions.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue) (fixes bugs, but actually they are not bugs)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[ ] I've added relevant tests.

I expected that ClickToHide would hide the tooltip when directly clicking on the tooltip. Also, how can one toggle the tooltip by clicking? Can one use both ClickToShow and ClickToHide at the same time? It is impossible right now, right? Wouldn't a single option ClickToToggle be better than ClickToShow and ClickToHide ?

Actually a bool ToggleOnClick would be the better API then

Actually a bool ToggleOnClick would be the better API then

Why not. But first i say why i add this, then you decide better. ClickToShow option directly means the toggle thing, ClickToHide is only for hide tooltip. There is two situation i don't know:

If there will be racing condition, is there a change to false open the tooltip again instead of closing?
Probably there will be more work about touch events in future, click pattern should not conflict with possible touch implementations.

Actually i like the bool parameter. If you say ok, i can change.

There can not be a race condition I think. OK, let's do the bool parameter

Changed to bool parameter and text of docs, could you look at these again?

The doc text is ok. The last thing I want to discuss are the side-effects of ToggleOnClick. It is impossible to have a hover tooltip that can be clicked away now?

I know it overrides the others. I just want to know if this is side-effect is absolutely necessary or if it would also work if it would not override the others.
For instance, setting ShowOnFocus = true and ToggleOnClick = true, what if ToggleOnClick has no side-effect? Would it still work? Right now, you can not have both.

@henon thanks, i like the new API now, its much clear and much fixable if there will be some bugs. I changed the names and behavior. Also changed GitHub and example "Run" button behavior to show tooltip properly.

@mckaragoz: So I guess the enum can be removed? And in the docs the Note: about the side effect can be removed.
I am not sure about the naming Click, Hover and Focus, it is not clear from the names what they do. ShowOnClick, ShowOnHover and ShowOnFocus is much more concise. You agree @mikes-gh ?

@mckaragoz: So I guess the enum can be removed? And in the docs the Note: about the side effect can be removed.
I am not sure about the naming Click, Hover and Focus, it is not clear from the names what they do. ShowOnClick, ShowOnHover and ShowOnFocus is much more concise. You agree @mikes-gh ?

Yes you are right Click Hover Focus are actions not behaviours.

Also probably needs tests. Can I just be clear these parameters can all coexist?  ShowOnFocus in combination with ShowOnHover is good for accessibility for example with keyboard users without fine motor skills.

Also probably needs tests. Can I just be clear these parameters can all coexist? ShowOnFocus in combination with ShowOnHover is good for accessibility for example with keyboard users without fine motor skills.

In current situation, tooltip already works on hover and on focus, but there is no click option to show/hide. The new one doesn't have breaking changes, it has hover and focus to true, and click to false by default, same behavior.
And yes, all three are possible at the same time, or possible all combinations.
This is important for me because for now there is no option to disable focus option without disabling all tooltip. With this everything is possible :)

In current situation, tooltip already works on hover and on focus, but there is no click option to show/hide. The new one doesn't have breaking changes, it has hover and focus to true, and click to false by default, same behavior.

You've added logic thats not covered by the tests.
Also I would change the Example file name to be consistent with terminology.
TooltipReactExample -> TooltipActivationExample

In current situation, tooltip already works on hover and on focus, but there is no click option to show/hide. The new one doesn't have breaking changes, it has hover and focus to true, and click to false by default, same behavior.

You've added logic thats not covered by the tests.
Also I would change the Example file name to be consistent with terminology.
TooltipReactExample -> TooltipActivationExample

Yeah I will handle all, but henon asks you for the new API naming, should we have "ShowOnHover" or simply "Hover"?

@mckaragoz all with ShowOn prefix please

@henon sorry, didn't see the mikes's message on upper, changed names and docs, removed enum, add a click test. And other hover and focus events tests work.

Many thanks!


cpuid: 20200427 -> 20201006

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/cpuid/versions.
meta.description for cpuid is: "Linux tool to dump x86 CPUID information about the CPU"
meta.homepage for cpuid is: "http://etallen.com/cpuid.html"
meta.changelog for cpuid is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 20201006 with grep in /nix/store/03i89q76p99h8wp5wbas4a299csmk3vv-cpuid-20201006

directory tree listing: https://gist.github.com/f84935dc64ad17a5469993d2e534fdbf

du listing: https://gist.github.com/3ad958be8f4cd2662928561bbf87fbb5

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
0 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
cpuid

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/03i89q76p99h8wp5wbas4a299csmk3vv-cpuid-20201006 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cpuid https://github.com/r-ryantm/nixpkgs/archive/b4fd542f7f8cf8ffdd3ee5141efe632c58d459c9.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/03i89q76p99h8wp5wbas4a299csmk3vv-cpuid-20201006
ls -la /nix/store/03i89q76p99h8wp5wbas4a299csmk3vv-cpuid-20201006/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

1 package built:

cpuid

Maintainer pings
cc @blitz for testing.

@SuperSandro2000

This package should be marked linux only.

It lives in os-specific/linux and has platforms = [ "i686-linux" "x86_64-linux" ];. What else do you suggest?

@SuperSandro2000

This package should be marked linux only.

It lives in os-specific/linux and has platforms = [ "i686-linux" "x86_64-linux" ];. What else do you suggest?

Nvm. I had allowUnsupportedSystem = true; on for a quick test and forgot to remove it again. 😂 🤦

No worries. ;)


Removed angular.copy instruction

I found this dramatically affected performance when dealing with a great number of items (10000+).
The digest loop went from 3.5s+ to < 500ms.
Would like to discuss this further, maybe by adding an options to enable/disable this behaviour.

This breaks the model bindings when the user adds and deletes custom options. http://plnkr.co/edit/08ndwJ?p=preview
However, I'm considering using .slice() instead of angular.copy() to improve performance

Interesting, thanks for the clarification!

In my case I didn't break the model binding, I'll explain:
I limit the items to 1 (maxItems), but I do not understand why this should make a difference
Ok that you have this condition but why should It matter, isn't the value still passed by reference?

Without that condition, the model value will = Array(value). but most people expect it to be the value itself, not an array with 1 item.


Incorrect patterns in update_**_for_continuation

FILL, to avoid "shifted pattern" on page boundary (I assume that 16B pattern is not handled yet and 8 is OK).
uint32_t processed = 8 * (fill_record.bytes_completed() / 8);
fill_dsc.transfer_size() -= processed;
fill_dsc.destination_address() += processed;

Does it apply to COMPARE_PATTERN?
DIF_INSERT:
uint32_t blocks_processed = bytes_completed / block_size;
bytes_completed -= blocks_processed  * block_size;
source_address += blocks_processed  * block_size;
destination_address += blocks_processed  * (block_size + DSA_DIF_SIZE);

Very similar pattern should be for DIF_STRIP.

Hey @jposwiata, thanks for bringing this to our attention. I don't think that we will have time to investigate/fix this issue for the next release (v1.2.0). Would it be okay if this is addressed at a later time? If you would need this fix as soon as it is addressed, you would need to use the develop branch as opposed to a release tag


[Buffer] Ensure data added is binary encoded.

Without this patch, it was possible for a buffer to change its encoding, which was occurring for me when in Framer#generate when adding data and then leading to an exception when prepending the common header.
irb(main):001:0> buffer = "".force_encoding(Encoding::BINARY)
=> ""
irb(main):002:0> buffer.encoding
=> #<Encoding:ASCII-8BIT>
irb(main):003:0> buffer << "émalgé"
=> "émalgé"
irb(main):004:0> buffer.encoding
=> #<Encoding:UTF-8>
irb(main):005:0> x = "\x00\x00\x80\x00\x01\x00\x00\x00\x13".force_encoding(Encoding::BINARY)
=> "\x00\x00\x80\x00\x01\x00\x00\x00\x13"
irb(main):006:0> buffer.prepend(x)
Encoding::CompatibilityError: incompatible character encodings: UTF-8 and ASCII-8BIT
	from (irb):6:in `prepend'
	from (irb):6
	from /Users/eloy/.rubies/ruby-2.2.2/bin/irb:11:in `<main>'

This patch ensures that the mutating methods that are used in Framer#generate are guaranteed to have a binary encoding, but it still feels a bit fragile. I think it would be better if Buffer were not a String subclass, but rather wrap a string and only expose the mutating API needed so that the possible surface for things to go wrong stays controllable. What are your thoughts?

I think it would be better if Buffer were not a String subclass, but rather wrap a string and only expose the mutating API needed so that the possible surface for things to go wrong stays controllable. What are your thoughts?

Yeah, that seems reasonable. Willing to take a run at it?

Aye, will do.

bump @alloy any luck with this one?

Merged via https://github.com/igrigorik/http-2/commit/d64b3eff83ce8f906bfe209873d81356c64eab83 - not sure why GH didn't pick it up.


After cloning, VM cannot be started; suspected race condition; introduce sleep after cloning

I think we likely will not merge this anymore (no comments in the last months)


remember lost connection and show it on the dashboard

When Webmin lose connection it will show a red window and that is really nice, but when the connection has establish again this red window will go away and now i can't see that there has been a lost connection.
I would like to know when Webmin has lost connection so i can see how often it will happen. If it will lost connection too often i would like to investigate it more further.
So could you add something to the dashboard that will persist so it is possible to see when i lost connection?

Okay, good idea.
Working on it, and actually finishing. Trying to figure out how to style colors properly.
I wanted to do it using Line Chart.
Example:

What do you think? It will tell you if you were away that connection was broken/fixed containing date and time data.

I've talked it over with the rest of the team and we don't all agree on polluting the Dashboard with such minor and weirdish feature.
I will possibly have to turn it down.

Oh no! Not a good idea. This is pretty fringe...I can't think of any other web app that notifies you of a disconnection while you were away. I don't think we should be trail blazing the idea of server connectivity monitoring by the browser.
Monitoring should be independent of the UI. Setup a status monitor in the System and Server Status module that notifies you (via email or SMS) when network connectivity fails. You can use the ping monitor or the web request monitor, or really anything...since you're concerned about network connectivity. Actually, there's a good idea in that. It would be cool if System and Server Status events could bubble up to the Notifications in Authentic Theme.
I'm gonna have to veto putting this kind of thing into the dashboard. There's already too much going on in the UI, and we need to simplify a bit.

Docs for System and Server Status are here, by the way: https://doxfer.webmin.com/Webmin/System_and_Server_Status

I didn't mean it should be a big graph (even if i liked it). It could be a small notice somewhere at the dashboard.

Sopor, what would you like to use it for?

The general solution of allowing any System and Server Status monitor to peek into the notifications would be more useful to everyone than having the browser check connectivity (and, I think it'd be way cooler).


[e2e]: nodejs release main default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/7498521875
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.release.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.release.main.default.slsa3.yml
Trigger: schedule
Branch: main
Date: Fri Jan 12 06:02:03 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/7510680749
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.release.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.release.main.default.slsa3.yml
Trigger: schedule
Branch: main
Date: Sat Jan 13 06:02:10 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v40.0.173
Run: https://github.com/slsa-framework/example-package/actions/runs/7517345837
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.release.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.release.main.default.slsa3.yml
Trigger: release
Branch: v40.0.173
Date: Sun Jan 14 06:09:38 UTC 2024
Tests are passing now. Closing this issue.


Compiled binary throws zlib dependency error

Version: Deno 1.39.1
Jan05-2100.ts
import { Database } from<EMAIL_ADDRESS>
const db = new Database("test.db");

const [version] = db.prepare("select sqlite_version()").value<[string]>()!;
console.log(version);

db.close();

Compile it
deno compile Jan05-2100.ts

Then run
./Jan05-2100
error: Uncaught (in promise) Error: Failed to load SQLite3 Dynamic Library
  throw new Error("Failed to load SQLite3 Dynamic Library", {
        ^
    at https://deno.land/x/sqlite3@0.10.0/src/ffi.ts:543:9
    at eventLoopTick (ext:core/01_core.js:181:11)
Caused by: Error: Could not open library: Could not open library: dlopen(/Users/gur/Library/Caches/deno/plug/https/github.com/104011a9e1238b1ae4e9c5bd462569d5bdcb9ae2d6b36d982871dbce44f79c44.dylib, 0x0005): Library not loaded: /opt/homebrew/opt/zlib/lib/libz.1.dylib
  Referenced from: <61850E31-E458-361A-ADCC-2CD22831D197> /Users/gur/Library/Caches/deno/plug/https/github.com/104011a9e1238b1ae4e9c5bd462569d5bdcb9ae2d6b36d982871dbce44f79c44.dylib (built for macOS 14.0 which is newer than running OS)
  Reason: tried: '/opt/homebrew/opt/zlib/lib/libz.1.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/opt/homebrew/opt/zlib/lib/libz.1.dylib' (no such file), '/opt/homebrew/opt/zlib/lib/libz.1.dylib' (no such file)
    at new DynamicLibrary (ext:deno_ffi/00_ffi.js:454:46)
    at Object.dlopen (ext:deno_ffi/00_ffi.js:591:10)
    at dlopen (https://deno.land/x/plug@1.0.1/mod.ts:125:15)
    at eventLoopTick (ext:core/01_core.js:181:11)
    at async https://deno.land/x/sqlite3@0.10.0/src/ffi.ts:531:12

This error solved by installing zlib
brew install zlib

Then works
./Jan05-2100
3.44.0

It's expected to work regardless user machine has zlib installed
https://github.com/denoland/deno/issues/21809#issuecomment-1879057507

Seems like we need to statically link to zlib for that. SQLite3 build doesn't seem to do it by default..

Are you on ARM Mac? ARM binaries are built locally and uploaded manually when making a release. Maybe there was some configuration issue earlier. We can try cutting a new release

Yes macbook air m2
So what should I do?

@7flash you should try building SQLite3 locally and run the tests in this repo to see if it works without installing zlib dependency. There are instructions to do so above my comment.

Yes on a M1.
Downloaded from github release:
otool -L ~/Downloads/libsqlite3_aarch64.dylib
/Users/steve/Downloads/libsqlite3_aarch64.dylib:
	/usr/local/lib/libsqlite3-<IP_ADDRESS>.dylib (compatibility version 9.0.0, current version 9.6.0)
	/opt/homebrew/opt/zlib/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.13)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1336.0.0)

If I build locally:
otool -L build/libsqlite3_aarch64.dylib
build/libsqlite3_aarch64.dylib:
	/usr/local/lib/libsqlite3-<IP_ADDRESS>.dylib (compatibility version 9.0.0, current version 9.6.0)
	/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.12)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1336.61.1)

Local build looks correct even if I do brew install zlib

would probs just work if you uninstall brew’s zlib before building since darwin comes with its own zlib

That would kinda explain why the build on CI (without installing brew zlib) doesn't have this issue compared to the build on my mac, where it is installed

I have the same issue, and I would prefer that the bundled builds do not require homebrew zlib.

This issue should be resolved in release 0.11.0


Brief pause on new features for winter holidays until January

Brief pause
Hey everyone! Due to parental leaves and winter holidays, we will have low coverage to support discussions, feature requests, and Discord until January.
Bug prioritization
If you reported a bug that is impacting you in production, please mention @sthulb, @mploski or @heitorlessa and we will prioritize it.
We appreciate everyone's understanding and we wish you an amazing holidays (or Christmas depending on your religious orientation)!

We're all back, closing the issue!


Revert "Bump rspec-rails from 3.8.2 to 3.9.0"

This reverts commit 1cbad39c4d2bfb5264ddcce58d33d66738f55b69, as it started failing the build.

It might be better to pin sprockets to ‘~> 3’ rather than reverting rspec. This app has no use for sprockets and would isolate the problem.

Merging to unblock PRs. Sounds like the brakeman PR is being merged soon, so the next time we attempt to bump the version everything should work fine, without the overhead of having to remove our pinning.


[5.4] Add when method to collections

Inspired by @tomschlick's addition to Eloquent, add a when method to the Collection class and help crush temporary variable assignment in your code.

For the sake of consistency, would it also make sense to add an optional $default callback parameter like Illuminate\Database\Query\Builder@when()? This callable is invoked when the truth condition is PHP falsy. This parameter was added in 5.3 to both the Eloquent and base query Builder classes.
public function when($value, callable $callback, callable $default = null)
{
    if ($value) {
        return $callback($this);
    } elseif ($default) {
        return $default($this);
    }

    return $this;
}

Yeah I'll make a PR for it


Extension host telemetry log channel shall be registered where the logger is getting created

At present, there shall not be any special code for registering an output channel for a logger. It is automated by creating the logger. The only special case is creating ext host telemetry logger which is still registered specially here
https://github.com/microsoft/vscode/blob/f777adc4909bd200f4a1696a6cdca3e76775d85d/src/vs/workbench/contrib/logs/common/logs.contribution.ts#L86
It would be nice if this can be moved to the location where the corresponding logger is being created
https://github.com/microsoft/vscode/blob/f777adc4909bd200f4a1696a6cdca3e76775d85d/src/vs/workbench/api/common/extHostTelemetry.ts#L38
For reference, please check the core telemetry logger here
https://github.com/microsoft/vscode/blob/f777adc4909bd200f4a1696a6cdca3e76775d85d/src/vs/platform/telemetry/common/telemetryLogAppender.ts#L35

Will be fixed along with the mentioned PR


Update lint-staged and husky examples

What I did

Remove gid add because it isn't necessary anymore. See lint-staged v10 changelog
Change the husky example to use a command to create the desired hook

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


Option to sort by file extension (i.e., ls -X)

It would be great to have the ls -X option for lsd. Just putting it out here as a potential nice-to-have feature

Hi @Bubblbu ,
Thanks for the report! I would be a great idea indeed! Do you want to take the issue an make a contribution?

Unfortunately very swamped right now. Also, no experience with Rust :(
But I will keep this on my radar! I saw another similar PR that added the -t option which might just need to be expanded


swiper doesnt work properly in webview

Hello,
I have a problem about show my link in webview in my RN app.
The problem is swiper doesnt work properly. But it works well at browser.
I used same link in "react-native": "0.59.1" & "react-native-webview": "7.4.2" before 1 year ago and i didnt see any problem.
I used the component from "https://flickity.metafizzy.co/". When i put it's web adress as source to Webview, i see same problem there too.
Can someone help me ?
link : https://frozen-taiga-83420.herokuapp.com/maledrobe

Android
react-native version: 0.61.5
react-native-webview version: 10.7.0

Thanks.

I guess it is about device. So i close this it.


update ci

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@48c34eb). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #24   +/-   ##
=======================================
  Coverage        ?   94.22%
=======================================
  Files           ?       13
  Lines           ?      987
  Branches        ?        0
=======================================
  Hits            ?      930
  Misses          ?       57
  Partials        ?        0

Flag
Coverage Δ

pytest
94.22% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.


HOT RELOAD: fast isolate restart with new source code

We can restart isolates using the same system as we do for hot reloading (preserve unchanged libraries, keep unoptimized code, etc).

@a-siva @rmacnak-google We should still do this if we can do it efficiently but it's not super high priority. From the meeting this morning:

we should find a way to take the clean libraries + scripts + classes + functions + unoptimized code objects from a host isolate and transplant those into target isolate. The dirty libraries can be loaded as normal to fill in the missing pieces. This would dramatically improve isolate spawn time and responsiveness of the newly spawned isolate.

Only taking clean libraries means only a subset of the classes, which might introduce holes in the class table:

Maybe we can just start with the dart: libraries as that will give us a dense cid space and still provide a bunch of the benefits.

Maybe we can take all clean classes and update their class ids so that they are dense? We don't want to take any instances of the classes so changing the class ids shouldn't mess anything up.

Maybe we allow for holes in the class table and fill them in when we load new classes?


how to configure compiler plugins?

I am thinking that commonly, you might want a compiler plugin for the whole repo.
We might want to have something like scala_library_internal so then repos can make a local scala_library macro that sets up default compiler options.
That seems like it would work okay. Any better approach?
I don't know now namespacing works in skylark, but I assume I can't import a rule with a name foo and also define a rule with the same name (thus the work around of adding variants of _internal to all the rules so we can import just a few of those).

I feel like the "ideal" way to do it is exactly what you said skylark doesn't support... have the bazel people weighed in at all if they want to support any notion of namespaces for skylark functions?

So per the response in https://github.com/bazelbuild/bazel/issues/1158, it seems like you can rename imports. With that, you can do it the "ideal" way, I think?

I think so. That's pretty good. We should probably just document that.

Here is documentation of the scalacopts pattern:
https://github.com/bazelbuild/rules_scala/wiki/Setting-repo-wide-compilation-defaults
See #47 for compiler plugin support


Can't send message after running for a long time

I always find a problem for TDLib Java for my applications. Two accounts running with two different applications separately show the same problem.
Usually after running for around 1 -2  weeks, it can't send message at all. And restart will fix the problem. But it is strange that after restart, the previous  message(s) which can't be sent will appear immediately automatically without resending again. This happened so many times already and I can't find any cause for this.
I also find haveAuthorization is already true.
Any suggestion for this issue?

What do you mean by "it can't send message at all"? What exactly happens? Do the messages stuck in the messageSendingStatePending state or something other?

Hi,
This is the method to send message:
public static void sendMessage(long chatId, String message, CommandResultHandler resultHandler) {
	TdApi.InputMessageContent content = new TdApi.InputMessageText(new TdApi.FormattedText(message, null), false, true);
	client.send(new TdApi.SendMessage(chatId, 0, 0, null, null, content), resultHandler);
}

When the problem happens, the above method still returns normally without causing any exception. But the message is not appeared. If I send other messages, all these messages can't be seen too until I shutdown and restart the application.
The strangest thing is that Telegram server have all these messages pending. When I restart the application, all these messages will then be released and appear. Of course my application does not resend them.
I do not know what messageSendingStatePending is. But it is likely to be related to this issue. How can I check with this?
Thanks!

A message returned by sendMessage is yet unsent and has a temporary message ID, because persistent message ID can be assigned only by the server. You need to handle updateMessageSendSucceeded, updateMessageSendFailed and updateDeleteMessages updates as described in https://core.telegram.org/tdlib/getting-started to correctly handle message sending.
If you send a message to a private chat after the client wasn't used for a long time, the message can be sent only after the client state is synchronized with the server and the connection state doesn't change to connectionStateReady. This could take some time, if you have a lot of private messages.

These do not seem to really explain the problem.
Firstly, for handling send message updates (updateMessageSendSucceeded, updateMessageSendFailed and updateDeleteMessages) none of these can make the message send finally even I wait for hours. I understand that they are useful to know the send message results. But the only way to fix the issue is restarting the application as I can do.  Without a restart, all messages sent by the application can't be seen at all even wait for many hours.
I just check messageSendingStatePending,  it shows message has not yet been delivered to the server. But waiting for max 10 hours can't see the message.
And I send at least one message to a private supergroup per day by this application. So does it caused by "the client wasn't used for a long time" ?
Finally for connectionStateReady issue, even waiting for 10 hours, the messages are not shown until a restart. How can I force client state to be synchronized if this is the root cause?
And the group messages are around 100-200 per day. So this does seem to be the issue with too many messages.
The hint is the restart fixs the problem and all messages will immediately appear. So what is the likely cause?

I send at least one message to a private supergroup per day by this application.

It doesn't matter how much messages is sent by this application, the total number of messages sent and received in private chats and small groups does matter.
Could you collect TDLib log with verbosity level 4 from the time application is started and up to one minute after the connection state is changed to connectionStateReady, but the message isn't actually sent and send it to @tdlib_bot in Telegram?

Sure! I will try to collect TDLib log. But I need to wait for this issue as it usually takes more than a week to happen.
Thank you!

@eos1d3 Did you manage to reproduce it?

Reproducing this problem is very easy as it always happens. But for safety issue, I do not run them recently. I have one log file after the issue was found. The issue caused ForwardMessage failed, but not SendMessage. I will send the log on coming Monday.
I will test this issue later.

@eos1d3 Do you still have the issue?

A message returned by sendMessage is yet unsent and has a temporary message ID

This should be updated in the sendMessage docs. Currently it says:

Returns the sent message.

That is quite confusing and i found it sometimes never returns at all.


A instruction with only one stage "fetch" will not show in the window

Hello, I found a problem that Konata will ignore the chart about an "only a fetch stage" instruction.
Is this a bug?

O3PipeView:fetch:199000:0x00010100:0:45:c_bnez a5, 12
O3PipeView:decode:0
O3PipeView:rename:0
O3PipeView:dispatch:0
O3PipeView:issue:0
O3PipeView:complete:0
O3PipeView:retire:0:store:0

I have just fixed this problem in version 0.38 and just released it. Please give it a try. This fix may cause problems in a gem5 trace, so if you find a problem, please report it. Thanks!

The bug has been fixed, thanks!


add Maven Central badge

Codecov Report

Merging #71 (531392c) into main (a3e3989) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main      #71   +/-   ##
=========================================
  Coverage     11.78%   11.78%
  Complexity       35       35
=========================================
  Files            65       65
  Lines          3359     3359
  Branches        358      358
=========================================
  Hits            396      396
  Misses         2907     2907
  Partials         56       56

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 a3e3989...531392c. Read the comment docs.


Corrected SQLite connection strings for 3.x and 5.0 code examples

Internal review:

Part 2, add a model: Section: Register the database context: VS Code: Code change for connection string
Screenshot update to match new VS update at RTM for Create a new ASP.NET Core web application dialog

Fixes issue #20473 Incorrect GetConnectionString param for VSC and macOS and updated new VS screenshot for Create a new app dialog which changed at RTM.

@wadepickett  see #20497

Closing this as unmerged and opening a new PR to keep this clean since I am changing the code files that need to be addressed.


KAFKA-2143: fix replica offset truncate to beginning during leader migration.

Seems like it fixes symptom (don't truncate log), instead of fixing original cause (possible race condition).

@lazyval , ideally the exception returned by leader should contain more information. However, that is a big wire protocol change and perhaps not necessary. The easier fix is to handle the exception correctly. So the problem is how to deal with the race condition. The follower is not confused in this case, it just needs one more check to understand the situation.

@becketqin, original issue https://issues.apache.org/jira/browse/KAFKA-2143 states that replica gets ahead of leader but you applied changes to branch for case when replica is far behind leader.

LGTM.

@becketqin Before committing this fix we need to figure out one thing, that this issue is ONLY due to an unclean election, and since in this case inconsistency will probably happen already we may allow follower to be different from leader. But as @junrao mentioned this can be also triggered by other scenarios then we cannot allow replicas to be inconsistent.

@guozhangwang The other issue is tracked by KAFKA-2477. After that is fixed, we should not see the OffsetOutOfRangeException triggered by that issue.

Merged to trunk and 0.9.0.

@becketqin   I think there are some problems with the comments. According to the logic of your program, fetchOffset should be the max value of (leaderStartOffset, replica.logEndOffset). But now the comment says that the fetchOffset is leaderStartOffset. Here, I give an immature comment, please take it.

Origin code

      val leaderStartOffset: Long = earliestOrLatestOffset(topicAndPartition, ListOffsetRequest.EARLIEST_TIMESTAMP,
        brokerConfig.brokerId)
      warn("Replica %d for partition %s reset its fetch offset from %d to current leader %d's start offset %d"
        .format(brokerConfig.brokerId, topicAndPartition, replica.logEndOffset.messageOffset, sourceBroker.id, leaderStartOffset))
      val offsetToFetch = Math.max(leaderStartOffset, replica.logEndOffset.messageOffset)
      // Only truncate log when current leader's log start offset is greater than follower's log end offset.
      if (leaderStartOffset > replica.logEndOffset.messageOffset)
        replicaMgr.logManager.truncateFullyAndStartAt(topicAndPartition, leaderStartOffset)
      offsetToFetch

Suppose modified code

      val leaderStartOffset: Long = earliestOrLatestOffset(topicAndPartition, ListOffsetRequest.EARLIEST_TIMESTAMP,
        brokerConfig.brokerId)
      val offsetToFetch = Math.max(leaderStartOffset, replica.logEndOffset.messageOffset)
      warn("Replica %d for partition %s reset its fetch offset from %d to %d, which is the max of current leader %d's start offset %d and replica logEndOffset %d"
        .format(brokerConfig.brokerId, topicPartition, replica.logEndOffset.messageOffset, offsetToFetch, sourceBroker.id, leaderStartOffset, replica.logEndOffset.messageOffset))
      // Only truncate log when current leader's log start offset is greater than follower's log end offset.
      if (leaderStartOffset > replica.logEndOffset.messageOffset)
        replicaMgr.logManager.truncateFullyAndStartAt(topicAndPartition, leaderStartOffset)
      offsetToFetch


Reduce cmp and cmp+br instructions

This reduces i{32,64}.{gt,ge}_{s,u} and f{32,64}.{gt,ge} instructions into respective {lt,le} variants.
Fused cmp+br instructions are also affected by the above change.
To support this, new {lt,le} variants with 16-bit immediate lhs values have been added.
Overall this reduces the total amount of Wasmi instructions by 24 which is quite significant.
Local benchmarks show significant improvements across the board:

I had a bit of trouble with the executor, as I am less experienced at that part, but it I couldn't see anything that looked wrong. The rest of the code ir, executor, instrs, tests I was more thorough and understood better and all looks good to me!

Thank you for the code review @dkcumming ! 🚀


4D quit when using curl

Since my  windows 11 as been updated to the version 2024-08 Mise à jour cumulative pour Windows 11 Version 23H2 pour les systèmes x64 (KB5041585), 4D quit after fews seconds when using curl.
Very rarely it s working but most of time 4D quit for example using cURL_FTP_GetDirList.
Thanks for your help

what if you disable Hardware-enforced Stack Protection ?

with no detail information about the Windows Defender log there is nothing I can do on my side.

https://www.windowslatest.com/2024/08/16/windows-11-kb5041585-ipv6-patch-slows-down-pcs-breaks-vanguard-fails-to-install/
because curl is not a device driver, maybe IPv6 related ?

from the article above

we observed that removing the patch and then turning off IPv6 manually is the best way to handle the problem

Thanks for yours informations.
On my PC I don't have Hardware-enforced Stack Protection.
Unfortunatly I desabled IPV6 and  unistalled the windows update. It seems a bit better but  most of time it s not working.
I have to investigate more.


User defined Target properties lost

Hi,
I'm trying to define a new class of target based on FixedTarget with extra properties to be used by a User-defined Constraint. This could be Magnitude, last-time observed, etc.
Unfortunately, in several places the target is transformed in a "target" which is no more than a astropy.SkyCoord, then all extra properties are discarded and make a pain in the neck to program any user-defined Constraint.
This is done in the method call in the class Constraint.
Any idea how to deal with that?

I ran into the same issue.  Rather than trying to subclass FixedTarget as a new target class with extra properties, an approach is to use your new user-defined constraint strictly as a block-specific constraint, rather than a global constraint.  You can then pass in your extra properties to the user-defined constraint on an observing block-by-block basis.  The math works out the same for global and block constraints when observing block scores are calculated.  Hope this helps.

Thanks,
That was a good solution. I just created a user-defined constraint which uses a user-defined parameter.


Release proto-java:0.5.16

Sorry for the late response, this changes will be included here https://github.com/terra-money/terra.proto/pull/22


Clean up design for messageboards index and new

This closed after merging kf-topics-index but I have since cherry-picked the commit. Thank you @kylefiedler!


when focus on Panel, using "workbench.action.closePanel" in "runCommands" sometimes the Panel will reopen

// put this in `keybinds.json`

//works fine
{
    "key": "alt+`",
    "command": "runCommands",
    "args": {
        "commands": [
            "workbench.action.closePanel",
            "workbench.action.maximizeEditor",
        ]
    },
    // "when": "inZenMode && (auxiliaryBarVisible || sideBarVisible || panelVisible) "
},
// works wrong
{
    "key": "alt+q",
    "command": "runCommands",
    "args": {
        "commands": [
            "workbench.action.maximizeEditor",
            "workbench.action.closePanel",
        ]
    },
},
// works fine when openAuxiliaryBar and closePanel
// works wrong when closeAuxiliaryBar and closePanel
{
    "key": "alt+e",
    "command": "runCommands",
    "args": {
        "commands": [
            "workbench.action.toggleAuxiliaryBar",
            "workbench.action.closePanel",
        ]
    },
},

https://github.com/microsoft/vscode/assets/3757123/f8dd216b-589a-4d50-8507-af95936bbeeb

unable to reproduce, is this still an issue?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Web autofill throw exception still reproducible

Steps to reproduce
See https://github.com/flutter/flutter/issues/85807
This issue is still reproducible!

Start example code in chrome debug mode.
hit down arrow to see suggested emails
select one
see error in log

Expected results
No error in log file
Actual results
error in logs
Code sample
Code sample
import 'package:flutter/material.dart';
import 'package:flutter/services.dart';

void main() => runApp(const MyApp());

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  static const String _title = 'Flutter Code Sample';

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: _title,
      home: Scaffold(
        appBar: AppBar(title: const Text(_title)),
        body: const MyStatelessWidget(),
      ),
    );
  }
}

class MyStatelessWidget extends StatelessWidget {
  const MyStatelessWidget({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Center(
      child: SizedBox(
        width: 100,
        child: TextFormField(
          autofillHints: [AutofillHints.username],
          keyboardType: TextInputType.emailAddress,
        ),
      ),
    );
  }
}

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
Error: Unexpected null value.
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 294:3       throw_
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 943:18  nullCheck
lib/_engine/engine/keyboard_binding.dart 372:38                                   [_handleEvent]
lib/_engine/engine/keyboard_binding.dart 582:7                                    handleEvent
lib/_engine/engine/keyboard_binding.dart 98:7                                     <fn>
lib/_engine/engine/keyboard_binding.dart 140:9                                    loggedHandler
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 574:37  _checkAndCall
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 579:39  dcall```

</details>

### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.16.5, on macOS 14.2.1 23C71 darwin-x64, locale en-NL)
[!] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.
[✓] Xcode - develop for iOS and macOS (Xcode 15.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.1)
[✓] IntelliJ IDEA Ultimate Edition (version 2023.2.3)
[✓] Connected device (4 available)
    ! Error: Browsing on the local area network for Apple Watch van J. Ensure the device is unlocked and discoverable via Bluetooth. (code -27)
[✓] Network resources

! Doctor found issues in 1 category.

Thanks for the report!
This is a known issue being tracked at https://github.com/flutter/flutter/issues/137771. Closing this issue as a duplicate, so please follow up on it for further updates.