Add "number" parameter to MarkerCluster

When you add markers to  MarkerCluster add a optional "number" parameter to the MarkerOptions (default: number=1). That way, MarkerCluster instead of showing the count of Markers, will show the sum of the "number" field in the Markers.
Very useful when you try to add lots and lots of identifical markes. For instance, if you have 100 markers in the same location, you only have to add one marker with "number=100" instead of adding 100 markers.
Pull request guide
Thank you for considering to improve this cordova-plugin-googlemaps.
When you create a pull request, please make it to multiple_maps branch instead of master branch.
Because the multiple_maps branch is edge version.
Thank you for your understanding.

Could you show me the screenshot? (I'm outside now)

Ah, I got your idea.
You want to show the value of markers instead of number of markers.

Right.
Three 3 markers with "number" equal to 48, 11 and 2:

When you zoom out:

On second thought, the name "number" is not a good one. It's best to call it "value" or "weight".

@rcpinheiro
Thank you for your PR. Your idea is good, but creating a special meaning property for particular is not good.
Because some people might want to more complex calculation, such as return value * priority;
I also asked someone wanted to customize the strings of the number, such as 2532 -> 2.5k
So, I will create a custom callback instead of particular property.


Oxlint crashes, due stack overflow and panics

Oxlint version - 0f026089d104800b963568f6703f91b737ac188f
command
oxlint file -D all -D nursery --fix

thread '<unknown>' has overflowed its stack
fatal runtime error: stack overflow
timeout: the monitored command dumped core

folder may contain also other crashes like
2024-07-08T09:04:58.1425461Z thread 'main' panicked at crates/oxc_diagnostics/src/reporter/graphical.rs:28:65:
2024-07-08T09:04:58.1427255Z called `Result::unwrap()` on an `Err` value: Error
2024-07-08T09:04:58.1430402Z note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
2024-07-08T09:04:58.1435215Z timeout: the monitored command dumped core

2024-07-08T09:41:20.0318660Z thread '<unnamed>' panicked at crates/oxc_linter/src/rules/eslint/array_callback_return/mod.rs:160:69:
2024-07-08T09:41:20.0320174Z called `Option::unwrap()` on a `None` value
2024-07-08T09:41:20.0321273Z note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
2024-07-08T09:41:20.0322577Z timeout: the monitored command dumped core

2024-07-08T07:34:13.8760591Z thread '<unnamed>' panicked at crates/oxc_linter/src/rules/unicorn/prefer_dom_node_dataset.rs:117:36:
2024-07-08T07:34:13.8762530Z byte index 5 is not a char boundary; it is inside '\u{8d}' (bytes 4..6) of `contnteditable`
2024-07-08T07:34:13.8767065Z note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
2024-07-08T07:34:13.8767997Z timeout: the monitored command dumped core

7zip file(needs to remove .zip extension) - zzz.7z.zip

It is probably related to https://github.com/oxc-project/backlog/issues/58

@qarmin I'd like to investigate this issue.
Is it possible for you to upload the archive as a plain zip with no passwords so we can check it for malware before downloading it? I personally have a phobia of downloading unknown files and *.7z.zip goes unchecked in online scanners and you can't look into the content without downloading it.
I know I'm overreacting and I hope it doesn't come out as rude to you, I truly appreciate your report but this fear has been totally out of my control in recent years.

qarmin is the fuzzer guy who is building a commercial fuzzer (my guess), he reported numerous crashes before.
I checked the files, it's safe to open the zip, there's 8779 js files in there.

This is .7z archive renamed as .zip, to be able to bypass github attachment limit(github not allows to put here 7z archives)
Of course I understand that it is better to be online too careful than not careful enough.
Files.zip *(

@qarmin Thanks I really appreciate it❤

I tested zzz.7z.zip with oxlint -D all -D nursery --fix --silent:
Finished in 1.2s on 8779 files with 258 rules using 8 threads.
Found 0 warnings and 263994 errors

Feel free to create more fuzzing issues @qarmin. For extra challenges, you may also fuzz rolldown 😁


Fresh install getting Error: Module version mismatch. Expected 48, got 46.

Description
Just installed functions-emulator and running any command gives the error:
Error: Module version mismatch. Expected 48, got 46.
    at Error (native)
    at Object.Module._extensions..node (module.js:597:18)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/usr/local/lib/node_modules/@google-cloud/functions-emulator/node_modules/grpc/src/node/src/grpc_extension.js:45:15)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)

Steps to reproduce

Nodejs installed and running v6.11.2
npm install -g @google-cloud/functions-emulator
functions-emulator start gives the above error

Thanks!

Give you give the fix I describe in #126 a try?

Yes I got this working based on that.  Had to uninstall then reinstall.
Thanks!


The site needs content loading using Markdown

the project requirements say :The site needs it's content loaded using Markdown as the data source like in the NextJS tutorial

I completely missed that requirement in the rubric, will promptly make the required changes

I have finished remaking the project so its content can be loaded using Markdown files


"Cannot debug over WIFI" on iOS device

Same symptoms that #7233
When I run on an iOS device ( flutter run -d myDevice -v ), the app is not launched, and the logs are ending by :
[ +619 ms] ------ Debug phase ------
[        ] Cannot debug f58ff425258a52e7af3a8509246f6e3f5b3c113a (UNKN, Unknown Device, uknownos, unkarch) over WIFI.
[   +4 ms] Application launched on the device. Attempting to forward ports.

=>Complete logs
logs from an other try
If I disable the WIFI before running, it's work, and I can re-activate WIFI when the app is open.
Flutter Doctor
[✓] Flutter (on Mac OS, channel master)
    • Flutter at /Users/rxlabz/dev/tools/flutter
    • Framework revision 1e1f7703cc (8 hours ago), 2017-02-21 12:22:26
    • Engine revision ab09530927
    • Tools Dart version 1.23.0-dev.0.0

[✓] Android toolchain - develop for Android devices (Android SDK 25.0.2)
    • Android SDK at /Users/rxlabz/Library/Android/sdk
    • Platform android-25, build-tools 25.0.2
    • Java(TM) SE Runtime Environment (build 1.8.0_111-b14)

[✓] iOS toolchain - develop for iOS devices (Xcode 8.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 8.2.1, Build version 8C1002
    • ios-deploy 1.9.1

[✓] Android Studio (version 2.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Gradle version 2.14.1

[✓] IntelliJ IDEA Ultimate Edition (version 2016.3.4)
    • Dart plugin version 163.13137
    • Flutter plugin version 0.1.10

[✓] Connected devices
    • A3 A40    •<PHONE_NUMBER>15                             • android-arm • Android 6.0 (API 23)
    • RXMiniPad • f58ff425258a52e7af3a8509246f6e3f5b3c113a • ios         • iOS 10.2.1 (14D27)
    • iPad Air  • 2B4DFECA-26F5-43F6-96C7-771B3B32535B     • ios         • iOS 10.2 (simulator)

@rxlabz this should be fixed by #8309. Can you try flutter upgrade and see if things are working now even with wifi enabled?

It works from command line and from IntelliJ plugin ! 👍  thank you

Perfect! Thanks for confirming!

I found this link -  and I followed the same and it worked for me. Make sure you are on the same network and your device is added to provisioning profile.

@prashantkaria, this link is broken. Do you have an alternative? Thanks 🙂

Hi @rob-patchett Yes here it is - https://www.logisticinfotech.com/blog/debug-ios-device-wifi

Looks like USB-c to lightning cable is still damn expensive 😅


Giving end-users the choice of identity provider

I see that the provider parameter and the associated ones like client_id and client_secret only take a single value right now. That forbids app owners from leaving end-users with the choice of identity providers. Is there a fork/PR which has removed this restriction? If not, is this on the development roadmap?

👍


webhooks and recording

hi,
after several yers using rtmp services, i'm trying this rtsp server and i'm looking for some functionality that seems missed:

will be supported "natively" some kind of recording process to store recording paths?
there is some kind of functionality that allows to notificate another server when a stream is start or reconect, like a webhook (maybe with a delayed  timeout)?

Hello,

will be supported "natively" some kind of recording process to store recording paths

At the moment the recording is not native (since this would require supporting containers and codecs, but maybe one day we'll get to this point), but nothing forbids from using ffmpeg together with rtsp-simple-server to achieve the result:
paths:
  mystream:
    runOnPublish: ffmpeg -i rtsp://localhost:$RTSP_PORT/$RTSP_PATH -c copy -f mpegts $(date +'%s').ts
    runOnPublishRestart: yes

This configuration saves all the streams published to path mystream as TS files.

there is some kind of functionality that allows to notificate another server when a stream is start or reconect, like a webhook (maybe with a delayed timeout)?

Yes:
paths:
  mystream:
    runOnPublish: ./on_publish.sh

create a file named on_publish.sh with the following content
#!/bin/sh
trap 'curl http://webhook-on-disconnect' INT
curl http://webhook-on-connect
sleep 86400

if you don't care about the disconnect webhook, you can simply do:
paths:
  mystream:
    runOnPublish: http://webhook-on-connect

This concept works great on linux. Do you have a good way to do a webhook  on windows? that we can call a webservice to notify on publish? I guess we could build our own exe to call it, but it would be good to know your thoughts.
also, the same for disconnect.

@t3therdev use Powershell, Cygwin or build an exe with Go - scripting is much more versatile than any new feature that can be added to the server.
Some software are shipped with interpreters, like Lua or Python, but nowadays there's a decent scripting engine in every OS too.


Fixes static build script given cub directory rename

Description
The cub 3rd-party repository has been recently renamed to nvidia-cub. This PR updates the static library compilation script to reflect these changes.

The PR has been merged. Thank you for the quick fix!


Start on webpack config

Ok the game works, and is playable end-to-end. There is a lot that needs to be refactored though :-)

Todo left for this branch: make sure the release process is working again


Export Major, Minor, Patch, Prerelease etc. versions as environment variables

Found it would be useful for building github actions to have application Major version inside environment variables to update tag Action's latests major version tag. So I think I can extract all of them into environment variables.

Done: https://github.com/HardNorth/github-version-generate/releases/tag/v1.2.0


Missing request timeout

Hi
it seems that our project, which use https://github.com/GoogleCloudPlatform/google-cloud-python/tree/master/storage/google/cloud/storage, is getting stuck during upload.
Although we can't confirm it with absolute certainty, it may be good idea have request timeout in resumable-media anyway.
Questions are:

do you find a timeout good idea in general?
should be there some well-chosen conservative implicit timeout by library (or explicit user defined timeout is preferred despite much complicated implementation because this library is only used by other google cloud platform libraries)?

We can provide eg. pull request for default timeout but we rather discuss all first.

I think a sane timeout makes sense.


Can't check ToS on mobile (iOS)

https://github.com/polarsource/polar/assets/281715/e09f3cb6-d3cc-49c2-b6e6-03b46a8ebf4d

On Chrome Desktop too so not browser specific, but a pure bug


Remove unused rand dependency

Can't we have bitcoin::PrivateKey::generate? I'd like that :)

Travis fails because the fuzzer seems to actually trigger a crash. I don't really see why as I haven't touched any functioning code. I can't find any helpful fuzzer output. The content of the file hfuzz_workspace/outpoint_string/SIGABRT.PC.7ffff7dbc82f.STACK.dae3564e1.CODE.-6.ADDR.(nil).INSTR.mov____0x108(%rsp),%rcx.fuzz is
$ xxd 'hfuzz_workspace/outpoint_string/SIGABRT.PC.7ffff7dbc82f.STACK.dae3564e1.CODE.-6.ADDR.(nil).INSTR.mov____0x108(%rsp),%rcx.fuzz'
00000000: 3636 3636 3631 3931 3432 3931 3432 3931<PHONE_NUMBER>914291
00000010: 3432 3934 3130 3932 3135 3037 3736 3636<PHONE_NUMBER>077666
00000020: 3139 3134 3239 3134 3239 3134 3239 3431<PHONE_NUMBER>142941
00000030: 3039 3231 3531 3737 3736 3631 3931 c2bf<PHONE_NUMBER>6191..
00000040: 3a2b 00                                  :+.

I thought for a sec it might have been https://github.com/rust-bitcoin/rust-bitcoin/pull/271, but that one's not merged yet. I don't understand the fuzzer quite that well..

Oof. This is a bug in the FromHexIterator in bitcoin_hashes which uses .len() (byte length) to determine if we have an even-length string but then the .chars() iterator to take characters, meaning that multibyte characters may fool our even/odd detection.

Hmm, suddenly it says "All checks have passed" ... Let's try again.

looks like it's working

We can deal with changes to rust-secp the next time we update our rust-secp dependency; for now we should just fix the badly out-of-sync rand dependency in rust-bitcoin.


Where is VIC-2 adapter??

https://github.com/c0pperdragon/C64-Video-Enhancement#create-your-own-kit


REACT_EDITOR=idea does not work

Describe the bug
According to this line: https://github.com/facebook/create-react-app/blob/2874e1209e14c7bff6c51fa3d73a53c5a15944cf/packages/react-dev-utils/launchEditor.js#L68-L69 it looks like it should have different format. However, on try opening the file I getting
open: unrecognized option `--line'

Anyway, when I trying to manually open the file it doesn't work with name:line neither with --line parameter, as it looks like it uses open command:
$ which idea
/usr/local/bin/idea

$ cat /usr/local/bin/idea
#!/bin/sh
# Generated by JetBrains Toolbox 1.15.5796 at Mon Sep 2 16:09:31 2019

open -a "/Users/extempl/Library/Application Support/JetBrains/Toolbox/apps/IDEA-U/ch-0/192.6603.8/IntelliJ IDEA 2019.2 EAP.app/Contents/MacOS/idea" "$@"

P.S., so the command added by toolbox, and it has different format from what described here: https://www.jetbrains.com/help/idea/opening-files-from-command-line.html
Environment
MacOS, IDEA

Looks like the IDEA's issue (Jetbrains Toolbox to be precise): https://youtrack.jetbrains.com/issue/TBX-3846.
So, closing this here.

Anyway, is it really ok, that it outputs --line format while in the code it set to be {file}:{line}?


Dropdown Help

Hi! I know there are some Issues posted about this. But it is already closed. Look I'm not that good with creating html files or lets say coding, But I love doing it and I want to use bootstrap, but the dropdown is not working. I searched the github and the net I followed the suggestions but nothing worked. Can someone please help me. Here's my code.
<link rel="stylesheet" type="text/css" href="bootstrap.css">
<link rel="stylesheet" type="text/css" href="own.css">

      MY TEAM

		Home

FAQ

			About

About this

About that

About

Contact

Thanks! I added the jQuery. I tried to place it in the ul but didn't work and made this div class="topbar" data-dropdown="dropdown". And worked fine. THANKS!! :D


Flatten simple if-else statements in brillig to avoid unnecessary jump statements

Consider the program
unconstrained fn main(active: bool) -> pub Field {
    if active { 2 } else { 0 }
}

This compiles to the SSA
brillig(inline) fn main f0 {
  b0(v0: u1):
    jmpif v0 then: b2, else: b1
  b2():
    jmp b3(Field 2)
  b3(v1: Field):
    return v1
  b1():
    jmp b3(Field 0)
}

This is equivalent to the program
unconstrained fn main(active: bool) -> pub Field {
    2 * (active as Field)
}

which compiles down to the program
brillig(inline) fn main f0 {
  b0(v0: u1):
    v1 = cast v0 as Field
    v3 = mul Field 2, v1
    return v3
}

This is much smaller in terms of bytecode size and more amenable to further optimizations. We should then attempt to find simple if-else blocks similar to this in SSA and flatten them even in the case of brillig functions (we'll likely want to apply the changes made in https://github.com/noir-lang/noir/pull/6073 as part of this).
This may seem a bit of a contrived example but we make heavy use of small if statements such as these in the sha256 implementation such that these jumpifs make a non-trivial portion of the overall program.

Two key considerations here are that we need to make sure that:

The arms of the if-else statement are small enough that executing both branches is preferable to the overhead of the jumpif.
The instructions in each arm are infallible, e.g. we can't pull an array get which may fail out of an if-else to be performed unconditionally.


chore: add ctrader section

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

36 of 79 (45.57%)  changed or added relevant lines in 10 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.4%) to 39.658%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/components/CFDSection/CFDContent/CFDContent.tsx
1
2
50.0%

src/cfd/components/CTraderList/CTraderList.tsx
7
14
50.0%

src/cfd/flows/CTrader/AddedCTraderAccountsList/AddedCTraderAccountsList.tsx
11
28
39.29%

src/cfd/flows/CTrader/AvailableCTraderAccountsList/AvailableCTraderAccountsList.tsx
10
28
35.71%

Totals

Change from base Build<PHONE_NUMBER>:
-0.4%

Covered Lines:
603

Relevant Lines:
1150

💛  - Coveralls


incorrect file size in WOFF header

Short description of the problem:
With version 0.0.45 I was able to extend ionicons with no problem (just adding few icons to v3 branch)
now with version 0.0.47, im getting this error for the icons:
Failed to decode downloaded font: http://localhost:8100/assets/fonts/ionicons.woff2?v=3.0.0-alpha.3
?ionicplatform=android:1 OTS parsing error: Failed to convert WOFF 2.0 font to SFNT
?ionicplatform=android:1 Failed to decode downloaded font: http://localhost:8100/assets/fonts/ionicons.woff?v=3.0.0-alpha.3
?ionicplatform=android:1 OTS parsing error: incorrect file size in WOFF header

What behavior are you expecting?
Icons should work normally with this version
Steps to reproduce:

user this as ionicons path in package.json "git@github.com:travessey/ionicons.git#travessey
use one of the new icons and see the result. (big square and not an icon)
Use logo-deals as icon (this is one of the new icons)

<ion-icon name="logo-deals"></ion-icon>

Which @ionic/app-scripts version are you using?
0.0.47
ionic info:

Cordova CLI: 6.4.0
Ionic Framework Version: 2.0.0-rc.4
Ionic CLI Version: 2.1.17
Ionic App Lib Version: 2.1.7
Ionic App Scripts Version: 0.0.47
ios-deploy version: Not installed
ios-sim version: Not installed
OS: macOS Sierra
Node Version: v6.9.1
Xcode version: Xcode 8.2 Build version 8C38

Hi again.
When trying to narrow down on the problem I see that it looks like a problem with the latest version 0.0.47.
I tried to revert to version 0.0.45 and all worked ok.
Also when trying to work with 0.0.46 All worked ok.
It seems that 0.0.47 is causing this.

Anyone have an idea how to solve that?

@royipressburger,
Sorry, this doesn't seem like an app-scripts issue. I'm not sure there is anything we can do to help you here.
Thanks,
Dan

@danbucholtz Hello,
Thanks for you answer.
If this is the case, How can you explain that it worked fine on 0.0.46?

@danbucholtz Hello again.
I found the issue and its behind this commit.
I remove the copy of the ionic-angular fonts and all seems to work fine.
I think its because that ionic-angular/fonts contains some ionicons files which causes the the conflict.
What do you think?

@danbucholtz Hi,  Sorry for poping this up again
After some more investigations, I see that both ionic-app-scripts and ionic (here)
are copying items from ionicons.
Because ionic is copying fonts from ionicons, when install ionic you get in the fonts folder woff files. And because the current copy script is copying the fonts from ionic-angular/assets after the fonts from ionicons we get a result that installing ionicons in a project is useless since you always get the files from ionic-angular.
This causes error when trying to create/add custom icons for ionicons.
we need to choose when we want to copy the files from ionicons to avoid this.

@danbucholtz @jgw96 Hi guys,
Can someone open this issue.. I think it is still relevant..

@danbucholtz @jgw96 Hi guys,
Can someone open this issue.. I think it is still relevant..

@danbucholtz Ill be happy for a response. Thanks.

Sorry, I don't know too much about this. It seems outside of the scope of what we intend to support.
Customizing our icon set and then seeing issues with the wrong size is not something we can support at scale.
Thanks,
Dan


Kill rewards can be given after death but before respawn and therefor offset inventory.

Rewards for killing a player can be given after you die but before you respawn, causing all the items in your inventory to be shifted over a slot (or more, depending on how many items are given in the reward).
You can reproduce this by:

Joining a map with a specified kill reward.
Punching a player from the opposing team off into the void.

Evidence: http://youtu.be/HYX8b7pTVWg

@iEli2tyree011 How are you going to fix this issue? The killreward is currently given instantly on player kill, and it does not have a slot assignment. Are you going to delay the killreward until player respawn?

@SungMatt We can keep track of players and who is alive and who is dead. If they are dead, the kill reward can be scheduled to run in one tick. If the player is still dead, repeat. If the player logs off or switches teams, cancel.


Update artifacts

Closes #615.
Changes proposed in this PR:

Copy artifacts directory from contracts/v4main_postaudit branch, commit 26abee59da67f105166fca03aa8f16c1dcadc659
Update ERC721Template.setMetaData to include data_proofs argument

TODO:

[ ] Update ERC721Factory.startMultipleTokenOrder (remove amount, add v, r, s, and providerData)
[ ] Update ERC20Template.startOrder (remove amount, add v, r, s, and providerData)
[ ] Update ERC20Template.ProviderFees event (add providerData, v, r, s)
[ ] Add ERC20Template.getPermissions
[ ] Update ERC2TemplateEnterprise.ProviderFees event (add v, r, s, and providerData)
[ ] Add ERC20TemplateEnterprise.getPermissions
[ ] Update ERC20TemplateEnterprise.startOrder (remove amount, add v, r, s, and providerData)
[ ] Add ERC721Template.MetadataValidated event
[ ] Add ERC20Roles.getPermissions

I think publish flow needs to be updated as well, because it uses set_metadata function.

@mariacarmina Thanks for reviewing!  You're right that test_publish_flow uses asset.create which in turn calls set_metadata which I've already updated with the new data_proofs argument.

I accidentally approved. @DMats can you please make sure to copy the artifacts from barge, instead of ocean-contracts? It's much safer this way.

Sure I can do that.  Thanks for reviewing!


Identifiers validation failed for dataset Apoyo a las colecciones biológicas de la Facultad de Ciencias de la UNAM: Fase 1 (Coleóptera)

Identifier validation failed for the dataset Apoyo a las colecciones biológicas de la Facultad de Ciencias de la UNAM: Fase 1 (Coleóptera):

Crawler attempt: 104
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 5447
Cause: GBIF IDs hit maximum allowed - 50%, duplicates - 100%, total records count 5445, absent records count 5445
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3072862/step

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Apoyo a las colecciones biológicas de la Facultad de Ciencias de la UNAM: Fase 1 (Coleóptera) : https://doi.org/10.15468/rb2p5u.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Apoyo a las colecciones biológicas de la Facultad de Ciencias de la UNAM: Fase 1 (Coleóptera):

Crawler attempt: 107
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 5447
Cause: GBIF IDs hit maximum allowed - 50%, duplicates - 100%, total records count 5445, absent records count 5445
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3093756/step

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Apoyo a las colecciones biológicas de la Facultad de Ciencias de la UNAM: Fase 1 (Coleóptera) : https://doi.org/10.15468/rb2p5u.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.


Added stars.add and stars.remove

Added stars.add and stars.remove as defined in https://api.slack.com/methods#stars

Thanks, @ntratcliff. Here's the changes I've made https://github.com/os/slacker/compare/e074ed506880da5d2e4199840c5ea0a4810eb2d6...master


nsd: check config and zone files before start

This pull request is a followup and replacement to #9284. If this patch gets merged #9284 can be closed without merging. This patch is not squashed into one commit to preserve authorship.
The commit from #9284 makes the use of escaping in front of variable names unnecessary. This is how it should have been from the beginning, sadly the patch will break every NSD config out there.
The commit uses nsd-checkconf and nsd-checkzone to validate zone and config files before the systemd unit gets started. This will

make NSD fail on any errors. Till now it still started when errors where present in some zone files which made it possible to end up with a non working config without noticing it.
make deployments via nixops fail on zone errors.
fail if the old config style was detected. There is a special check to find out if escaped dollar signs are being used, in this case it shows an extra explanation besides NSDs error message.
give you a nice overview of you zone/config files and there check result in the journal.

I have also redone the deletion of old state files. The old way led to errors in some special cases.
All patches are tested and already integrated in my production systems without any problems.
@nbp @aszlig
Update: The latest commit from https://github.com/NixOS/nixpkgs/pull/9284 which adds documentation of the new config behavior has now been added as well.

:+1:

closed in favor of https://github.com/NixOS/nixpkgs/pull/12487


[Bug]: Links in * routes don't include the * part of the match/params

What version of Remix are you using?
1.1.3
What version of Node are you using? Minimum supported version is 14.
16.13.1
Steps to Reproduce
Create a single route named $slug.*.tsx with this code:
import { Link } from 'remix';
export default function Slug() {
    return (

                <Link to='a'>A</Link>

    );
}

Run Remix Dev and browse to http://localhost:3000/xxx
Notice the link href goes to http://localhost:3000/xxx/a which is correct
Now browse to http://localhost:3000/xxx/yyy
Notice the link href still goes to http://localhost:3000/xxx/a which is wrong
Expected Behavior
Links to a location with no "/" prefix are supposed to be relative to the last matched route.
I would expect this to include the "*" portion of the match, so in the above example
on http://localhost:3000/xxx the link should go to http://localhost:3000/xxx/a
and on http://localhost:3000/xxx/yyy the link should go to http://localhost:3000/xxx/yyy/a
Actual Behavior
The * portion of the route match is being ignored when constructing hrefs for links.

Hey, I took a quick look at this. I think this is maybe a react-router-dom bug?
So, internally, remix creates a RouterLink using react-router-dom useHref(to) for the location which looks like this:
let Link = React.forwardRef<HTMLAnchorElement, RemixLinkProps>(
  ({ to, prefetch = "none", ...props }, forwardedRef) => {
    let href = useHref(to);
    let [shouldPrefetch, prefetchHandlers] = usePrefetchBehavior(
      prefetch,
      props
    );
    return (
      <>
        <RouterLink
          ref={forwardedRef}
          to={to}
          {...props}
          {...prefetchHandlers}
        />
        {shouldPrefetch ? <PrefetchPageLinks page={href} /> : null}
      </>
    );
  }
);

Changing your example to the following
import { useEffect } from "react";
import { Link } from "@remix-run/react";
import { useHref } from "react-router-dom";
export default function Slug() {
    const to = useHref('a');

    useEffect(() => {
        console.log(to);
    }, []);
    return (

                <Link to='a'>A</Link>

    );
}

the console log prints out xxx/a both times. So it doesn't seem like remix is actually doing anything wrong, as where the link points to is determined by useHref. At least that's what it seems to be to me.
I guess the solution would be to change how remix determines where the link points to?
Anyone with more knowledge about remix, feel free to chime in.

Took a quick look at this. Looks like the current link component has no knowledge of what our current location is. It simply constructs a link using whatever we pass in for to.
Changing the link component to:
let Link = React.forwardRef<HTMLAnchorElement, RemixLinkProps>(
  ({ to, prefetch = "none", ...props }, forwardedRef) => {
    let { pathname }  = useLocation();
    let href = useHref(to);
    let [shouldPrefetch, prefetchHandlers] = usePrefetchBehavior(
      prefetch,
      props
    );
    return (
      <>
        <RouterLink
          ref={forwardedRef}
          to={`${pathname}/${to}`}
          {...props}
          {...prefetchHandlers}
        />
        {shouldPrefetch ? <PrefetchPageLinks page={href} /> : null}
      </>
    );
  }
);

fixes the issue. Not sure if there may be unintended consequences to this approach or if there is a better way to do this.
Question for people more familiar with remix:
If I do this, should I switch let href = useHref(to) to also use the current location? Since we use that href for the PrefetchPageLinks

This is intended behavior. See the test here.
https://github.com/remix-run/react-router/blob/f2178b9d093eb43f958815137067649c0335f1bd/packages/react-router-dom/__tests__/link-href-test.tsx#L321-L341


When requesting nodal stresses kernel dies + windows fatal exception with access violation

Hi all,
I was having some trouble post processing some results (writing to text files) with APDL (simulation time without postpro around 10 min, and with postpro 50 min), and I decided to give it a try and access the Ansys binary result file using pyansys. Before going hard core with my original model (around 0,5 million elements), I implemented the code for a smaller model, and everything went great. Hats off with the job done in developing pyansys!!!
The problem arrived when I tried the code with the original "big" model. First time I tried, the kernel in Spyder died and I got a huge message with "Windows fatal exception: access violation". After that I restarted the kernel manually and tried again, and this time the kernel died, and tried restarting by itself many times without success.
At first, I thought the problem was the amount of variables I've defined in my code. But when I just load the .rst file and try calling the nodal_stress() function, it crashes like before with the Windows fatal exception: access violation.
I have no idea where the problem may be. Any ideas?
Many thanks in advance.
PS: I tried adding screen shots of the error, but unsuccessfully.

Hello,
I'm guessing that this is the same issue as #216, which was recently patched in pyansys=0.40.0.  Could you please let me know what version you're running with:
import scooby
scooby.Report('pyansys')

Hi there,
Thank you very much for the fast reply. That was indeed the problem. After I updated to pyansys 0.40.0 the problem vanished.
I also read the issue #216, and it would be great if the reading speed would be optimized. Nevertheless great job with pyansys.

Thanks!


Reduce false positives for PointlessTypeBounds

fixes https://github.com/scapegoat-scala/scapegoat/issues/415

@mccartney could you please kindly check this out?


How to mine GPU with Intel HD GPU?

I ran with command line arguments
-l pool:port -u wallet.workerName -od 0
It crashed saying IOError
Any idea? How do I find out which device id to use?
Pretty sure that's my issue correct, or is Intel HD not supported?

I'm also running to the same problem.
If you run the -oi what it responds? Mine shows nothing, not even "0 cards found".
I thing there is a bug, like the OpenCL is kind of let aside.

I had my buddy with an AMD run it with similar command and still no luck. I just think I'm doing the parameters incorrect.

But when you run with -oi what returns?
Here I'm not receiving anything, not even a "0 cards found".

Intel HD is integrated graphics there is no dedicated gpu everything is done in the cpu.


Fix Math.asin error

Please check if the PR fulfills these requirements

[ ] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

最小案例：
class XXs extends Script {
onUpdate() {
this.entity.transform.rotate(new Vector3(1,0,0));
console.log(this.entity.transform.rotation.x+" "+this.entity.transform.rotation.y+" "+this.entity.transform.rotation.z);
}
}

https://github.com/galacean/engine/pull/1851


jsonapi: more flexible host matches

For jsonapi when querying on host, (what the browser extension does):

Search for exact matches (or, as the existing logic was doing, progressively more "base" subdomains - aka - foo.alpha.beta.com, then alpha.beta.com, then beta.com
Also search for the same matches, but looser.

This will help users, like myself, that store passwords in directories in broad categories.
This should preserve the existing logic in cases where "better" matches were found, but will still help the user when there are looser matches available that may be desired without having to manually search for the same hostname that was already queried.
For example, right now, the extension will not find colemickens/github.com when I am on https://github.com. With this PR, that is resolved.

Please let me know if it's more appropriate to change the browser extension side of things. cc: @Pharb

So, I personally see the risk that you can easily trick the user to enter credentials for a third party site. It is  also not clear to me, why colemickens/github.com is not found? Can you supply a unit test for this case?

can you rebase onto pr #977? Lets see if these cases are still considered.

#980 adds a test that should mimick the situation that you describe in the first post. Looks good for me. Can you check out what's the difference between the test and the problem statement @colemickens?


Update README.md

Codecov Report

Merging #173 (127a923) into main (b31d783) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #173   +/-   ##
=======================================
  Coverage   67.21%   67.21%
=======================================
  Files          14       14
  Lines        1449     1449
=======================================
  Hits          974      974
  Misses        371      371
  Partials      104      104

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 b31d783...127a923. Read the comment docs.


Bump to 4.6.0

Bumping to version 4.6.0.

Coverage remained the same at 63.345% when pulling ee5e6698816618eb9c3474ddc918617b7fc29458 on compulim:bump-4.6.0 into 8bde8d3bb14c6a576bb6f4b5755888f117f56c15 on microsoft:master.


Request: Add fine-tuning for the embedding model and creating a custom tokenizer from scratch

Request: Add fine-tuning for the embedding model and create a custom tokenizer.

Thank you for the request. There is a section that covers fine-tuning the embedding model if you check out the notebook here.


Bad math expression

Issue
I get the following error
spaceship_battery:37: bad math expression: operator expected at `47'

Screenshot
Provide a screenshot that show your issue

Environment
Operating system: Ubuntu 16.04 LTS
Terminal emulator: Terminator
ZSH version: zsh 5.1.1 (x86_64-ubuntu-linux-gnu)

Huh, I don't see that issue on my system (also ubuntu, zsh 5.1.1)

It definitely happened on one of my computers. On one of my other computers it didn't happen.

However, this fixed it for both. If this doesn't break it on your computer, it would definitely be nice to merge in.

Could you match my version of zsh and see what happens?

I'm using 5.1.1 and I see no issue

Are you using terminator?

I'm using terminator 0.98

I have no idea why this fixed it, but it did.

I don't think the choice of terminal should affect this, it should only be related to zsh version. You mentioned you have 2 machines, can you double check the version (echo $ZSH_VERSION) on the machine with the bug?

I will check tomorrow. Both my machines dotfiles are exactly identical. I use https://github.com/jamrizzi/dotcli to keep them in sync.

One other interesting thing to note is that the -lt flag works on the machine that spaceship does not work. But, in the spaceship, when I replaced -lt with <, it fixed it. Basically this is super confusing to debug.

I just disabled the whole battery function for myself. I think it's super weird to have my battery stats in my terminal like that anyways. I'm still not sure what the problem was, but it's super isolated and not really a problem for me now anyways.

I realize this is closed. But I wanted to comment for future me. Or others that google this. I am getting this and I am 99% certain it's because I have two batteries. The number that is reported in the error message is the percentage from the second battery.  If I new zsh more, I would submit a patch, but I don't. I'm happy to help test if someone else wants to take a shot

Example of the problem and example of the output that two batteries gives.
~ acpi -b | awk '{print tolower($3)}' | tr -d '%[,;'
unknown
charging
spaceship_battery:40: bad math expression: operator expected at `23'
~ acpi -b | awk '{print $4}' | tr -d '%[,;]'
86
23
spaceship_battery:40: bad math expression: operator expected at `23'
~

Oh dang, good fine. I have two batteries also.

I am having the same issue on my laptop with two batteries connected.

@n2o What laptop is that? Mac? Is the on the current version of spaceship prompt?
If you're on macOS, can you copy the output of pmset -g batt please?

Laptop: Thinkpad T450S
OS: Arch Linux
Shell: urxvt
Spaceship-Version: 3.8.1
Batteries: 2
Each command ends with this message and does not show the normal char-symbol:
spaceship_battery:44: bad math expression: operator expected at `99'

Here is a short video of it
term.zip

This means line 44 inside spaceship_battery function, so it's:
elif [[ $battery_percent -lt $SPACESHIP_BATTERY_THRESHOLD ]]; then

Could you paste the output of upower and upower -e please?

λ upower -e
/org/freedesktop/UPower/devices/line_power_AC
/org/freedesktop/UPower/devices/battery_BAT0
/org/freedesktop/UPower/devices/battery_BAT1
/org/freedesktop/UPower/devices/DisplayDevice

Could you also do that for upower -i /org/freedesktop/UPower/devices/battery_BAT0 please?

Sure
λ upower -i /org/freedesktop/UPower/devices/battery_BAT0
  native-path:          BAT0
  vendor:               SANYO
  model:                45N1773
  serial:               20253
  power supply:         yes
  updated:              Di 04 Dez 2018 12:51:48 CET (46 seconds ago)
  has history:          yes
  has statistics:       yes
  battery
    present:             yes
    rechargeable:        yes
    state:               fully-charged
    warning-level:       none
    energy:              16,64 Wh
    energy-empty:        0 Wh
    energy-full:         16,97 Wh
    energy-full-design:  23,2 Wh
    energy-rate:         0 W
    voltage:             12,244 V
    percentage:          98%
    capacity:            73,1466%
    technology:          lithium-ion
    icon-name:          'battery-full-charged-symbolic'
  History (charge):
<PHONE_NUMBER>	98,000	fully-charged

The next step I'd do is this -
On line 75 of sections/battery.zsh there's this part:
# Change color based on battery percentage
  if [[ $battery_percent == 100 || $battery_status =~ "(charged|full)" ]]; then
    battery_color="green"
  elif [[ $battery_percent -lt $SPACESHIP_BATTERY_THRESHOLD ]]; then
    battery_color="red"
  else
    battery_color="yellow"
  fi

If you add set -x just before that and set +x right after it and open a new shell (or just run zsh -l), you will see the actual commands that are being executed. You might see what happened just before the error happened.

Okay, did this and this is the output:
+spaceship_battery:44> [[ $'97\n96' == 100 || $battery_status -regex-match "(charged|full)" ]]
+spaceship_battery:46> [[ $'97\n96' -lt 10spaceship_battery:46: bad math expression: operator expected at `96'
 ]]

~ +spaceship_battery:44> [[ $'97\n96' == 100 || $battery_status -regex-match "(charged|full)" ]]
+spaceship_battery:46> [[ $'97\n96' -lt 10spaceship_battery:46: bad math expression: operator expected at `96'

$ upower -e | grep battery | head -1
/org/freedesktop/UPower/devices/battery_BAT0

Adding set -x at the beginning of the function in battery.zsh and set -x to the end produces this:
+spaceship_battery:3> [[ true == false ]]
+spaceship_battery:5> local battery_data battery_percent battery_status battery_color
+spaceship_battery:7> spaceship::exists pmset
+spaceship::exists:1> command -v pmset
+spaceship_battery:15> spaceship::exists acpi
+spaceship::exists:1> command -v acpi
+spaceship_battery:16> battery_data=+spaceship_battery:16> acpi -b
+spaceship_battery:16> battery_data=$'Battery 0: Unknown, 97%\nBattery 1: Unknown, 98%'
+spaceship_battery:19> [[ -z $'Battery 0: Unknown, 97%\nBattery 1: Unknown, 98%' ]]
+spaceship_battery:21> battery_percent=+spaceship_battery:21> echo $'Battery 0: Unknown, 97%\nBattery 1: Unknown, 98%'
+spaceship_battery:21> battery_percent=+spaceship_battery:21> awk '{print $4}'
+spaceship_battery:21> battery_percent=$'97%\n98%'
+spaceship_battery:24> [[ $'97%\n98%' == 0%, ]]
+spaceship_battery:26> battery_status=+spaceship_battery:26> echo $'Battery 0: Unknown, 97%\nBattery 1: Unknown, 98%'
+spaceship_battery:26> battery_status=+spaceship_battery:26> awk '{print tolower($3)}'
+spaceship_battery:26> battery_status=$'unknown,\nunknown,'
+spaceship_battery:41> battery_percent=+spaceship_battery:41> echo $'97%\n98%'
+spaceship_battery:41> battery_percent=+spaceship_battery:41> tr -d '%[,;]'
+spaceship_battery:41> battery_percent=$'97\n98'
+spaceship_battery:44> [[ $'97\n98' == 100 || $battery_status -regex-match "(charged|full)" ]]
+spaceship_battery:46> [[ $'97\n98' -lt 10spaceship_battery:46: bad math expression: operator expected at `98'

I don't know why I always assumed that your system used upower instead of acpi command...
This definitely helped though :)
Just pushed MR #583 that should fix this for you.

I would still prefer a solution similar to my PR ( #365 ) that I made some time back. The title should probably be updated. Here is a second attempt. This one sums the available mAh, and divides it by the total mAh and uses that as the percentage.

IMO it makes sense. Either average or Max of the available batteries.
But this is a feature. I think it's important to fix the bug that exists, unrelated to enhancing battery display.


Update build_podspec script & added SwiftNIOHPACK Pod

SwiftNIOHTTP2 has a dependency on internal target SwiftNIOHPACK so validating the podspec was failing
Updated the script to allow for the generation of both SwiftNIOHTTP2.podspec & SwiftNIOHPACK .podspec
In NIOHTTP2StreamChannel.swift, it imports NIOConcurrencyHelpers which was not added as a dependency explicitly. Added the dependency which allowed the successful validation of the SwiftNIOHTTP2 Pod.

Cocoapods
SwiftNIOHTTP2
SwiftNIOHPACK
Newly created Pods from Release 1.9.1 - still need to add the other maintainers as Pod owners!

@swift-nio-bot test this please


Material Sandbox prints the wrong file it couldn't open

Describe the bug
When running material_sandbox, if it fails to load any models (or attempts to load incorrectly ordered options as files) it reports that it can't load the first model regardless of which actually failed.
To Reproduce
Simply run:
out/cmake-release/samples/Release/material_sandbox.exe assets/models/sphere/sphere.obj --ibl=samples/envs/pillars

or your platform equivalent. Note the out of order option. The output will be:
file assets/models/sphere/sphere.obj not found!

Expected behavior
The output should be:
file --ibl=samples/envs/pillars not found!

which makes the situation much more clear (though is still suboptimal since it didn't parse the argument).
Desktop (please complete the following information):

OS: Windows 10
GPU: RTX 2080 Ti
Backend: OpenGL and Vulkan

Additional context
Add any other context about the problem here.

Doing a search for the offending line of code reveals it's in a bunch of samples. I'll create a PR that addresses them.


Introduce ProgressBar callback

Useful when training time between epochs is quite long.

@dnouri Do you think this is the best way to handle this? I also experimented with having only one progress bar so that they don't stack when in jupyter notebook mode, however it is quite hard to re-use a progress bar instance and I ran into all sorts of problems.

@ottonemo Could you add an example (notebook or not)?


Get a feel for how close we're getting to completion

We've got quite a few parts working now but also still quite a few things left to do!
I think there are two levels of "complete" for this project:
level 1: join the sciencemesh with a Nextcloud server

when initiating sharing in the Nextcloud GUI (from share-with or from public-link), the "user@host" string is matched to a user on Sciencemesh, and NC calls Reva to send the share
when a share comes in via Reva, it becomes visible in Nextcloud
the user sees a notification about the new share
not sure what to do about the 'accept / decline', but we can say that to decline is to delete
accepting the share should send a notification (n->r->r->n)
webdav mount into the recipient's nextcloud should work via the recipient's reva to the sender's reva to the sender's nextcloud
unshare should work (n->r->r->n)

level 2: support all aspects of reva's api

use nextcloud as the user backend
use nextcloud as the storage
use nextcloud as the shares backend
implement all the methods that reva exposes

[ ] n->r->r->n minimal contact in #35
[ ] check webdav fetch
[ ] check accept notification
[ ] check unshare and back to starting positions
[ ] OCM test suite in reva CI
[ ] all outstanding PRs merged (cs3-build, node-cs3, reva, ocm-api)
[ ] test instance running live e.g. cloud.pondersource.org, mesh.pondersource.org
[ ] full reva-cli test suite to make sure we're also ready for Phase II


fix-updating-commit-status

Changelog
Fix updating commit status when local repo is on another branch
Fix #44
Instead of relying on the local repo to lookup the commit SHA,
use the github API response.  This allows for updating the commit status
when the local repo is out of sync with the remote server.

Coverage decreased (-0.0%) to 99.58% when pulling e5e05a0e86ff2a94b1c82cc27224e5c639a1ce71 on fix-updating-commit-status into 04f7fc4d43927f5a6470626f43b831efb13fe412 on master.


Add information about "god mode" attack to Security Model page

Attack description:
https://gist.github.com/john-light/80f5d30b93b052f63fab691e400de521

This is so fun. I've got a couple other small updates there, I'll try to roll it in


Support loading databases from disk

This PR doesn't work in its current state:
$ WASMTIME_BACKTRACE_DETAILS=1 extism call --input 'abcdefg' out/example.wasm count_vowels --wasi --allow-path /path/to/your/

extism_runtime::sdk ERROR 2023-04-13T00:00:10.833237648+09:00 - Call: error while executing at wasm backtrace:
    0: 0x1e169e - <unknown>!abort
    1: 0x1e1e2d - <unknown>!find_relative
    2: 0x1e1f73 - <unknown>!lstat
    3: 0x6a2d3 - <unknown>!appendOnePathElement
    4: 0x12c91 - <unknown>!appendAllPathElements
    5: 0x12a6a - <unknown>!unixFullPathname
    6: 0x6c46c - <unknown>!sqlite3OsFullPathname
    7: 0x6c8b7 - <unknown>!sqlite3PagerOpen
    8: 0x5eb98 - <unknown>!sqlite3BtreeOpen
    9: 0x5b7d8 - <unknown>!openDatabase
   10: 0x5af1e - <unknown>!sqlite3_open
   11: 0x1343 - <unknown>!count_vowels

Caused by:
    wasm trap: wasm `unreachable` instruction executed
Traceback (most recent call last):
  File "/home/eni/.local/bin/extism", line 607, in <module>
    main()
  File "/home/eni/.local/bin/extism", line 602, in main
    r = plugin.call(args.function, input, parse=None)
  File "/home/eni/.local/lib/python3.10/site-packages/extism/extism.py", line 378, in call
    self._check_error(
  File "/home/eni/.local/lib/python3.10/site-packages/extism/extism.py", line 337, in _check_error
    raise Error(_ffi.string(error).decode())
extism.extism.Error: Call failed

Caused by:
    0: error while executing at wasm backtrace:
           0: 0x1e169e - <unknown>!abort
           1: 0x1e1e2d - <unknown>!find_relative
           2: 0x1e1f73 - <unknown>!lstat
           3: 0x6a2d3 - <unknown>!appendOnePathElement
           4: 0x12c91 - <unknown>!appendAllPathElements
           5: 0x12a6a - <unknown>!unixFullPathname
           6: 0x6c46c - <unknown>!sqlite3OsFullPathname
           7: 0x6c8b7 - <unknown>!sqlite3PagerOpen
           8: 0x5eb98 - <unknown>!sqlite3BtreeOpen
           9: 0x5b7d8 - <unknown>!openDatabase
          10: 0x5af1e - <unknown>!sqlite3_open
          11: 0x1343 - <unknown>!count_vowels
    1: wasm trap: wasm `unreachable` instruction executed


Remove offer create view and form (they were moved to Angular)

Codecov Report

Merging #974 into master will increase coverage by 1.02%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #974      +/-   ##
==========================================
+ Coverage   87.69%   88.71%   +1.02%
==========================================
  Files         110      110
  Lines        2884     2828      -56
  Branches       23       23
==========================================
- Hits         2529     2509      -20
+ Misses        353      317      -36
  Partials        2        2

Impacted Files
Coverage Δ

backend/apps/volontulo/forms.py
98.3% <ø> (+15.17%)
:arrow_up:

backend/apps/volontulo/views/offers.py
74.03% <100%> (+11.15%)
:arrow_up:

backend/apps/volontulo/utils.py
96.15% <100%> (+2.82%)
:arrow_up:

Continue to review full report at Codecov.

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


Canned queries with named parameters fail with error against SQLite 3.46.0

Reported on Discord: https://discord.com/channels/823971286308356157/823971286941302908/1248924498128932914
I managed to replicate it locally using this trick https://til.simonwillison.net/sqlite/sqlite-version-macos-python
DYLD_LIBRARY_PATH=$PWD datasette fixtures.db -c datasette.yml --pdb

Where datasette.yml has this:
databases:
  fixtures:
    queries:
      demo: select * from sqlite_master where tbl_name = :table

  File "/opt/homebrew/Caskroom/miniconda/base/lib/python3.10/site-packages/datasette/utils/__init__.py", line 1147, in derive_named_parameters
    return [row["p4"].lstrip(":") for row in results if row["opcode"] == "Variable"]
  File "/opt/homebrew/Caskroom/miniconda/base/lib/python3.10/site-packages/datasette/utils/__init__.py", line 1147, in <listcomp>
    return [row["p4"].lstrip(":") for row in results if row["opcode"] == "Variable"]

Within the --pdb debugger I could see this:
(Pdb) pprint([dict(r) for r in results.rows])
[{'addr': 0,
  'comment': None,
  'opcode': 'Init',
  'p1': 0,
  'p2': 13,
  'p3': 0,
  'p4': None,
  'p5': 0},
 {'addr': 1,
  'comment': None,
  'opcode': 'OpenRead',
  'p1': 0,
  'p2': 1,
  'p3': 0,
  'p4': '5',
  'p5': 0},
 {'addr': 2,
  'comment': None,
  'opcode': 'Rewind',
  'p1': 0,
  'p2': 12,
  'p3': 0,
  'p4': None,
  'p5': 0},
 {'addr': 3,
  'comment': None,
  'opcode': 'Column',
  'p1': 0,
  'p2': 2,
  'p3': 1,
  'p4': None,
  'p5': 0},
 {'addr': 4,
  'comment': None,
  'opcode': 'Ne',
  'p1': 2,
  'p2': 11,
  'p3': 1,
  'p4': 'BINARY-8',
  'p5': 82},
 {'addr': 5,
  'comment': None,
  'opcode': 'Column',
  'p1': 0,
  'p2': 0,
  'p3': 3,
  'p4': None,
  'p5': 0},
 {'addr': 6,
  'comment': None,
  'opcode': 'Column',
  'p1': 0,
  'p2': 1,
  'p3': 4,
  'p4': None,
  'p5': 0},
 {'addr': 7,
  'comment': None,
  'opcode': 'Column',
  'p1': 0,
  'p2': 2,
  'p3': 5,
  'p4': None,
  'p5': 0},
 {'addr': 8,
  'comment': None,
  'opcode': 'Column',
  'p1': 0,
  'p2': 3,
  'p3': 6,
  'p4': None,
  'p5': 0},
 {'addr': 9,
  'comment': None,
  'opcode': 'Column',
  'p1': 0,
  'p2': 4,
  'p3': 7,
  'p4': None,
  'p5': 0},
 {'addr': 10,
  'comment': None,
  'opcode': 'ResultRow',
  'p1': 3,
  'p2': 5,
  'p3': 0,
  'p4': None,
  'p5': 0},
 {'addr': 11,
  'comment': None,
  'opcode': 'Next',
  'p1': 0,
  'p2': 3,
  'p3': 0,
  'p4': None,
  'p5': 1},
 {'addr': 12,
  'comment': None,
  'opcode': 'Halt',
  'p1': 0,
  'p2': 0,
  'p3': 0,
  'p4': None,
  'p5': 0},
 {'addr': 13,
  'comment': None,
  'opcode': 'Transaction',
  'p1': 0,
  'p2': 0,
  'p3': 35,
  'p4': '0',
  'p5': 1},
 {'addr': 14,
  'comment': None,
  'opcode': 'Variable',
  'p1': 1,
  'p2': 2,
  'p3': 0,
  'p4': None,
  'p5': 0},
 {'addr': 15,
  'comment': None,
  'opcode': 'Goto',
  'p1': 0,
  'p2': 1,
  'p3': 0,
  'p4': None,
  'p5': 0}]

Note that the Variable opcode now has p4 as None - and the name of the variable no longer appears in any of the opcodes!

Code at fault: https://github.com/simonw/datasette/blob/7437d40e5dd4d614bb769e16c0c1b96c6c19647f/datasette/utils/init.py#L1137-L1150

The key problem here is that opcodes are not a stable feature of SQLite, so it was always risk to attempt to use them in this way.

We need to ensure SQLite 3.46.0 is covered in the new tests here:

#2352

Posted about this on the SQLite forum - https://sqlite.org/forum/forumpost/0adbc56447 - but since opcodes are an undocumented and unsupported interface I don't expect them to fix it.

This mechanism here was already supposed to catch things if SQLite broke the mechanism I was using:
https://github.com/simonw/datasette/blob/7437d40e5dd4d614bb769e16c0c1b96c6c19647f/datasette/utils/__init__.py#L1149-L1150
But it didn't think to catch AttributeError.

Here's the macOS SQLite 3.46.0 libsqlite3.0.dylib I was using: https://static.simonwillison.net/static/2024/libsqlite3.0.dylib

Here's the commit that removed this feature: https://sqlite.org/src/info/dd5977c9a8a418be
Via https://sqlite.org/forum/forumpost/1cafc721009cef7f

I manually tested the patch to 0.64.x like this:
DYLD_LIBRARY_PATH=sqlite-3.46.0 datasette fixtures.db -m issue-2353.yaml -p 8034

Then visited http://<IP_ADDRESS>:8034/fixtures/demo?table=facetable and it worked.

Here's the full set of changes going out in 0.64.7: https://github.com/simonw/datasette/compare/0.64.6...0.64.7

Blogged about the release here: https://simonwillison.net/2024/Jun/12/datasette-0647/

Need to forward-port this to Datasette 1.0.

Oh it's in Datasette 1.0 already, just not yet in a release: d118d5c5bbb675f35baa5c376ee297b510dccfc0


cannot set 3 different labels on the same image

I'm trying to label 3 different labels to the same image, but all of them appears to be right.

works now


nixos.moonraker: fix config options location

Description of changes
Old config locations were deprecated, https://moonraker.readthedocs.io/en/latest/configuration/#option-moved-deprecations.
Also, this adds PrivateTmp (for logs).

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

#185599 also moves the configs, but no committer came to merge :(

@zhaofengli
Oof :(
Could you also add PrivateTmp=true to your PR? It's creates logs in /tmp.

It's @vtuan10's PR. Maybe you can still keep the PrivateTmp here, I don't mind either way.

Thanks for the PR! Happy to close mine, as this also adds PrivateTmp 😊
If possible, could you add me as maintainer as well?


after import styled from "styled-components" ERROR Module not found

Environment
Styled-components: '3.4.2'
overlay: '1.0.0',
npm: '5.6.0',
ares: '1.10.1-DEV',
cldr: '32.0',
http_parser: '2.8.0',
icu: '60.1',
modules: '57',
napi: '3',
nghttp2: '1.32.0',
node: '8.11.3',
openssl: '1.0.2o',
tz: '2017c',
unicode: '10.0',
uv: '1.19.1',
v8: '6.2.414.54',
zlib: '1.2.11'
Reproduction
just "import styled from "styled-components";" in any component and try to "npm run build" or paste this component in an project you have set up.
import * as React from "react";
import styled from "styled-components";

export interface Props
{

}

export interface State
{

}

const list = [
    {
        prize: "€500"
    },
    {
        prize: "€250"
    },
    {
        prize: "10 Free Spins"
    },
];

const MyStyle = styled.td`
color: green;
`;

export class RaffleComponent extends React.Component<Props, State>
{
	render()
	{

		return (

                RAFFLE

                       {list.map(item =>

                        <MyStyle>{item.prize}</MyStyle>

                    )}

Random {list.length} players get one of the rewards

		)
	}

}

and run "npm run build"
Expected Behavior
expecting webpack to build and start the project
Actual Behavior
throws two errors
ERROR in ./node_modules/prop-types/index.js
Module not found: Error: Can't resolve './factoryWithTypeCheckers' in 'C:\Users\****\code\clientmodule\node_modules\prop-types'

and
ERROR in ./node_modules/styled-components/dist/styled-components.browser.esm.js
Module not found: Error: Can't resolve 'fbjs/lib/hyphenateStyleName' in 'C:\Users\JohanJonsson\code\clientmodule\node_modules\styled-components\dist'

i have been trying to google for a solution but found nothing. Anybody have a clue?

all i needed was to add .js to my extension resolve in webpack.config.js


ENOENT: no such file or directory, stat '/home/xxx/.steampath'

How did you install the Amplify CLI?
yarn and curl
If applicable, what version of Node.js are you using?
19.7.0
Amplify CLI Version
11.0.3
What operating system are you using?
Ubuntu 20.04.5
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes
Describe the bug
I type in amplify init then enter a default name or don't enter a default name and this error pops up
Project information
| Name: dallas
| Environment: dev
| Default editor: Visual Studio Code
🛑 ENOENT: no such file or directory, stat '/home/justin/.steampath'

Expected behavior
I expect it to continue to initialize
Reproduction steps
type amplify init
enter a default project name
the error pops up
Project Identifier
It was empty
Log output

# Put your logs below this line

2023-04-07T02:02:53.453Z|info : amplify plugin core scan
2023-04-07T02:02:53.485Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2023-04-07T02:03:43.523Z|info : amplify help core
2023-04-07T02:07:39.255Z|info : amplify configure core
2023-04-07T02:07:39.287Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2023-04-07T02:16:17.465Z|info : amplify-provider-awscloudformation.system-config-manager.setProfile.credentialsFilePathExists(["/home/justin/.aws/credentials"])
2023-04-07T02:16:17.467Z|info : amplify-provider-awscloudformation.system-config-manager.makeFileOwnerReadWrite(["/home/justin/.aws/credentials"])
2023-04-07T02:16:17.469Z|info : amplify-provider-awscloudformation.system-config-manager.setProfile.configFilePathExists(["/home/justin/.aws/config"])
2023-04-07T02:16:17.470Z|info : amplify-provider-awscloudformation.system-config-manager.makeFileOwnerReadWrite(["/home/justin/.aws/config"])
2023-04-07T02:16:17.471Z|info : amplify-provider-awscloudformation.system-config-manager.setProfile.writeCredentialsFilePath(["/home/justin/.aws/credentials"])
2023-04-07T02:17:11.318Z|info : amplify help core
2023-04-07T02:17:48.612Z|info : amplify init core
2023-04-07T02:17:48.643Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2023-04-07T02:18:12.618Z|error : ENOENT: no such file or directory, stat '/home/justin/.steampath'
UnknownNodeJSFault: ENOENT: no such file or directory, stat '/home/justin/.steampath'
2023-04-07T02:18:20.337Z|info : amplify init core
2023-04-07T02:18:20.368Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2023-04-07T02:18:24.951Z|error : ENOENT: no such file or directory, stat '/home/justin/.steampath'
UnknownNodeJSFault: ENOENT: no such file or directory, stat '/home/justin/.steampath'
2023-04-07T02:18:39.783Z|info : amplify init core
2023-04-07T02:18:39.813Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2023-04-07T02:18:42.407Z|error : ENOENT: no such file or directory, stat '/home/justin/.steampath'
UnknownNodeJSFault: ENOENT: no such file or directory, stat '/home/justin/.steampath'
2023-04-07T02:19:49.753Z|info : amplify configure core
2023-04-07T02:19:49.783Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2023-04-07T02:21:26.279Z|info : amplify-provider-awscloudformation.system-config-manager.setProfile.credentialsFilePathExists(["/home/justin/.aws/credentials"])
2023-04-07T02:21:26.280Z|info : amplify-provider-awscloudformation.system-config-manager.makeFileOwnerReadWrite(["/home/justin/.aws/credentials"])
2023-04-07T02:21:26.282Z|info : amplify-provider-awscloudformation.system-config-manager.setProfile.configFilePathExists(["/home/justin/.aws/config"])
2023-04-07T02:21:26.282Z|info : amplify-provider-awscloudformation.system-config-manager.makeFileOwnerReadWrite(["/home/justin/.aws/config"])
2023-04-07T02:21:26.283Z|info : amplify-provider-awscloudformation.system-config-manager.setProfile.writeCredentialsFilePath(["/home/justin/.aws/credentials"])
2023-04-07T02:21:32.727Z|info : amplify init core
2023-04-07T02:21:32.759Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2023-04-07T02:21:35.577Z|error : ENOENT: no such file or directory, stat '/home/justin/.steampath'
UnknownNodeJSFault: ENOENT: no such file or directory, stat '/home/justin/.steampath'
2023-04-07T02:23:30.889Z|info : amplify init core
2023-04-07T02:23:30.921Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2023-04-07T02:23:32.499Z|error : ENOENT: no such file or directory, stat '/home/justin/.steampath'
UnknownNodeJSFault: ENOENT: no such file or directory, stat '/home/justin/.steampath'
2023-04-07T02:24:03.499Z|info : amplify init core
2023-04-07T02:24:03.531Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2023-04-07T02:24:05.086Z|error : ENOENT: no such file or directory, stat '/home/justin/.steampath'
UnknownNodeJSFault: ENOENT: no such file or directory, stat '/home/justin/.steampath'
2023-04-07T02:25:45.753Z|info : amplify plugin core scan
2023-04-07T02:25:45.784Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2023-04-07T02:25:59.515Z|info : amplify configure core
2023-04-07T02:25:59.545Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2023-04-07T02:26:52.962Z|info : amplify-provider-awscloudformation.system-config-manager.setProfile.credentialsFilePathExists(["/home/justin/.aws/credentials"])
2023-04-07T02:26:52.963Z|info : amplify-provider-awscloudformation.system-config-manager.makeFileOwnerReadWrite(["/home/justin/.aws/credentials"])
2023-04-07T02:26:52.964Z|info : amplify-provider-awscloudformation.system-config-manager.setProfile.configFilePathExists(["/home/justin/.aws/config"])
2023-04-07T02:26:52.964Z|info : amplify-provider-awscloudformation.system-config-manager.makeFileOwnerReadWrite(["/home/justin/.aws/config"])
2023-04-07T02:26:52.964Z|info : amplify-provider-awscloudformation.system-config-manager.setProfile.writeCredentialsFilePath(["/home/justin/.aws/credentials"])
2023-04-07T02:26:57.814Z|info : amplify init core
2023-04-07T02:26:57.845Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2023-04-07T02:27:01.626Z|error : ENOENT: no such file or directory, stat '/home/justin/.steampath'
UnknownNodeJSFault: ENOENT: no such file or directory, stat '/home/justin/.steampath'
2023-04-07T02:30:34.131Z|info : amplify version core
2023-04-07T02:31:02.952Z|info : amplify configure core
2023-04-07T02:31:02.983Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2023-04-07T02:31:35.666Z|info : amplify-provider-awscloudformation.system-config-manager.setProfile.credentialsFilePathExists(["/home/justin/.aws/credentials"])
2023-04-07T02:31:35.668Z|info : amplify-provider-awscloudformation.system-config-manager.makeFileOwnerReadWrite(["/home/justin/.aws/credentials"])
2023-04-07T02:31:35.671Z|info : amplify-provider-awscloudformation.system-config-manager.setProfile.configFilePathExists(["/home/justin/.aws/config"])
2023-04-07T02:31:35.672Z|info : amplify-provider-awscloudformation.system-config-manager.makeFileOwnerReadWrite(["/home/justin/.aws/config"])
2023-04-07T02:31:35.673Z|info : amplify-provider-awscloudformation.system-config-manager.setProfile.writeCredentialsFilePath(["/home/justin/.aws/credentials"])
2023-04-07T02:31:44.411Z|info : amplify init core
2023-04-07T02:31:44.441Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2023-04-07T02:31:51.292Z|error : ENOENT: no such file or directory, stat '/home/justin/.steampath'
UnknownNodeJSFault: ENOENT: no such file or directory, stat '/home/justin/.steampath'
2023-04-07T02:33:25.129Z|info : amplify version core
2023-04-07T02:35:29.553Z|info : amplify diagnose core  {"send-report":true,"yes":false}
2023-04-07T02:35:29.584Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hey @justingatlin-ny :wave: thanks for raising this! This error seems a bit strange, what is the directory path you're working in (i.e. pwd)? Do you experience this regardless of the directory you are working in?

I haven’t tried changing directories but I did try installing and initializing with yarn global and with cURL and same error.
Sent from my iPhone
On Apr 7, 2023, at 1:11 PM, josef @.***> wrote:

Hey @justingatlin-ny 👋 thanks for raising this! This error seems a bit strange, what is the directory path you're working in (i.e. pwd)? Do you experience this regardless of the directory you are working in?
—
Reply to this email directly, view it on GitHub https://github.com/aws-amplify/amplify-cli/issues/12406#issuecomment-1500473822 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AHTDW7R46YC27IGRXCQR353XABDC5ANCNFSM6AAAAAAWWDRFQI .
You are receiving this because you were mentioned. https://github.com/notifications/beacon/AHTDW7VT6AH7FFARDQNXZFDXABDC5A5CNFSM6AAAAAAWWDRFQKWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSZN5U54.gif Message ID: @.***>

Changing the directory solved the problem.  I can amplify init now. Thanks.


Fix context menu displayFn call when right click on grid row that does not have a store record

As reported by client:
If a user right clicks on grouped line popup, app returns error in console and displays standard context menu.

Closed.  Not a framework issue.  Applications using displayFn need to null check record.


HTML5 Color picker is broken

Operating system: macOS Sierra 10.12.5 (16F73)
Browser: Google Chrome 58.0.3029.110 (64-bit)
Bootstrap: v4.0.0-alpha.6

If I remove the class "form-control" from the input, it works as intended, but with the class the input just looks like a line.
You can reproduce it even in the samples page: https://v4-alpha.getbootstrap.com/components/forms/#textual-inputs

I forgot to mention that the line doesn't even change color.

I tried and it works on Mozilla Firefox 54.0 (64-bit) but in Safari 10.1.1 (12603.2.4) it looks just like a input text (I think Safari doesn't support color pickers yet).

Closing as duplicate of #18786.


UNREACHABLE: User of a constant expression was a constant

The relatively simple kernel below produces this error message:
User of a constant expression was a constant!
UNREACHABLE executed at ../../lib/UndoGetElementPtrConstantExprPass.cpp:74!

#define WGSIZE 4
__attribute__((reqd_work_group_size(WGSIZE, 1, 1)))
kernel void foo(global float *output)
{
  local float scratch[WGSIZE];

  uint lid = get_local_id(0);
  scratch[lid] = 0.f;
  barrier(CLK_LOCAL_MEM_FENCE);

  float tmp = 0.f;
  for (uint k = 0; k < WGSIZE; k++)
    tmp += scratch[k];

  output[0] = tmp;
}

Hey James, you've encovered one of the... less well tested parts of the compiler - well done!
What a think is happening is:

scratch gets moved to a global variable as that is how Vulkan represents local memory.
the loop gets unrolled
that means scratch[k], k is a constant
and we had a ton of issues whereby LLVM will turn scratch[1] -> a GEP constant expression, which isn't allowed in Vulkan

I'm not certain what the fix is off the top of my head, but I'll see if I can look into it!

Working as 00e7a58a2834ee938830f82b42a0692fc2232511 at least.


pick-up 1.3.2 bug fixes

What type of PR is this?

Uncomment only one  /kind line, and delete the rest.
For example, > /kind bug would simply become: /kind bug

/kind bug
/kind cleanup
/kind failing-test
/kind enhancement
/kind documentation
/kind code-refactoring

What does this PR do / why we need it:
Picks up bug fixes for v1.3.2 from the rhos-v1.3 branch of argocd-operator
Have you updated the necessary documentation?

[ ] Documentation update is required by this PR.
[ ] Documentation has been updated.

Which issue(s) this PR fixes:
Fixes #?
Test acceptance criteria:

[ ] Unit Test
[ ] E2E Test

How to test changes / Special notes to the reviewer:

Hi @jaideepr97 , Did you check if any of these changes have updates/modifications to CSV, CRD or other manifest files ?

@iam-veeramalla
Yes, neither of the 2 upstream commits included in this change involve any manifest changes

awesome, lets keep this PR open and update it when all the changes for 1.3 are done ?

@iam-veeramalla Sure
But I think for 1.3.2, from an operator code perspective I don't think there are any more pending changes
All other changes are in cpaas

/LGTM
/approve


generated xcodeproj failed!

bazel build success:

but tulsi generated xcodeproj and run failed:
In @tulsi//:tulsi/tulsi_aspects.bzl%tulsi_outputs_aspect aspect on apple_framework_packaging rule

I don't think we can see the full error msg in your screenshot. Mind checking the build log in Xcode (cmd+9 then select the most recent build)?.
Also, rules_ios has it's own project generator and we prioritize building features using that as a reference. AFAIK folks haven't been testing to see how compatible with Tulsi things are.
Feel free to test it and let us know how it goes! See: https://github.com/bazel-ios/rules_ios/blob/master/rules/xcodeproj.bzl

Sorry, I do't know how to generated project by rules_ios,
Do we have a document for how you generated xcode project?

You do that by invoking bazel run in xcodeproj targets, you can see a few examples here: https://github.com/bazel-ios/rules_ios/blob/master/tests/ios/xcodeproj/BUILD.bazel
I just did a quick scan in the repo and I guess we don't have a more detailed documentation for that rule! We should definitely add it!

cc @gyfelton in case what I said is false, AFAIK we don't have docs for that right?

Based on the screenshot it looks like XCHammer related? I think rules_ios needs to be added into XCHammer and Tulsi still

Thank you!
Use xcodeproj generated success!
But, how to fixed the info.plist?
ios_application(
    name = "app",
    bundle_id = "cc.gle.app",
    srcs = glob([
        "iOSApp/*.swift",
    ]),
    resources = [
        "iOSApp/Base.lproj/LaunchScreen.storyboard",
    ],
    swift_version = "5.0",
    visibility = ["//visibility:public"],
    families = [
        "iphone",
        "ipad",
    ],
    minimum_os_version = "9.0",
    infoplists = [":iOSApp/Info.plist"],
    deps = [
]
)

https://github.com/bazel-ios/rules_ios/blob/8682f956e6668b18889e01c21a8ff4114fa88d7c/rules/xcodeproj.bzl#L708-L710
Need copy my :iOSApp/Info.plist into "$BAZEL_STUBS_DIR/Info-stub.plist" ?

I believe the Info.plist used in the generated project is a stub/fake file included only to avoid errors in Xcode. The Info.plist referenced by your ios_application rule will still be used when building via the generated project.

Finally use the latest version, run successfully!

Not Working...，

Finally use the latest version, run successfully!
xcodeproj(
    name = "xcodeproj",
    bazel_path = "bazelisk",
    generate_schemes_for_product_types = ["application"],
    include_transitive_targets = True,
    infoplist_stub = "iOSApp/Info.plist",
    project_name = "iOSApp",
    deps = [
        ":app",
    ],
)

老哥 有demo工程吗 发我参考学习下... 我也遇到同样的问题，build没问题，tulsi生成的工程用Xcode就死活无法编译通过，可难受了。。。 哈哈哈

bazel-iOS的项目和tulsi两个不互通的, 你只能通过bazel run xcodeproj生成xcode项目文件然后运行

感谢大佬....
tulsi生成的工程有毒，就是无法编译，我觉得应该是tulsi对apple_framewok没做好兼容...

感谢大佬.... tulsi生成的工程有毒，就是无法编译，我觉得应该是tulsi对apple_framewok没做好兼容...

tulsi的那一套, 貌似只能用官方的规则~~
我现在已经不搞这个了,


 I'd assume just adding in the condition of not HasStatus('SG_Invisible', context.Source) should suffice.

Also consider limiting counterspell to combat, see https://www.nexusmods.com/baldursgate3/mods/3348


appears a subset of tests are being run twice in FHIRServerIntegrationTests

Found a problem today with one of the profile specific tests included in the fhir server integration test bucket.  Interestingly, the failure for that single test showed up twice in the results of the test run.
Working in Eclipse with IBM FHIR Server 4.7.0+ ... latest version of main
Did the following:

configured fhir-server-config with snomed remote term service provider
"term": {
"remoteTermServiceProviders": [{
"__comment": "Configuration for public SNOMED-CT endpoint",
"enabled": true,
"base": "https://snowstorm-fhir.snomedtools.org/fhir",
"supports": [{
"system": "http://snomed.info/sct"
}]
}]
},
ran integration test
fhir-server-test->src/test/java->testng.xml   (Run as TestNG Suite)

Expected all tests to pass but found one test failed twice (see attachment):
"com.ibm.fhir.server.test.profiles.USCoreObservationSmokingStatusTest" failed "loadResources"
once as part of "Server Tests" and once as part of "Profile Tests"
Why was this profile test run more than once?

I looked into this issue in more detail. - per testng If the package name ends with .* then subpackages are included too. in this case we are not using package-names. I think this is an artifact only in Eclipse with the testng plugin, and it's not actually running twice.  phew...


⚠ Bofrost.de has degraded performance

In 5ae1c8f, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1007 ms

Resolved: Bofrost.de performance has improved in 8968440.


remove "SDF" from the platforms group in the Network dropdown

The phrase "SDF Platforms" can lead to some confusion about what or if SDF has access to if someone's using those platforms, or if it's a service we're providing/selling, etc. "Platforms" will (hopefully) mitigate some of this confusion/hesitancy.

Preview is available here:http://developers-pr367.previews.kube001.services.stellar-ops.com


snapshots/native: ignore xattr errors during CopyDir

secuity.* xattrs cannot be copied in most cases
For moby/buildkit#1189
Signed-off-by: Akihiro Suda<EMAIL_ADDRESS>

Codecov Report

Merging #3749 into master will decrease coverage by 0.02%.
The diff coverage is 22.22%.

@@            Coverage Diff             @@
##           master    #3749      +/-   ##
==========================================
- Coverage   41.99%   41.97%   -0.03%
==========================================
  Files         131      131
  Lines       14528    14536       +8
==========================================
  Hits         6101     6101
- Misses       7520     7526       +6
- Partials      907      909       +2

Flag
Coverage Δ

#linux
45.39% <33.33%> (-0.02%)
:arrow_down:

#windows
37.08% <0%> (-0.03%)
:arrow_down:

Impacted Files
Coverage Δ

snapshots/native/native.go
42.42% <22.22%> (-0.63%)
:arrow_down:

snapshots/btrfs/btrfs.go
57.39% <0%> (-0.9%)
:arrow_down:

Continue to review full report at Codecov.

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


ACL integration tests using testcontainers

I saw that one integration test used KafkaContainer, while others assumably rely on a local Kafka to have been started manually. I thought it would be a good idea to be able to run all the integration tests using testcontainers, and I started with rewriting the tests for ACLs.
The SaslPlaintextKafkaContainer is based on the original KafkaContainers, but modified to support 6.0.0 from Confluent, and to run with SASL_PLAINTEXT natively.
I don't know if you want this change, but...

By the way, here is how SaslPlaintextKafkaContainer would look if KafkaContainer provided some hooks and calculated the final KAFKA_ADVERTISED_LISTENERS a little differently:
https://github.com/sverrehu/kafka-testcontainers-test/blob/main/src/main/java/no/shhsoft/kafka/AlternativeSaslPlaintextKafkaContainer.java

I love this change, just left a few cosmetic comments, I will continue with the review later.

Added #147 and #146 as a follow-up of this issue. Thanks again for your help man! appreciate a ton.


Spritesheet/atlas editor.

Editing the coordinates for background-image to fit the stylesheet is tedious. Double that if the stylesheet is not fitted in a grid but fitted in using a special algorithm. Would be nice to include a GUI tool to easily select which part of the background image should be displayed.
Or even better, add to that integration with some spritesheet/atlas generator.
Sorry if this is a duplicate, I tried to find one but maybe my wording is not right.

Is this in brackets now? Will it be worked on?

@Dany0 This is not yet in Brackets and I am not aware of anyone working on it. I added Extension Idea label in case someone wants to write an extension for this.

k.

I started working on an extension for this a while back -- demoed at Adobe MAX last year -- but I haven't had time to finish getting it to production quality since then.
One tricky aspect is that the coordinates are often specified in a different CSS selector from the background-image, and even the best heuristics wouldn't always be able to find the right image file -- so the UI needs to include a lightweight way for users to point out the correct image.

Cool beans, I don't understand why you wouldn't be able to find the image though, browsers have to do it, why can't you?

Brackets is not a web browser and it's not loading or executing your complete webpage -- so we have no way of knowing which CSS classes will be combined on any given tag.  Lots of webpages have dynamic content, so even static analysis of what's hardcoded in an HTML file wouldn't be enough.


feat(build): added postcss-discard-comments

Not sure if this is something that will be accepted or if we should wait for #1656.
I've got a single @import "~material-design-lite/src/material-design-lite"; in my ./src/style.scss which results in 31 copies of each comment used in ~material-design-lite/src/variables aswell as a lot of other comments.
Simply removing all CSS comments makes a huge difference in final bundle size as seen below.
Before
                                   Asset       Size  Chunks             Chunk Names
     main.6fbac24ca5132af329fe.bundle.js    1.22 MB    0, 2  [emitted]  main
   styles.b90aa540ebff7287c650.bundle.js     355 kB    1, 2  [emitted]  styles
                               inline.js    1.39 kB       2  [emitted]  inline
styles.b90aa540ebff7287c650.bundle.js.gz    31.7 kB          [emitted]
  main.6fbac24ca5132af329fe.bundle.js.gz     283 kB          [emitted]
                              index.html  977 bytes          [emitted]

After
                                   Asset       Size  Chunks             Chunk Names
     main.8d1026f789bf4650316e.bundle.js    1.22 MB    0, 2  [emitted]  main
   styles.149e785c053377a80361.bundle.js     161 kB    1, 2  [emitted]  styles
                               inline.js    1.39 kB       2  [emitted]  inline
styles.149e785c053377a80361.bundle.js.gz    22.8 kB          [emitted]
  main.8d1026f789bf4650316e.bundle.js.gz     282 kB          [emitted]
                              index.html  977 bytes          [emitted]

I agree that it should go in, that is a huge size difference.


Migrate CI to GitHub Actions

Travis-CI is getting really slow, and the integration has broken to show statuses on our PRs. Perhaps we should attempt running the tests on Travis-CI GitHub Actions?

Do you mean running tests on GitHub Actions instead?
I use GH Actions for all my projects now. Such a good user experience, great documentation, easy to set up.

Yes! Haha, messed up the comment. I think migrating the tests may be worthwhile...

Update: I migrated the unit tests, but the e2e tests with Cypress are proving to be a challenge. Particularly in spinning up a development server (Python + Django) and using the wait-on command to wait for the server to be up. I'm not sure what's wrong, but I deleted it in 58406025cc378298978365c2adb18ad4cffd0b8e

It is done! The workflow script is... complicated. But it works!

It is done! The workflow script is... complicated. But it works!


experiment: build release with panic=abort

Change Summary
Just to see what the estimated performance speedup of panic=abort is. It would have significantly worse UX on any panics though.
Related issue number
N/A
Checklist

[ ] Unit tests for the changes exist
[ ] Documentation reflects the changes where applicable
[ ] Pydantic tests pass with this pydantic-core (except for expected changes)
[ ] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

Let's consider rebasing this once the PyO3 changes for the "bound" API are done. There's no clear win here.

I think the main win here is from better inlining of some of PyO3's internals, so maybe there's a future win to be had inside PyO3 before we try this change.

I've updated the pr, but I think we shouldn't merge this before 2.7, given the number of changes in cofe, we should wait for 2.8 for this.

I would suggest we think carefully before merging this, in particular how the changes to aborting instead of unwinding will affect users and whether that's something we actually want.

@davidhewitt, is this something that we're still considering, or can we close as not planned?

Let's close.


번역 예정: webpack-2-tree-shaking-configuration

http://moduscreate.com/webpack-2-tree-shaking-configuration/

https://github.com/FEDevelopers/tech.description/wiki/Webpack-2-Tree-Shaking-Configuration


Robert Columbia: Watch getenroute.io

Robert Columbia requests the watch of the watch_keyword getenroute\.io. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

getenroute\.io has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Spevacus in Charcoal HQ


PT #153206821 - Change the PoW graph size to 2^28

For the testnet lean30 is a bit over the top and the difficulty/target
adjustment never kicks in. Graph size 2^28 should be more suitable until
we reach thousands of nodes...

This should also be reflected on the Wiki


Some code is not updated after the library update

Describe the problem
Hello, in my newly released v.1.1.0 release of the Stone_serial library, the library downloaded in the IDE is different from the library in my distribution
To reproduce
https://github.com/STONElibrary/arduino_lib/releases/tag/v1.1.0
For example, the stone_receive_group.cpp file that I downloaded from this link contains V1.1.0 characters, but the stone_receive_group.cpp file that I downloaded from the IDE contains V1.0.9 characters
Expected behavior
I hope you can make the library files you search for in your IDE exactly the same as those in your distribution
Additional context
No response
Issue checklist

[X] I searched for previous reports in the issue tracker
[X] My report contains all necessary details

@STONElibrary don't you think it would have been helpful to mention in your report that you made a bad 1.1.0 release and then later retagged?
I already explained in your release removal request of three days ago that you need to wait for a maintainer to make the removal:
https://github.com/arduino/library-registry/issues/2545#issuecomment-1461537689
Until that is done, it is expected that the bad release will still be in Arduino Library Manager.
My recommendation is for you to make a new release (e.g., 1.1.1). That is much more friendly to the users than creating multiple variants with the same version number.


Add training plots and plot saving

Changed plotting structure.
Now can plot during the training. Found good example (training epoch #11):


spy().reset() return this

Is there any way to extend Sinon so that it returns same object after calling reset()? Or can I request to make this change to Sinon?

You can also send a pull request with this feature ;-)

Sure, but isn't there any reason that it has not been done yet?

No. Me, for example, I only use reset in afterEach. I can't think of anything else that reset() should return, so return this; is fine.


fix: volume._pointsinside resample img to template

During the intersection calculation of a volume and a pointset, Volume._points_inside determines the points laying inside the volume. However, some regional masks can have different shapes than the template. This can cause points to be extracted wrongly. At the moment, this only occurs during BigBrain intensity profile queries with a region that is defined on Julich Brain 2.9 on BigBrain.
To reproduce the issue:
import matplotlib.pyplot as plt
import siibra
from nilearn import plotting

mask29 = siibra.get_region('julich 2.9', 'hoc1 left').get_regional_map('bigbrain').fetch()
tmp = siibra.get_template('bigbrain').fetch(resolution_mm=max(mask29.header.get_zooms()))
cf = siibra.features.get(
    siibra.get_region('julich 2.9', 'hoc1 left'),
    'BigBrainIntensityProfile'
)[0]
pts = cf.anchor.location.as_list()
print(len(pts))
display = plotting.plot_roi(mask29, bg_img=tmp)
display.add_markers(pts, marker_size=5)
plt.show()

(to test that it works otherwise, use cf = siibra.features.get(siibra.get_region('julich 3', 'hoc1 left'), 'BigBrainIntensityProfile')[0])
TODO:

[ ] add an example to test a possible scenario
[ ] Update e2e tests

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

Project coverage is 53.46%. Comparing base (5a0e6b3) to head (3ae88ab).
Report is 406 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##             main     #565       +/-   ##
===========================================
+ Coverage   36.81%   53.46%   +16.64%
===========================================
  Files          61       69        +8
  Lines        5421     6646     +1225
===========================================
+ Hits         1996     3553     +1557
+ Misses       3425     3093      -332

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

This PR, in fact, does not solve the actual source of the bug. #566 solves the issue. The example here will be committed there.


[SMP] Update to latest SMP release

What does this PR do?
Updates SMP experiments to use newest release and removes the now-unsupported workload checks feature.
Motivation
https://github.com/DataDog/single-machine-performance/releases/tag/v0.15.0 and https://github.com/DataDog/single-machine-performance/releases/tag/v0.15.1
Additional Notes
In draft until CI passes.
Server-side companion PR: https://github.com/DataDog/single-machine-performance/pull/1919
Possible Drawbacks / Trade-offs
Describe how to test/QA your changes

/merge

/merge


Site scope clarification request: Tenancy, Site Collection or Site?

When the OPT OUT is enabled as above does it affect every site collection in the tenancy OR does it have to be applied at every sub-site level?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 4c5279de-43c1-3a83-83ce-c1b34d25287d
Version Independent ID: 7cda1751-170a-7bbd-6d71-33daf5168f68
Content: SharePoint site theming
Content Source: docs/declarative-customization/site-theming/sharepoint-site-theming-overview.md
Service: unspecified
GitHub Login: @spdevdocs
Microsoft Alias: spdevdocs

The scope is the site collection, which includes the sites.


FW attitude control needs rewrite

There are very obvious design errors (e.g. not using inheritance) in the fw attitude controller code which leads to a lot of boiler plate code. The controller should be rewritten using the blocks library.

#1564 (merged on master) was a start

I think we're good on that front. Very little complaints.


feat(Member): set and reset guild timeouts

About
Adds setGuildTimeout and resetGuildTimeout functions to easily modify guild timeouts for a Member.
Previously, you could only do this by using Member.edit
Status

[x] These changes have been tested against Discord API or do not contain API change.
[ ] This PR includes only documentation changes, no code change.
[ ] This PR introduces some Breaking changes.

Since Member entity already is a part of Guild, I think just setTimeout and resetTimeout would be better names.

Since Member entity already is a part of Guild, I think just setTimeout and resetTimeout would be better names.

oh ok, wanted to avoid confusion with timeouts as in network reqs


[incubator/kafka] KAFKA_ADVERTISED_LISTENERS should use hostname instead of IP

Is this a request for help?: Yes

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

Version of Helm and Kubernetes:
$ helm version
Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.0", GitCommit:"91e7b4fd31fcd3d5f436da26c980becec37ceefe", GitTreeState:"clean", BuildDate:"2018-06-27T22:29:25Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.3", GitCommit:"2bba0127d85d5a46ab4b778548be28623b32d0b0", GitTreeState:"clean", BuildDate:"2018-05-28T20:13:43Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Which chart:
incubator/kafka
What happened:
After a Kafka pod is restarted, applications cannot reconnect to the pod. The pod advertises its IP to applications, but after restart, the pod gets a new IP after restart, so applications cannot reconnect to the pod using the old IP.
What you expected to happen:
When a Kafka pod is restarted, applications can reconnect to the pod.
How to reproduce it (as minimally and precisely as possible):

Run Kafka with this chart with 1 Kafka pod.
Start an application pod that connects to Kafka.
Delete kafka-0 pod
Application pod cannot connect to Kafka anymore.

Anything else we need to know:
Changing https://github.com/helm/charts/blob/master/incubator/kafka/templates/statefulset.yaml#L186 to use something like PLAINTEXT://${POD_NAME}.{{ include "kafka.fullname" . }}-headless:9092

@Chehai have you tried using the headless service names instead of IP address in your application pod? Eg conecting to <statefulset>-<pod-number> instead of IP?

I did try having my Kafka client connecting to the headless service (like setting bootstrap.servers = kafka-headless:9092). However, I had the same problem. When the Kafka client was reconnecting to Kafka, it tried to use the addresses from KAFKA_ADVERTISED_LISTENERS (returned from Zookeeper) instead of addresses listed in bootstrap.servers. KAFKA_ADVERTISED_LISTENER had the old pod IP, so the Kafka client still could not connect.

Hi @Chehai just in case you are still dealing with the problem this did the trick for me: https://github.com/gallolp/charts/commit/0984cd4552690cbbbe56454ce26b39fae45faeab
I added .POD_NAMESPACE to your suggestion in order to be able to access the cluster from a different namespace (for example I'm using kubeless)

Cool! Thank you, @gallolp
Hopefully, the official chart can get your fix soon.

not stale

not stale

not stale

not stale


Update repositories.txt

Add driver class libraries for sensors - tilt sensor, ultrasonic distance sensor, radar sensor, IR proximity sensor, PIR sensor

Adding driver classes for PIR sensor, IR Prox sensor, 0516 radar sensor, tilt sensor, ultrasonic distance sensor

Hey @ArduinoBot - I added tag 1.1

@ArduinoBot. please lint again


[Test] Price mechanism and pending file mechanism

Calculate reward in the middle of the file
Update file price per blocks
Add files count price
Add limit of groups and replicas length
Add pending file mechanism
Dynamic base fee

need to set files count and change file price