List of variables

We should make sure we have all these variables. Most of them are there, but some are missing.
Gender pay inequity
Race pay inequity
Genie score
median House rent
Median house price
House sq footage
Poverty
College educated
Labor force participation
Number of deaths
Cholesterol,
blood pressure,
arthritis
Population
Median income
Violent crime
Property crime
unemployment

Some charts need extra computation, e.g. gender pay inequity or race pay inequity

@Spaceenter how should we handle the ones that require computation?

@beets Things like gender pay inequality is already in our data, so we might just need to run the generation script again to refresh the data.
https://source.corp.google.com/piper///depot/google3/datacommons/import/mcf/resolved_mcfs.textproto;l=579-584

@beets An example of gender income inequality obs node: https://browser.datacommons.org/browser/dc/o/7083cskvb140f

Looks like we'll solve this with just config changes. In the meantime, could you run the generation script again? Thanks!

Drive-by comment: I believe the StatVar for gender-income-inequality shouldn't include "_15OrMoreYears_WithIncome" suffix. (Those are dependent PVs that we normally omit from StatVar name).
@tjann

@pradh probably because it's not in https://github.com/datacommonsorg/website/blob/master/tools/pv_tree_generator/pop_obs_spec_common.textproto -- we can't really say omit these PVs every time they occur.
I'll add that when we check in the StatVar generation tool--TBD how we should keep g3 and this repo's pop obs spec in sync.

I think Bo and Lijuan were also going to look into Pop Obs Spec's scaleability; somehow related to the PV Tree, although I am having a hard time remembering the exact context. We've also previously had discussions about potentially encoding DPV in schema, but that probably won't happen in the near term?

Moving discussion to an internal bug.

Added doc on how to run the binary (see latest CL this morning). Re-assign this back to beets as it's mostly a config change.

We've added most on the list, and have other housing related charts added.

[x] Gender pay inequity
[x] Race pay inequity
[x] Genie score
[ ] median House rent
[ ] Median house price
[ ] House sq footage
[x] Poverty
[x] College educated
[x] Labor force participation
[x] Number of deaths
[x] Cholesterol,
[x] blood pressure,
[x] arthritis
[x] Population
[x] Median income
[x] Violent crime
[x] Property crime
[x] unemployment


where is the test scripts?

where is the test scripts?

The test code has been implemented within the model_factory, please refer to the eval_model function for details.


[mrcm]: Support evaluation of applicable type/predicates

Closed in favor of https://github.com/b2ihealthcare/snow-owl/pull/1068


Sharp produces output that it cannot read.

This only happens with some images.  I've attached the an example input and output to help reproduce this:
const sharp = require('sharp')

const main = async () => {
  const image = sharp(path.join(__dirname, '../src/input.jpg'))
  const imageBuffer = await image
    .resize(10)
    .webp()
    .toBuffer()

  const resultInfo = await sharp(imageBuffer).metadata()
  console.log(resultInfo)
}

main()

The error I get on line 10 is:
Error: Input buffer contains unsupported image format

I can also save the image to disk using .toFile('10px-output.webp'), but sharp still can't read it.  Chrome reads it just fine, however.
Here is a zip file containing the input file I used and the output I got:
images.zip

Hello, this 92 byte WebP input image is tripping the 100 byte minimum check within libvips.
https://github.com/jcupitt/libvips/blob/master/libvips/foreign/webp2vips.c#L70
I've managed to create a valid 44 byte WebP image that also fails.
@jcupitt What would your recommendation be here?

Nice debugging @lovell!

Oh dear, I wish WebP was clearer on issues like this.
Googling around, it seems that WebP has "RIFF xxxx WEBP" in the first 12 bytes, I'll change libvips to look for that.

OK, git master now sniffs the webp file type by looking for a magic number rather than trying to decode the header. This will be in 8.6, due RSN.
Thanks!

... I tested it with all the webp images I have, and tried making a webp just slightly larger than the magic number, and it all seems to work.

@jcupitt Brilliant, thanks John, and thank you @whmountains for reporting.


Add /avatar command using no api's

Command Name
/avatar
Public API Resource
no api
Description
Show user avatar or mentioned user avatar
Implementation Details

Add a new javascript file in the commands folder
Use axios fetch the data from your public API
Format the data in a readable way and send it to the user
Use the discord.js docs to get started

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Can i work on this?


Keys management with helm secrets

Hi guys,
We are trying to define the way we manage the GPG keys to enc/dec the helm secrets.
The idea is trying to avoid having to share one key across the team. Then we will create a master key for the helm secrets, any additional new member who need access to the helm secret, the new member will have to generate his/her own key pairs then provide us his/her public key and we sign/trust it so that the new member will be able to enc/dec with own key.
Options like helm secrets add-user might be helpful?

@gitkent Looks this is directly supported in sops. You could use key-groups. No additional commands required.
https://github.com/mozilla/sops#key-groups

@jkroepke Thanks for that. It really helps. I will close this issue.


keep a type of $ref as a string

When use derefecence option resolve_local_ref: false and resolve_file_ref: false,
type of $ref changed from string to symbol.
This commit keep type of $ref.

I've published v0.1.5.
https://rubygems.org/gems/json_refs/versions/0.1.5


[ Full Stack Cert ] - update intro text for semantic HTML quiz

Let’s update the description to the following:
"intro": [
          "The following quiz will test your knowledge on semantic HTML concepts you have learned so far."
        ]

Here is the file you need to update
https://github.com/freeCodeCamp/freeCodeCamp/blob/main/client/i18n/locales/english/intro.json#L1763-L1768

This has been opened for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors.
If you would like to contribute and have not read the contributors docs, please do so here: https://contribute.freecodecamp.org/#/
If you have any issues with contributing, be sure to join us on the contributors channel, or on the contributors sub-forum
Happy coding


App crashes on start

Currently I cannot start the app successfully. It begins to load, then suddenly closes.
Last thing i did before, was adding new characters.
Crash log is attached.
crash.txt
I'm on mac OS 14.6.1 on a M2 MBA. Please let me know if I can provide additional informations.

Thanks for posting the issue and the crash report. I will look into it.
Which  evebuddy version are you using?

Thanks for the quick response. I'm on the latest 0.2.3, sorry that I didn't include that info.
Very promising tool btw, thanks for developing it!

The issue is likely caused by invalid data in a TowerAlertMsg notifications, proberbly from the last character you added. (e.g. aggressorID = 0). I updated the app so it can now deal with those better.
The new release (0.2.4) should available in about 15 mins. Please let me know if that fix works for you.

Thank you for checking out the app and for your kind feedback. The app is still brand new and every feedback helps a lot.


feat(compaction): do not schedule too small compaction task

Signed-off-by: Little-Wallace<EMAIL_ADDRESS>What's changed and what's your intention?
a small compaction task may block a long time and cost a lot of IO resource
Checklist

[x] I have added necessary unit tests and integration tests

Refer to a related PR or issue link (optional)

We can see that the files are merged to base level just in several minutes after streaming process has end.
And the write-amplification (compaction write throughput / flush throghput) is as expected.

Compaction Strategy Change

When there are very many small files, the intra-l0 compaction task is triggered preferentially. We only merge those files whose size are smaller than 128MB.
limit the write-amplification from L0 to L1 no more than 4 when the participant files are small.

Code Refactor

split intra-l0-compaction to an independent CompactionPicker.
calculate the priority score independently in LevelSelector for intra-l0. So that when there are no small files, we can also trigger a compaction task from L0 to L1.


Focus on the newly created note

So far, when we run the command, it'll create the new note and fill it perfectly - but then we still need to open it manually which can be annoying.
It would be nice to have toggle in the settings to open the newly created note right after creation. It could work like QuickAdd's template options: whether to open it, if yes whether to open it in a new pane or on active pane, if in a new pane whether open it vertically or horizontally.
This would remove friction of having to manually find the file. It could also be another YAML key, to make it more flexible and decide which templates should open after creation and which ones shouldn't.

Agreed - both on the idea and the YAML execution

There's a new field in the new version: template-should-create, which you can use to open the new note in the same pane or a new split (vertical only at the moment0.
Can be set as a default, or by template in the YAML :)


Fix regex pattern

When a hostname is something like shaparak.ir.fake-shaparak.xyz, the pattern /shaparak.ir/ will be matched. The PR fixes this issue :)
BTW, great job 👍

thanks!
applied the next update. 👍


Cannot include same type twice

Imagine a book has multiple authors. You want to fetch an author, their books, and all the other co-authors for those books.
/authors/123?include=books.authors
Currently, if you do this, it will blow away all relationships on books instead of rendering correctly.

What do you mean by "blow away"? I would expect this to include the base author (id=123) in the primary data, and all their books, as well as all their co-authors in the included section. Moreover, I would expect every book in the response to have a fully populated authors relationship.

I would expect every book in the response to have a fully populated authors relationship.

This would not be the case. The relationships are removed.

Are you providing a sparse fieldset as well? Otherwise that would be a bug.

No, no sparse fieldset.

Could you provide a failing spec for this if you have one handy? I'll investigate and fix right now.

Not one for this repo but next best thing. This reproduces in my sample app. If you run bin/rspec spec/api/v1/employees/index_spec where that binding.pry is, you'll see that no included is coming back at all (in a different scenario ive seen included come back but relationships missing from one of the included members.). Remove the extra include of .employees and it will work again.

Otherwise it will be a little while before I can get a spec for this repo.

has_many :employees (plural)
vs
create(:position, employee: employee1) (singular employee)
Does the created resource actually respond to .employees (plural)?

Ah, yes, that's an eventual issue but not relevant to the immediate one. It's originally position belongs_to employee, but as part of the commit I made it have many employees as well (at one point I was thinking it might be has-many specific). So it responds to employee and employees both.


Updated Part-4 to use PyQt5

I found your tutorial very helpfull, thanks.
I followed it using PyQt5, and have now added the required changes to your code.

Hi, thanks for the pull request. The code itself looks good, however the problem is that the tutorial parts build on each other, meaning that if one part uses PyQt5, all parts should (for consistency; it shouldn't be that one part builds properly for someone while another doesn't). Do you think you could integrate (i.e. copy) your changes into the other parts so that all parts use PyQt5?

There's now a PyQt5 version for all 4 parts. I also added a summery of the changes.

I just cloned your fork and installed PyQt5 and everything builds well. However, there seems to be an encoding issue which needs to be resolved. Can you please paste the line # -*- coding: utf-8 -*- to the top of part-1.py, part-2.py, part-3.py and part-4.py? I'll merge right after.

Strange. I have my editor set to utf-8.

@Jock2 Thanks :blush:


Build path incorrectly computed when it's in the same hierarchy as its owning project

Writing this on behalf of a user who reached out to me directly:
We think the first StripPath in the subVI subConvertValueToNameAndPath.vi should be removed. Without removing this, the Builder could not locate previously created .lvlibp’s. Our folder structure looked like:
A folder/
   Package A.lvproj
   Package B.lvproj
   Packages/
      Package A.lvlibp
      Package B.lvlibp

Turns out the necessary value in the build spec to check was Bld_localDestDirType (or PKG_output.Type for packages) to determine whether the build path should be determine from relativeToProject or not. Acting based on that value is instead the correct thing to do.


Plugin management system

[ ] based on git
[ ] every function call is recorded into a script
[ ] wrap the script in its own function
[ ] automatically push to remote repo
[ ] automatically manage versions: git tags if available, or git hash otherwise
[ ] add plugins by adding URL of git repo
[ ] the core of Napari is just the minimal plugin system, everything is plugin based, even the plugin core, this way we have a unified way to push updates to users. Users can also add their own user defined plugins, and first class contributions can be added to the official distribution.

I assume that we will also be creating our own environment then?

@kne42 Ah yes, this is a good point. And an interesting one. I think separate environments will be tricky to manage. You'd have to do inter-process communication, and plugins would be second-class citizens, because you couldn't match the performance of running in the "app" environment. Perhaps we should explicitly say which packages we are shipping with the app, and plugins can add packages but only if they don't conflict with the base ones, in the conda-forge sense of "conflict".

For now we have to define a basic but relatively exhaustive set of dependencies that would cover 90% of needs.
Late on, we can figure out a way for plugins to play well together. This has not been solved in FiJi for example.

On 4. Jun 2018, at 23:12, Juan Nunez-Iglesias<EMAIL_ADDRESS>wrote:
@kne42 https://github.com/kne42 Ah yes, this is a good point. And an interesting one. I think separate environments will be tricky to manage. You'd have to do inter-process communication, and plugins would be second-class citizens, because you couldn't match the performance of running in the "app" environment. Perhaps we should explicitly say which packages we are shipping with the app, and plugins can add packages but only if they don't conflict with the base ones, in the conda-forge sense of "conflict".
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/Napari/napari/issues/3#issuecomment-394593441, or mute the thread https://github.com/notifications/unsubscribe-auth/AByMknqOfxKUq5cIp780yqOObdd6jrJNks5t5iFZgaJpZM4UYKpd.

We can use the GitPython lib:
http://gitpython.readthedocs.io/en/stable/index.html
Here is an example how to pull:
https://stackoverflow.com/questions/20073873/how-to-checkout-a-tag-with-gitpython

Thanks for the pointers! I'll get started on this now :P

I think we should create a cookiecutter for plugins similar to what Jupyter has set up.

Great idea!


Validate documentation examples on CI

This PR moves most of our solidity code blocks into dedicated examples. Snippets that should work for all our targets go into the /examples directory, and target specific ones into /examples/target. I implemented a test to check that all examples successfully compile, in parallel.
Also a lot of examples contained syntactical errors, I fixed everything. Additionally they are now correctly formatted.

@xermicus thank you very much, this looks great. It must have been a lot of work to fix all the examples and give them names. :1st_place_medal:
I'll have to go over it in detail again.

I really do like the rayon crate, it is my favorite data parallel library :blush:

I don't think the solidity fragments belong in examples though. What do you think of docs/examples/ or docs/solidity/?

That makes it too compliclated in my opinion. I just updated the fragments where it makes sense to full contract example. So we can have as a general rule of thumb: If it is a full contract example, put it into the examples, otherwise just use a solidity code block. WDYT?

If you feel like it, there are bunch of examples with .. code-block:: javascript that should really be .. code-block:: solidity

I noticed that too, but when I started to change them the doc generator would complain about the syntax. I suspect this is mainly due to some of our custom language additions, so I just let them be.

I don't think the solidity fragments belong in examples though. What do you think of docs/examples/ or docs/solidity/?

I have reviewed your files and found no problems, but I share the same opinion as @seanyoung. These Solidity files should not be under examples, because a proper example should have a thorough explanation of what they are doing, including many comments for usage.
Creating a top-level examples folder will mislead users, making them think we are providing them with comprehensive examples of how to use Solidity for either Solana or Substrate.


Confused how to use custom theming

I went through this description https://github.com/asciidoctor/asciidoctor-pdf/blob/master/docs/theming-guide.adoc to create a custom theme which should just change the footer of my generated pdf. What I unterstand from the description is, that I can just overwrite the properties I want to change and the rest will look the same as without any custom theme.

When creating a new theme, you only have to define the keys you want to override from the base theme, which is loaded prior to loading your custom theme.

But it seems something is messing up with the fonts. Which is - to be fair - pointed out directly beneath

If you start a new theme from scratch, we strongly recommend defining TrueType fonts and specifying them in the base and literal categories. Otherwise, Asciidoctor PDF will use built-in AFM fonts, which can result in missing functionality and warnings.

So I have to wrestle with the fonts, which I don't want to change? Or did I make a mistake?

When creating a new theme, you only have to define the keys you want to override from the base theme, which is loaded prior to loading your custom theme.

This is describing the bare minimum so that you understand the boundaries. You are going to end up with a severely understyled document if you don't start with the default theme. That includes the fonts. Here's the default theme file: https://github.com/asciidoctor/asciidoctor-pdf/blob/master/data/themes/default-theme.yml

Just copy that file, tweak it and you'll be off to the races.

Thanks. That first quoted paragraph just mislead me. But it would be nice if I just could change the values I would like to and get the default settings anyway. Convention over configuration :)

It's now possible to extend themes, which will make this a lot easier. You can see this in action in the theme for the chronicles example. https://github.com/asciidoctor/asciidoctor-pdf/blob/master/examples/chronicles-theme.yml

See #367 for details about how this got fixed.


Wrong kWh charging report: 130.000 kW charging speed and 578 kWh charged in 16 seconds

Describe the bug
In my chargelog I found a charging event with "phantasy" figures of 130.000 kW

I have no clue what to do cause it affected my usual stats big times, I mean those counter senors for daily, weekly and monthly charging.
I have not deleted it yet cause I do not know how and if that would update my sensors too.
So here is the record

finally the log from the wallbox pulsar plus charger which has no such record even though there was a charging session on october 5th

Steps to reproduce

the wrong values appeared

...
Configuration details
###################################################
# 2024-10-09 - 13:45 = vehicle golf: 2 not phases #
###################################################

network:
  schema: http
  host: evcc.local # .local suffix announces the hostname on MDNS
  port: 7070

log: debug
  # alternativ
  # log: info
levels:
  site: debug
  lp-1: debug
  lp-2: debug
  cache: error
  db: error
  ocpp: trace

# unique installation id
plant: b4e6c38871bb59bd6f892b4fa72af41423514af3f6177bba1d789184ab602bf3

##########################################
# control cycle interval                 #
# kann kritisch sein, wenn < 30 Sekunden #
##########################################

interval: 12s   # meterinterval: 12s unter chargers sollte mit synchron gehalten werden
                # wenn das zu kurz ist, dann gibt es den folgenden Fehler, von daher das Intervall verlängern
                # Garage: charger logic error: current mismatch (got 11.2A measured, expected 8.73A)
                # https://github.com/evcc-io/evcc/discussions/15761#discussioncomment-10893056

meters:
  - type: template
    template: growatt-hybrid
    id: 1
    device: /dev/ttyUSB0
    baudrate: 9600
    comset: 8N1
    usage: grid
    modbus: rs485serial
    name: grid1

  - type: template
    template: growatt-hybrid
    id: 1
    device: /dev/ttyUSB0
    baudrate: 9600
    comset: 8N1
    usage: pv
    modbus: rs485serial
    name: pv2

  - type: template
    template: growatt-hybrid
    id: 1
    device: /dev/ttyUSB0
    baudrate: 9600
    comset: 8N1
    usage: battery
    modbus: rs485serial
    name: battery3
    capacity: 14.0

# chargers:
#   - type: template
#     template: pulsarplus
#     timeout: 2m
#     name: wallbox4

###   LÖSUNG   von   hier   ###
###   https://github.com/evcc-io/evcc/issues/15581#issuecomment-2337136867

chargers:
#   5 ZEILEN LÖSUNG für 1.30.13 von https://github.com/evcc-io/evcc/discussions/15986#discussioncomment-10674568
  - type: template
    template: ocpp-abb
    remotestart: true     ###   >1.30.x   ###   NEU FOLGE von https://github.com/evcc-io/evcc/issues/15581
    meterinterval: 12s    ###   from 10s to 12s 09.10.2024 >1.30.1x = optional
                          ###   ganz oben noch als generelles interval: 12s
    metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Import,Voltage  # >1.30.1x

    # metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Power.Offered,Current.Import,Voltage  # >1.30.1x

    stationid: Garage ### NEU = OCCP ID
    connector: 1 ### soll alt sein
    timeout: 2m
    name: wallbox4

vehicles:
  - name: eGOLF
    title: GOLF
    type: custom
    ###       type: template
    ###       template: offline
    icon: car
    capacity: 31.6 # net capacity in kWh

    phases: 2

    soc: # optional SoC (%)
      source: mqtt
      topic: export/golf/soc_permanent
    range: # optional electric range (km)
      source: mqtt
      topic: export/golf/reichweite_permanent
    odometer: # optional odometer (km)
      source: mqtt
      topic: export/golf/km_stand_permanent

loadpoints:
  - title: Garage
    charger: wallbox4
    mode: pv # charge mode (off, now, minpv, pv)
    vehicle: eGOLF # set default vehicle (disables vehicle detection)
    ###   NEU: SCHWELLEN   ###
    enable:
      delay: 1m
      threshold: -1500 # laden, sobald 1 Minute lang min 1.500 W eingespeist worden sind
    disable:
      delay: 2m
      threshold: 1000 # laden beenden, wenn 2 Minuten lang mehr als 1.000 W Netzstrom bezogen wurden

site:
  title: Zuhaus
  meters:
    grid: grid1
    #
    # für saubere Überschussdarstellung bei mehreren Wechselrichtern
    # pv Zähler deaktivieren
    # https://github.com/evcc-io/evcc/discussions/16574#discussioncomment-10892601
    #
    pv: pv2
    battery:
      - battery3
  residualPower: 111

tariffs:
  currency: EUR # three letter ISO-4217 currency code (default EUR)
  grid:
    type: tibber
    token: RcnWXBLfW5ZLf2yuHShZ9X3hubZgvIR7azaD7SUt084
    # type: fixed
    # price: 0.272 # 0.272 [currency]/kWh

  feedin:
    # rate for feeding excess (pv) energy to the grid
    type: fixed
    price: 0.0774 #  seit 19.8.2024

# mqtt message broker
mqtt:
  broker: <IP_ADDRESS>:1883 # MQTT-Broker & Port
  topic: evcc # alles wird im MQTT Explorer unter TOPIC EVCC erscheinen
  user: mymqtt
  password: mymqttpi

# push messages
messaging:
  events:
    start: # charge start event
      title: Charge started
      msg: Started charging in "${mode}" mode
    stop: # charge stop event
      title: Charge finished
      msg: Finished charging ${chargedEnergy:%.1fk}kWh in ${chargeDuration}.
    connect: # vehicle connect event
      title: Car connected
      msg: "Car connected at ${pvPower:%.1fk}kW PV"
    disconnect: # vehicle connected event
      title: Car disconnected
      msg: Car disconnected after ${connectedDuration}
    soc: # vehicle soc update event
      title: Soc updated
      msg: Battery charged to ${vehicleSoc:%.0f}%
    guest: # vehicle could not be identified
      title: Unknown vehicle
      msg: Unknown vehicle, guest connected?

Log details
none available about this topic or at least I have not found any

What type of operating system are you running?
HomeAssistant Add-on
Nightly build

[X] I have verified that the issue is reproducible with the latest nightly build

Version
Current version: 0.130.13

Unfortunately your report is missing a detailed log file. Without log, we don‘t have the information for diagnosing the issue described. See https://docs.evcc.io/docs/faq#wie-kann-ich-ein-logfile-zur-fehleranalyse-erstellen.

Neither have we without log. Probably rogue readings.

I do not have these logs from early october and I can not create those under HA if I remember right.
My logs from the log UI are limited to I guess last evcc reboot or so.
I have deleted that charging and I then saw a kind of correction in the log but it did not arrive in the HA sensors.
There was a change of 780 kWh .

For all those facing a similiar issue there is a repair tool in HomeAssistant under the developer tools called statistics.
If you search for your wrong sensor then there is on the right border a chart which you can click to edit a value for a certain hour or multiple.

in this case I set the value to 7,5 kWh for 2 consecutive hours cause MyWallbox Portal says that I had charged 15 kWh.


python311Packages.bitsandbytes: 0.41.0 -> 0.42.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.bitsandbytes is: 8-bit CUDA functions for PyTorch
meta.homepage for python311Packages.bitsandbytes is: https://github.com/TimDettmers/bitsandbytes
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.42.0 with grep in /nix/store/39gm0z6babq3dghpkxn8ia2ziddrrph8-python3.11-bitsandbytes-0.42.0
found 0.42.0 in filename of file in /nix/store/39gm0z6babq3dghpkxn8ia2ziddrrph8-python3.11-bitsandbytes-0.42.0

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
python311Packages.bitsandbytes
python311Packages.openllm

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/39gm0z6babq3dghpkxn8ia2ziddrrph8-python3.11-bitsandbytes-0.42.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/e66df5a9cd0e3ba077a6a7e5d2df4c44ac379752#python311Packages.bitsandbytes

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/39gm0z6babq3dghpkxn8ia2ziddrrph8-python3.11-bitsandbytes-0.42.0
ls -la /nix/store/39gm0z6babq3dghpkxn8ia2ziddrrph8-python3.11-bitsandbytes-0.42.0/bin

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

1 package marked as broken and skipped:

python311Packages.openllm

1 package built:

python311Packages.bitsandbytes

Maintainer pings
cc @bcdarwin for testing.

Result of nixpkgs-review pr 289763 run on x86_64-linux 1

2 packages failed to build:

python311Packages.openllm
python311Packages.openllm.dist

6 packages built:

python311Packages.bitsandbytes
python311Packages.bitsandbytes.dist
python311Packages.openllm-client
python311Packages.openllm-client.dist
python312Packages.openllm-client
python312Packages.openllm-client.dist


Support quoted types

For example; list['Task']

Looks like this is supported with the eval_str parameter in inspect.signature of python 3.10+. As such this is probably for 3.0 not 2.0 as 2.0 will support Python 3.9.
Or maybe the feature could be gated based on python version? idk

I do at least need to make sure that an exception isn't thrown when quoted types are used.


Unexpected Keyword Syntax Error

I'm on Ubuntu 12.  And I'm getting the following error in Dropcaster
$ dropcaster
/usr/local/bin/dropcaster:22:in `load': /var/lib/gems/2.3.0/gems/dropcaster-1.0.0/bin/dropcaster:56: syntax error, unexpected keyword_rescue, expecting keyword_end (SyntaxError)
  rescue StandardError
        ^
	from /usr/local/bin/dropcaster:22:in `<main>'
ygreif@ygreif-OptiPlex-3020:~/Dropbox/Public/hebrew$ dropcaster > index.rss
/usr/local/bin/dropcaster:22:in `load': /var/lib/gems/2.3.0/gems/dropcaster-1.0.0/bin/dropcaster:56: syntax error, unexpected keyword_rescue, expecting keyword_end (SyntaxError)
  rescue StandardError
        ^
	from /usr/local/bin/dropcaster:22:in `<main>'
ygreif@ygreif-OptiPlex-3020:~/Dropbox/Public/hebrew$ dropcaster > index.rss
/usr/local/bin/dropcaster:22:in `load': /var/lib/gems/2.3.0/gems/dropcaster-1.0.0/bin/dropcaster:56: syntax error, unexpected keyword_rescue, expecting keyword_end (SyntaxError)
  rescue StandardError
        ^
	from /usr/local/bin/dropcaster:22:in `<main>'

@nerab can we get a new release? 20faccfb47fc49504e5d1d2dd4af940af0dbb23e and 5f880072b21960e5103112a8ca6e131e18f212c9 make dropcaster compatible with Ruby 2.3 which will fix it for this user.

Ruby 2.3 is not maintained anymore. Sorry.


[META] Remote Cluster State Issues (Phase - 2)

Is your feature request related to a problem? Please describe.
Issues listed under this meta issue are related Remote Cluster State feature for Phase 2. As part of Phase 2, we will add support to backup and restore global metadata to and from remote store.
Describe the solution you'd like
https://github.com/opensearch-project/OpenSearch/issues/9143
Tasks
OpenSearch 2.10 Release

[ ] https://github.com/opensearch-project/OpenSearch/issues/10525
[ ] https://github.com/opensearch-project/OpenSearch/issues/10526
[ ] https://github.com/opensearch-project/OpenSearch/issues/10527
[ ] https://github.com/opensearch-project/OpenSearch/issues/9816
[ ] https://github.com/opensearch-project/OpenSearch/issues/10662
[ ] https://github.com/opensearch-project/OpenSearch/issues/10658
[ ] https://github.com/opensearch-project/OpenSearch/issues/10841
[ ] https://github.com/opensearch-project/OpenSearch/issues/10697
[ ] https://github.com/opensearch-project/OpenSearch/issues/10691
[ ] https://github.com/opensearch-project/OpenSearch/issues/10888
[ ] https://github.com/opensearch-project/OpenSearch/issues/10586
[ ] https://github.com/opensearch-project/OpenSearch/issues/10555
[ ] https://github.com/opensearch-project/OpenSearch/issues/10071
[ ] https://github.com/opensearch-project/OpenSearch/issues/10911
[ ] https://github.com/opensearch-project/OpenSearch/issues/10809
[ ] https://github.com/opensearch-project/OpenSearch/issues/10773
[ ] https://github.com/opensearch-project/OpenSearch/issues/10688
[ ] https://github.com/opensearch-project/OpenSearch/issues/10687
[ ] https://github.com/opensearch-project/OpenSearch/issues/10645
[ ] https://github.com/opensearch-project/OpenSearch/issues/10978
[ ] https://github.com/opensearch-project/OpenSearch/issues/10683
[ ] https://github.com/opensearch-project/OpenSearch/issues/10682
[ ] https://github.com/opensearch-project/OpenSearch/issues/10686
[ ] https://github.com/opensearch-project/OpenSearch/issues/10890
[ ] https://github.com/opensearch-project/OpenSearch/issues/10990
[ ] https://github.com/opensearch-project/OpenSearch/issues/10913
[ ] https://github.com/opensearch-project/OpenSearch/issues/10905
[ ] <adjust remote retries to have a shorter back-off/more attempts as compared to translog/segments>

Additional context
Previous Release - https://github.com/opensearch-project/OpenSearch/issues/9344

Hi, are we on track for this to be released in 2.12 ?

@soosinha can you update this Meta issue with latest status?

The changes planned for 2.12 have been released. The major changes are upload of global metadata on cluster state publication and download of global metadata during cluster-manager node bootstrap. The timeout of metadata upload has been added as dynamic settings. Cluster UUID chaining logic has been modified according to global metadata. Cluster state upload stats having added under discovery metric in node stats API. Cluster state uploads are now being performed from a separate threadpool.
Resolving this meta issue now. The pending issues will be tracked individually


fix: Use a stable recipe order for NullableRecipe.getRecipeList()

Hi! Great to see the recipes here; I do have one request: can we make the order of the recipe list stable?
For context: we generate documentation for recipes, even when maintained externally. Before this change we would see a new recipe list order for every run. After this change the order should be fixed, such that we do not keep changing that documentation page every time.
Thanks in advance!

While I have you, quick question - how do I run tests for these recipes in parallel? They take a lot of time, and when I tried parallelizing them via JUnit 5, I got a whole bunch of exceptions. I searched the OpenRewrite docs and nothing came up. Surely, there has to be a way...

Good question! I guess we've never explored that option, nor do I know what issues that would run into. I'd briefly on the migration module here added the same files as I had seen on core/src/test/resources/junit-platform.properties, but saw no issues or noticable improvement. What did you run into before?


Fix "quarter" granularity serialization.

There are three months in a quarter.

Thanks for fixing this. 👍


Added CLI flags for updating multiple domains at once.

@jdevelop I've merged your changes to master, keeping only the support for many domains. Feel free to issue another pull request for specifying a custom AWS profile path and a custom log file path (please put them on two separate commits). Thanks!


Well.from_las fails when using pathlib.Path object(s)

The function Well.from_las(filename) causes an exception when using a pathlib.Path object instead of a string. This is common use case on Windows. I'll provide a PR to fix this later today based on @dcslagel's earlier fix to lasio.

Thank you Kent!


Add support for CloudEvents In Event manager/Event driver

[ ] Bug
[ ] Feature
[x] Enhancement

Detailed Description
Currently, there is no standard format for events flowing in our system. We should look at CloudEvent Spec [1] and implement it as a format of events once they get through the event driver.
[1] https://github.com/cloudevents/spec/blob/14b4e7122d026b6bac21897b8c892be2fb900ef2/spec.md
Complexity

[ ] Low - Simple enhancement or bug fix, no architectural changes or refactoring
[ ] Medium - Change requires some thought, but is relatively isolated
[x] High - Significant architectural change or large refactor

Fixed in #244


Camera Node Crashes

The camera node on my system crashes randomly with the following error:
[camera/stereo_s-6] process has died [pid 9094, exit code -11, cmd /home/faizan/catkin_ws/devel/lib/astra_camera/camera_node /camera/image_raw:=/camera/rgb/image_raw __name:=stereo_s __log:=/home/faizan/.ros/log/3551285c-a325-11e9-ab44-309c23644e94/camera-stereo_s-6.log].
The log file is empty and there are no error messages printed before this crash. Any ideas how to approach debugging this?

Hi @faizan-m , are you using multiple cameras simultaneously? Or could you provide more details such as your launch file? It usually happens while you are using a wrong uvc setting (format, frame rate, resolution). The recommended setting for stereo_s is 640x480@30fps with yuyv.

Hi!
Thanks for getting back so quickly! I am only using a single stereo s camera. My launch file is derived from the original stereo-s launch file:
https://gist.github.com/faizan-m/a186a58379866b6b116bd0a20b3939cd

I think I found it in line 74:
<param name="camera_info_url" value=""/>
I added the camera calibration url here as well (apart from setting it in rgb_camera_info_url parameter:
And that seems to have fixed it.

It actually still crashes. Much less frequently than before though....

I've already checked your file. It should be fine. For now, I would recommend you to change another usb cable. According to this issue, I think low-quality cables are possible to produce unexpected crashes.

Hi @faizan-m , do you fix the problem? If not, you could modify the launch file by switching yuyv to mjpeg and try it again. Hope it helps.

The problem slowly disappeared so I am assuming it is because of the USB cable but I will keep that in mind, thanks!


OpenEXR install for ubuntu in README

@siddas27  for ubuntu， sudo apt-get install openexr and libopenexr-dev before pip install solved it for me

_Originally posted by @butterl in

https://github.com/gabrieleilertsen/hdrcnn/issues/5#issuecomment-394076616_

Could this be added to the main readme?
For UBUNTU:
sudo apt-get install openexr
libopenexr-dev
pip install OpenEXR

Thanks. Added a note about it in the install instructions.


Rename the package

The PyPI name does not have the .py, so I am removing it from here.

Hi! This is the friendly conda-forge-admin automated user.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Out of interest, did you also rename the repo? That is cool.

Out of interest, did you also rename the repo? That is cool.

Nope. The repo was automatically named without the .py because that is the project name, and that name comes from the directory. Since the directory did not have the .py the repo name was OK.
I somehow had geojsonio.py in the yaml file because of its name on GitHub. That mismatch was the cause of the broken badge URLs.


Correctly write empty value records

This fixes a long standing (but previously unencountered) issue where we could not write empty value records containing device or variation index tables.
This required an upstream fix, which is now in place.

going to self+1 this, it's a small PR that I'd like to get merged so I can release and update fontc.


Focal Loss for Multi-class classification

Thank you for your work. I am sure this implementation of Focal Loss will work perectly fine for Binary Classification. Will it also work for multi-class classification? Or will need to tweak it a bit?

You can try this out. Take it with a grain of salt though as I did it in a hurry
class CategoricalFocalLoss(nn.Module):
    def __init__(self, gamma:float=2., reduction:str='mean'):
        """
        https://arxiv.org/pdf/1708.02002.pdf
        default gamma from table 1(b)
        we could specify alpha as a per class weighting but I haven't implemented
         it yet
        """
        super().__init__()
        if reduction not in ['mean', 'none', 'sum']:
            raise NotImplementedError('Reduction {} not implemented.'.format(reduction))
        self.reduction = reduction
        self.gamma = gamma

    def forward(self, input: FloatTensor, target: LongTensor):
        """
        expect input to be (B, N) where N is number of classes
        expect target to be (B, 1) If target is B, unsqueeze
        """
        target = target.reshape(target.shape[0], -1)
        p = torch.softmax(input, -1)
        p = torch.gather(p, -1, target)
        logp = torch.log_softmax(input, -1)
        logp = torch.gather(logp, -1, target)
        fl = - 1 * (1 - p) ** self.gamma * logp
        return self._reduce(fl)

    def _reduce(self, x):
        if self.reduction == 'mean':
            return x.mean()
        elif self.reduction == 'sum':
            return x.sum()
        else:
            return x

Thank you for the response!! @alexander-soare

    p = torch.softmax(input, -1)
    p = torch.gather(p, -1, target)
    logp = torch.log_softmax(input, -1)
    logp = torch.gather(logp, -1, target)

Why you are calculating loss for only true class here? Isn't in multi class classification we add all classes losses?


Add legacy browser specific CSS, swap out jQuery for native JavaScript when checking for browser

Reassigning to @Coenego

Coverage remained the same at 100.0% when pulling df2a013846ad1bf3f784a92be60c15bd75ab537d on bp323:issue-424 into 33dc4751d1f40064e6d6088e15a44705183359e2 on CUL-DigitalServices:master.


linted parallel.py

I'm assigning this to Matt because Ingrid and I did a bit of code re-writing in order to pass the linter (see comment on the code itself).  Matt, can you check that the code still does what you want it to?  No rush.  :)

This needs to be tested; @MridulS will test it in the context of the parallel problems with cstwMPC and either accept it or delete it.

This will work but instead of creating a new var and storing it in memory, we can use the following version for the linted version
    agent_list_out = Parallel(n_jobs=num_jobs)(
        delayed(runCommands)(*args)
        for args in zip(agent_list, len(agent_list) * [command_list])
    )

Closing in favour of https://github.com/econ-ark/HARK/pull/465


moving loadPixels() to after beginDraw() should resolve #87

I tested with 3.0, default renderer and P2D.

Fixes #87

@shiffman thanks again... this in fact sorted it. I owe High-Fives


Cave directly under water

Potential Solutions:
Create code so that caves must have at least one solid block between air and water.

As mentioned in #16 there are no block updates so far.
Evan is going to implement flowing water some time in the future: https://github.com/EvanatorM/ScuffedMinecraft/issues/16#issuecomment-2427638962.

same thing happened but in less amounts


Avoid using profiles in REST integration tests

There are two integration tests in REST that test the same thing based on the properties:

RestApiV2QCqlDisabledIT
RestApiV2QCqlIT

The second one specifies a profile that sets stargate.rest.cql.disabled=false.
However, although this works on the integration tests, it fails when we are using the integration tests with the running app. Simply, you can not switch the properties of the running app. IN that sense, the integration tests, which are effectively end-to-end tests should not specify profiles.
I am not sure what's the best way to solve this. Imo the RestApiV2QCqlDisabledIT could be classical @QuarkusTest with concrete profile and check that method is not existing. For the other, we could enable by default in the test resources that the option is false and then have some kind of a protection in the situation when we run against the running app. Not sure though, maybe a small discussion on this should be done.

Ok. Yes, that makes sense. Just need to discuss the best way to refactor things to just verify 2 aspects (default being not to include; ability to include).


Feat: add warning kind diagnostic

Add warning kind diagnostics to build kclvm warning.

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[ ] N
[x] Y re #109

2. What is the scope of this PR (e.g. component or file name):
error/src/error.rs
error/src/diagnostic.rs
error/src/lib.rs

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[x] Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[ ] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[x] Other
add doc test in error/src/lib.rs

6. Release note

Please refer to Release Notes Language Style Guide to write a quality release note.
None

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 18 (0.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.6%) to 58.992%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

kclvm/error/src/error.rs
0
8
0.0%

kclvm/error/src/lib.rs
0
10
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.6%

Covered Lines:
21364

Relevant Lines:
36215

💛  - Coveralls


WIP:  Fix time limit error for CI

This PR is trying to ensure that the 50 minute limit of CI is not exceeded for the framework.

The time is really from simphony-openfoam and simphony-lammps-md.  Both take between 17-20 minutes to build/test which doesn't allow much time for everything else.


chore: remove duplicate dependencies from pom files and updated README.md

After some investigation still, issue #100 is hanging,
so the README.md file is updated to mention it as a
limitation.

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


Hackage releases don't pass tests on ghc 9.0

The most recent version on Hackage (alex-3.2.6) predates ghc 9.0.1 and as such fails to include the fix (84b29475e057ef744f32a94bc0d3954b84160760). Can we get a release which passes the tests?

The fix is included in releases starting with 3.2.7.


[bazel on macOS] numpy: incompatible architecture (have 'arm64', need 'x86_64')

When I run an agent with bazel run, the process fails with an error about incompatible numpy shared objects:
'/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/numpy/core/_multiarray_umath.cpython-311-darwin.so' (mach-o file, but is an incompatible architecture (have 'arm64', need 'x86_64'))
My system is Apple silicon, yet numpy is complaining the x86_64 build isn't there.
I can import numpy just fine when I launch Python:
❯ python3
Python 3.11.2 (v3.11.2:878ead1ac1, Feb  7 2023, 10:02:41) [Clang 13.0.0 (clang-13<IP_ADDRESS>)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import numpy
>>> print(numpy.__file__)
/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/numpy/__init__.py

Full logs:
 ./tools/bazelisk run //agents/pid_balancer:pid_balancer
Using existing Bazel binary from /Users/bora/upkie/tools/bazel...
+ /Users/bora/upkie/tools/bazel version
Bazelisk version: v1.16.0
Bazelisk version: v1.16.0
Build label: 6.2.0
Build target: bazel-out/darwin-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Tue May 9 18:38:01 2023<PHONE_NUMBER>)
Build timestamp:<PHONE_NUMBER>
Build timestamp as int:<PHONE_NUMBER>
+ /Users/bora/upkie/tools/bazel run //agents/pid_balancer:pid_balancer
INFO: Analyzed target //agents/pid_balancer:pid_balancer (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
Target //agents/pid_balancer:pid_balancer up-to-date:
  bazel-bin/agents/pid_balancer/pid_balancer
INFO: Elapsed time: 0.377s, Critical Path: 0.01s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
INFO: Running command line: bazel-bin/agents/pid_balancer/pid_balancer
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/numpy/core/__init__.py", line 24, in <module>
    from . import multiarray
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/numpy/core/multiarray.py", line 10, in <module>
    from . import overrides
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/numpy/core/overrides.py", line 8, in <module>
    from numpy.core._multiarray_umath import (
ImportError: dlopen(/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/numpy/core/_multiarray_umath.cpython-311-darwin.so, 0x0002): tried: '/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/numpy/core/_multiarray_umath.cpython-311-darwin.so' (mach-o file, but is an incompatible architecture (have 'arm64', need 'x86_64')), '/System/Volumes/Preboot/Cryptexes/OS/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/numpy/core/_multiarray_umath.cpython-311-darwin.so' (no such file), '/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/numpy/core/_multiarray_umath.cpython-311-darwin.so' (mach-o file, but is an incompatible architecture (have 'arm64', need 'x86_64'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/numpy/__init__.py", line 130, in <module>
    from numpy.__config__ import show as show_config
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/numpy/__config__.py", line 4, in <module>
    from numpy.core._multiarray_umath import (
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/numpy/core/__init__.py", line 50, in <module>
    raise ImportError(msg)
ImportError:

IMPORTANT: PLEASE READ THIS FOR ADVICE ON HOW TO SOLVE THIS ISSUE!

Importing the numpy C-extensions failed. This error can happen for
many reasons, often due to issues with your setup or how NumPy was
installed.

We have compiled some common reasons and troubleshooting tips at:

    https://numpy.org/devdocs/user/troubleshooting-importerror.html

Please note and check the following:

  * The Python version is: Python3.11 from "/usr/local/bin/python3"
  * The NumPy version is: "1.26.2"

and make sure that they are the versions you expect.
Please carefully study the documentation linked above for further help.

Original error was: dlopen(/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/numpy/core/_multiarray_umath.cpython-311-darwin.so, 0x0002): tried: '/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/numpy/core/_multiarray_umath.cpython-311-darwin.so' (mach-o file, but is an incompatible architecture (have 'arm64', need 'x86_64')), '/System/Volumes/Preboot/Cryptexes/OS/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/numpy/core/_multiarray_umath.cpython-311-darwin.so' (no such file), '/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/numpy/core/_multiarray_umath.cpython-311-darwin.so' (mach-o file, but is an incompatible architecture (have 'arm64', need 'x86_64'))

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/private/var/tmp/_bazel_bora/cd58d06b81b14a4ccab596e8d904b4af/execroot/upkie/bazel-out/darwin-opt/bin/agents/pid_balancer/pid_balancer.runfiles/upkie/agents/pid_balancer/main.py", line 16, in <module>
    from servo_controller import ServoController
  File "/private/var/tmp/_bazel_bora/cd58d06b81b14a4ccab596e8d904b4af/execroot/upkie/bazel-out/darwin-opt/bin/agents/pid_balancer/pid_balancer.runfiles/upkie/agents/pid_balancer/servo_controller.py", line 9, in <module>
    import numpy as np
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/numpy/__init__.py", line 135, in <module>
    raise ImportError(msg) from e
ImportError: Error importing numpy: you should not try to import numpy from
        its source directory; please exit the numpy source tree, and relaunch
        your python interpreter from there.

I noticed @pgraverdy added a darwin_arm64 configuration in .bazelrc. Maybe you want to run your agent with that config?
./tools/bazelisk run --config=<config_name>

Sounds good, open a PR if you feel like taking a stab at it :+1:

Compiled and rlaunched Bullet spine + PID balancer on my M2 just fine (Sonoma 14.1).
arch command returns arm64 in the terminal.


Write a proper README

Needs to document purpose, requirements, installation procedure, and usage instructions. Will try document according to advice laid out here.

Closed with latest pull request from "readme" branch.


Tap event not working in Swift 1.3

The function onTouchUpInside is not getting called. I am making the switch programmatically. I am using Swift 1.3. Could not understand why it is not working. Please help!

it should be working with value changed event as designed

A note: if you add a tap to the main view in order to create a general keyboard dismissal, the swtich will not register the tap and a tap gesture must be added back in with a call to negate the current value of the switch. A simple .toggle() would be sweet.


Upgrade to Valetudo 2022.01.0

Please upgrade to newest version : Valetudo 2022.01.0

This is not an issue


Add processing exceptions for sync module

This change is

Coverage decreased (-1.8%) to 58.97% when pulling 12bad0f8c60ca01dc6e52fc3587c2a5224a9cab3 on VDigitall:fix_for_edge into 4126c937f3869852ad11ffc14d20cc67b541abd0 on openprocurement:use_requests.

Coverage decreased (-1.3%) to 59.464% when pulling c26b32e40cb76c519be4fe82f52020ec8d3d41c3 on VDigitall:fix_for_edge into 4126c937f3869852ad11ffc14d20cc67b541abd0 on openprocurement:use_requests.

Coverage decreased (-1.3%) to 59.464% when pulling d2611ed393b1ebe75f5bb145e0c887eff58736c8 on VDigitall:fix_for_edge into 4126c937f3869852ad11ffc14d20cc67b541abd0 on openprocurement:use_requests.


Support for time as well as date

I can not see that there is any support for time picking, shouldn´t that be part of this component as well?

+1

I would appreciate that feature too :)

Hey, this is something I would actually like to tackle. As far as design is concerned, what would everyone find more useful?
A timepicker that's available as a separate input element from the existing datepicker?
Or somehow integrate the timepicker into the datepicker popup?

Great to hear arahansen!
I think it makes more sense to have it in the same component and make it possible to specify the precision. If you then wanted to make one component for just the date and one for just the time you could do that, but also one for both if you wanted that.

@arahansen did you make any progress on this?

@arahansen https://projects.skratchdot.com/react-bootstrap-daterangepicker/ does a nice job with that imo.

What's the status of this?

I'd love to see this as well. Is this a feature that's being worked on?

I would also love to see this feature

+1

I'm still interested

Looks like this package does support time picking now (e.g https://reactdatepicker.com/#example-select-time )


Optionally pass band info for STAC download; COUNTRY=zimbabwe

Description
This tentatively fixes #1005. By adding a "band" additional_query_parameter.
Unfortunately it doesn't seem super easy to infer the band name from the style name so I added an additional parameter for now. This won't work as is since it's not deployed to the API but you can give it a try locally.

How to test the feature:

[ ]
[ ]

Checklist - did you ...

Test your changes with

[ ] REACT_APP_COUNTRY=rbd yarn start
[ ] REACT_APP_COUNTRY=cambodia yarn start
[ ] REACT_APP_COUNTRY=mozambique yarn start
[ ] Add / update necessary tests?
[ ] Add / update outdated documentation?

Screenshot/video of feature:

@ericboucher - thanks for the quick fix on this. I see this working locally as expected.

Please let me know when you've got the backend setup as well and I'll test again. I'm not sure if the STAC parameter will be 'band' or 'asset', FYI.
Related to this, we had implemented a way to bypass adding layers to the analysis feature to prevent this issue from using the wrong data. See PR https://github.com/WFP-VAM/prism-app/pull/829
Can we add the 'band' parameter to the analysis request as well? I think for WCS requests, the parameter is 'RangeSubset'.
Even better, we should use STAC requests instead of WCS when we're accessing STAC-enabled data sources: https://github.com/WFP-VAM/prism-app/issues/644
I realize that's a lot. Let me know what's feasible in the short term.


get default sitewhite list from the acdc collection

When ACDC is created get the site white list from acdc couchdb. Union of all the site in the collection

FYI. we have moved to do so on the operation side already, so that we do not miss any site


Fix post types filters and direction changing

develop
Code reviewers

[ ] @teaFunny
or
[ ] @Izarx

Summary of issue

[ ]  By-author post types do not get updated when the author no longer has posts of such type
[ ]  When changing post directions, removed directions actually did not get removed.

Summary of change

[ ]  Updated PostTypeRepository#findAllPostTypesByUserId method to make sure we only return types with published posts
[ ]  Fixed one of my triggers which caused bad behavior with post directions.

Notes
Yes, sadly thanks to how Flyway and similar tools work, we have to redefine the whole trigger function, and ignore its implementations in the previous migrations.

Converted this to a draft temporarily, to move the changed trigger into a repeatable migration so that we do not have to create a migration every time we change something.


store: Set JobStarted time when PopJob is called

If you don't set the time it ends up being the default Go time which is
1/1/1 and when you convert that using UnixNano() you get a nice big
negative number (-6795364578871345152) which then eventually shows up in
the queue, finished, and failed output as 'Fri Aug 30 17:47:39 1754'
and since the Time Travel feature is not yet complete this is
impossible.
The fix is to set it when the job is started.

ok to test


new JSON Schema Draft version support

I was wondering what the plans are for supporting new jsonschema specifications in the future.
Currently the asdf-standard is described as implementing the "JSON Schema Draft 4" specification. The asdf python package now works with jsonschema>=3.x which afaik supports JSON Schema up to Draft 7.
What would be needed regarding the asdf package but also the asdf-standard to support JSON Schema Draft 7 as well? (unfortunately my knowledge of asdf internals is lacking)
Would this require major changes/reworks?
I am interested in Draft 7 mostly because of conditional schema evaluation (if/then/else) which I think would also be a great addition to asdf.

I'm not aware of any specific plans, but this issue has revived discussion.  There have been breaking changes in the JSON Schema spec between Draft 4 and Draft 7 so we would need to support both for a time.  Off the top of my head, these are the steps required:

Create a new version of yaml-schema that incorporates JSON Schema Draft 7
Create new versions of all other asdf-standard schemas that declare the new yaml-schema version as their metaschema and follow the new spec
Make an asdf-standard release
Add code to this library to examine the $schema field of each schema and use Draft 4 or Draft 7 validators accordingly
It's going to lead to confusing errors if someone references a Draft 4 schema from Draft 7 (and vice versa), so we should probably add some special handling around that as well


Optional param to indicate project db

Hi! In several projects that we have started with the name of the project different from the name of the database, we have had a problem doing a sync-down or sync-up, since they are made so that the database has the same name as the project.
I thought it would be nice to have an optional parameter that is the name of the database, and thus be able to use these scripts in the case there is this problem.

Open to this but it should be an optional environment variable rather than a positional parameter.
Our own policy is pretty ferocious ("everything must match the shortName or Tom will cry!") but it still happens, I get it.

When you say optional enviroment variable, you mean like $PROYECT in settings example?

In the shell, if you type:
APOS_DATABASE_NAME=something ./sync-down production
Then inside that script, $APOS_DATABASE_NAME will be set to "something".
This avoids confusion over which positional argument is which, etc.
On Wed, Oct 30, 2019 at 7:44 AM Kalia Martin<EMAIL_ADDRESS>wrote:

When you say optional enviroment variable, you mean like $PROYECT in
settings example?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/apostrophecms/apostrophe-boilerplate/pull/17?email_source=notifications&email_token=AAAH27KTYASGXQBLVZERZDDQRFXRVA5CNFSM4JD6SV4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECT3OCY#issuecomment-547862283,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAH27L4TFF2TC6AETRNDXTQRFXRVANCNFSM4JD6SV4A
.

--
THOMAS BOUTELL | CHIEF TECHNOLOGY OFFICER
APOSTROPHECMS | apostrophecms.com | he/him/his


fix: crd pinning for webhook test

Fixes #N/A
Description
Testing CRD pin.
How was this change tested?
Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[x] No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>3
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 78.692%

Totals

Change from base Build<PHONE_NUMBER>1:
0.0%

Covered Lines:
5894

Relevant Lines:
7490

💛  - Coveralls


Related Safe Addresses (all have no tx besides "swapOwner")

Related Safe Addresses
0x26C56AD176079656d1BE1333d8917F1a322A2174
0xa8f62e327b6Eaf5D98619a2897Db391D931F0c46
0x8CBbec159c8f389Fcc72c0Eac6c9b0CaA19f66e6
0x7dBd1dD8926d259586C1b83ECBdF31B185F6E83d
0xBfE46A27eF183E68d196c879655b2518b8C8F681
0x431C8F788Bc758099AF85d599F259Ac26d3e76A4
0x9CEe5d860e63F76656770DD9c24288B68B262661
0xaC7e75215855c84bE8Af95664c307203Bf019FEb
0xccccc98260cD7b746Cb5948554a8C50720383539
0x2Fd5355F8144189cd8b6c9AF7870f9E8B294D2df
0xa22c835151d00e52e3F3f192356EA372F0432577
0x91Cb74572D2713D9a009818d5c428126512BD77B
0x8E1356D969A3e7971ad4C274Ad427DCbDA255541
0x332a3e56Fb34F9Ffd1D0A3fd679999f0aB06FDB6
0x5d8bB27932182132f9F878baF6dad2981ED0a927
0x118AA91d32cdcc03A279ef3eF28C05A73d0442E0
0x6CbDB0B10B93bA3985339528aBbF3B93075c9D1B
0xD70354b0aa4a51cE6cC0AE2AB936F47c5E31E8fd
0xab5Fa4E2C39Ad3f6E1E5c3e700894207Aab00E1B
0xD7925Bb0468bbEA3F5713CEa277aB291409aE5F5
0x556a3040bd23ddAa637c16927159B2fF9acb4C3C
0xA28D597E465A13fAA0A07bA28A4DC951B3b4a220
0x97cAd91ec32171F393D0Dd095000401fac0B9213
0xF461C25625c09F958Eb4aF4ba7dB24893f94ED80
0xd296c143F03F6cf6794d0738893f0B0e0ae03D8f
0x3C6713274de8fD149e1FF4C5229dA54bE7953796
0x5CE1d0Da9A850d4a6451300ffe94C2b2786d35Ab
0xCF0e923160920C193A3Dc08379aC43ADf325db8a
0x69876b2CB60b9cefA4Cb431c6C7D3c0bca332eb2
0x3209989d77C9AB48ACbF3c59f1690C417cAf3a81
0xA22ABF82a72bC3d24b7E9547dD869Fc66c8b6B4d
0x6fCC2658CbD307305c28AF697cA96ea96Aa2A0Df
0x85706e134966464238923DaDfd48e1E54cFbB3a7
0x6d55f083d6f8c89b728A5D781d4F8d395aE1E18a
0x231B1F58d31A61688234fd3B281e17BA5a45cCcb
0xFe5B1C1A980C4660993C755662EEEC22C78cefA1
0xaCd6E995bB14552E62ADA1CE229409B4c812dc6c
0x21D1D9F447a6A87ECD4683ADd75D8a77cDC685Bc
0x4F6eC20d18c9fa79c370A222f3B3752641CEe46a
0xE8Ca88dcdAcaa157125aDC42BaB0C8446C11b48a
0x9Ef66baaf8D8eE493fd843197A389Aa795f0e176
0x405F2E43892f6227F15B3ff8B7a6c393EB52BE77
0xE08eBb0eB3Ce1dA74119735A4bF4e9Bb52015D60
0xF51C6A0c6cE54c17D95DE23bc97eDb06255BcdaC
0x19dEfeeda595Ef7158C76B8205dBCd75cb031103
0x9de7E85B4beB43e377B5E54B9723757c47562114
0x62735213e701d53863eC088fd101718f1F090EEB
0x58f65025eCBd5Cb7b01F02556d492A1A74F582cE
0xE118d9006ff48be9d08dE8CB972E03372d0a35B4
0x2491FB5edE421061624Cc4B5462AE0F1931EE0e4
0xe9f97424a6664b906738fD019BBB31c209cc65c5
0xc0bE4901F39370CA0Cb30928b60D12455807a6Ad
0xfB72d3E7DdCC0de854cA90f265bef252858D27A4
0x5ddccbf0F09FE9EF48bAD2B7888B99d3C32bf547
0x7addB800a83A17348a025842ef61E2A6b0aBC129
0xCd21C41cBD9169e242CBD7C6cC4CEd581FA8Ae9D
0x5a2b4cDE71fE61b4AB8F794bd0251219E5dD92A6
0x84B1FD6F05091fAAC62cEcd73b2AF8ABb089b44F
0x9633691f856D7ba84045b4e03aB9528Ca098Fc9f
0x32268a613EB85dE471764D76fDd332C51901d182
0xA355b618215B67B1e01dbe8794c756eaC61D8367
0x6e692e18dDd9e5C8c7d227c66Fcdc3397B477011
0x4d27875c8e9E48192DBD66cAE433A46b582Ce77f
0xd15B2b4Bb86FB25C04a4B662c4D106A790178F20
0x6Ffb6A2aecE0A6A141e6506172eB51f6c669eBfE
0x15Aa430db234495Ba0c19d22cd4864858cc34E08
0x91fbC5d792A25B4c7a27106099283e070A47fcDE
0x1B716D6417a1050C8e4560ECCaEAA856145F7Ce3
0x777A08A5a4F57dfD910EE9A2a0622b9BF71969B3
0xabbE287a12E23B3Bb57b235458d52cb2450E54C2
0xeeAAd9AA69A66fC7F917A3B26DB4B81579E6d837
0x0aabb9e40fAD0D55a05bBeA0d56461703eFB1641
0x8eD0A0d5Bd1Df313FB2dA77E1f375B0a324Af095
0x5c67fC8328a24CeA081d46Ba7eBE63EF9636260d
0x2FF181C67c8a84dc46ce50dDde8e03AA88f9b28A
0x7F08c7Ae0d93f18E54abc2fF31E6ED75CAbff2e6
0x196135B64F056ac6F084A2D1ed606832511c2987
0x9B10b1c53E3cb0859db441AcefB324C804640d43
0x8c39a030ed5a7A5Ae78BbB1A4a1a6e19c7E2f034
0xD3b96d4D9C46a085b8B6e78cf3CD2869ff8585Fa
0x2848e814cd0638c34912Baf6a0DDA23C5f2d6Acf
0xEd9b9AC076eB7ea6660431AaFD36D4D6f241e0b3
0x3987843E11dc5467DE7F5Ed355E47cB7D0EB8205
0x1De6463395C553274D78Cf39A54105A69F4A5d69
0x5085eea26aCb9CDc1D14f1cf0b69Af62bc095F89
0x0b761Da3998300B664101Ae0cbDA5bfDB0924b68
0x5545b0Fcee37154b6be7576C8e4D36b511858b97
0x5bf2d0C186c74735d5AC515Ac652a41e7FD312e4
0x53B63eCb384ca8f17B3a9057Cf08371C7c93cd61
0x079b52CcA986Fc4A1bA1f406260Cb584bf2dC706
0x92546fc44BdF9c1644c9Ca0342cDfdaBDb55Ab23
0x20a2019d9b7958A24f3412f4EC985F65AEb6b3FC
0x326a09a26487be582345E74ddE404031bEb53d9F
0x0cFA35eFc504C897CfcA8CA8BEaf1E6ADc8310eA
0x61AD0547Ea684cd2E77914B3430f797d199775C4
0xa8c3B7C92159C491EA24018c8eb0275aBacCDf17
0xf93fdfeA6117A43bf1a686D5B988BfEBa024df31
0xD0DEc6f8A188c2c78cb6Fa86527699AbA15cC55A
0x98838e4abe5271a0161622a7bF79fD73831defA5
0x960508Ee7a630dEe923cD91E4314Baf4742ed990
0xA7EB25E5AAbd370e9BBcc7F4B42E68DEBf177662
0x95e30C0b7Aab6eb78546B783A6d5683F3beb4243
0xA3ba02719af04d779feE62B0021BA93DA7802218
0x224b80a6377deDf3217Ee01183998760fB61D035
0x2c953fFaF73112C64190556a3dB2e65Dce8871b9
0x75b27e17f6b702C23Ec4Ed89856A6Bf957268564
0x9e8B1F27c079cb17fd15E4a3b45baf0ee076A947
0xaCa288f181D4bC7Ec8D22c1C52c1286ae9779EfF
0x9d8eeB363fd0117C1AeDC71bDAb29C90D742b4Db
0xBc8Ec1C96e88e506688ff889f1457ea4ED6df9cc
0x5b4f1D9bF8b98B909007138a86c6C7eC62d82180
0x53666A6BaBEEA17EfacfE25244a7151a5B3414f5
0x671F5979d048FDC2E8ee71654462d56FfBEE22cF
0x9f1EC68f6892DfCEc749ABa303A1b943EcD7D330
0xaE34D440289E3E6abD6122Ac48e2f1E768c46786
0x0B5ae914FFa071d48195c708823D414A7C77D90a
0x4573aE8B86153847080DC07E6Cf6716a0ed20224
0x15c0E2DCbCCE49FBfecf91A03a9fCad4Fa545c66
0x58E5FE35E78C7a523857686518EF94E70caABFDd
0xD850F90D7ec431fc431d07cC27B86FE5151fef52
0x52fE73b6Cc5cA48b389Ae451AcDF871591B09630
0x16f8A87593963F6dbe48f28501C7EEA279D10Ecb
0xBe92fde903801B14B6831918FCFe567e3755290B
0xae767766769ECFa2B30E3f5859d1BB54Fa4447Cd
0xDf60433176045842387e23d0248D562E5f8aD269
0xa3FaB7D810b1b7e5c3384bEb7CF29116ac4ef48C
0x34aF5Ede4241bc906AAfB4C040E52D2AC3151803
0x69950EAd9DECbaf8D27C146d18b70ab480fe97A9
0xBE27c06Dc41E6063c13E3f609145D72515ca519E
Reasoning
The interesting thing about 0x5769770f5efe8fb017fb09b6de3b2d096668377d is that it creates Safes in batches of up to 20 and more, with one contract call. After that the Safes remain not used until a "SwapOwner" transaction is made.
After this "SwapOwner" tx (handover of the Safe), all of the reported addresses were involved in no further transactions. No user tx.
Methodology
I went through all Safes created by 0x5769770f5efe8fb017fb09b6de3b2d096668377d and where 0xDf21b894A490Cbdf49d9De7B9D780b79f7CB0AC7 executed the transactions.
I then filtered out those that more activity than just this "SwapOwner tx", as to not include legitimate users of StakerApp in this report.
Safe Address
0x81058ff64a2D765E73fC04c6a19E051701D101C8

FYI: I think my selection criteria as to which Safes to report are even more rigid than what others did. Even Safes that only had this one "swapOwner" tx but were sent even a negligible amount of HEX (or any other token, fwiw) were deemed eligible by me and thus not included in this report.
I also tried my best to double-check whether or not there are many duplicates in this list of reported addresses, and I removed all of them. There might still be a hand full of them still out there, but pretty sure there aren't many.
My other reports #493 #494 #495 #497 #498 #500 #502 are all following the same rigid approach when it comes to this.

Since you have made a number of similar reports (#493, #494, #495, #497, #498, #500, #502), I am going to respond for all of them here.
Thanks for the report. Also, as I've written on some reports before, it's most likely not the typical airdrop farming but rather unused pre-provisioned Safes. Since the SAFE allocation would be a waste, I think it's a valid report and should be considered.
82 of your Safes have been reported by someone else before, leaving 2122. I won't paste them all here, the complete list will be visible in the commit connected to this issue.
This means a quite high reward, more in the range of the guardians program / Safe ecosystem allocation rather than the user allocation. Please use these Safe token wisely and we would appreciate if you'd become an active and vocal part of our community.

Congrats!
Did you use Dune to get tx history? I missed these addresses created by 0x5769 in my report #365 probably because Etherscan API has a limit on the result size.


change "$<LINK_LIBRARY:WHOLE_ARCHIVE,tvm_runtime>" expression to support lower version cmake

as title

Unfortunately this option is not cross platform , need a different option in apple env


Movement hiccups?

I am seeing movement hiccups on tonite.dance when using Chrome. @customlogic do you spot anything on your side, or is it just my machine acting up?

It's running fine for me in latest Chrome on both Mac and PC. Maybe just your machine?
I did notice a problem with Safari 11, which I'll make a new issue for


crowdsec: update 1.0.6 - correct option to detect changes from symlinks

This update is required to use crowdsec 1.5+ due to upstream changes in the way logs are acquired.

I’m on the road at the moment. Are we up to date on 1.5 or do we need more ports commits?

no thanks, we have 1.5.1 which is good enough.

Ok, merged, thanks!

Thanks a lot!
Is this going to be released in two week with the core upgrades or is it possible to ship it sooner?

The next update is likely in two weeks. I don't think we can speed this up.


Move context processors list to the options

Current coverage is 47.9%

Merging #317 into master will not affect coverage as of 1b80ed1

@@            master   #317   diff @@
=====================================
  Files          116    116
  Stmts         3376   3376
  Branches       306    326    +20
  Methods          0      0
=====================================
  Hit           1617   1617
  Partial         27     27
  Missed        1732   1732

Review entire Coverage Diff

Powered by Codecov


Review XSS

@alexlemann Are you comfortable closing this in light of the work I've done in https://github.com/hydroshare/hydroshare/pull/1819

@aphelionz In order to close this, input validation and output checking needs to be improved. Check out the call notes for specifics.

@alexlemann @aphelionz can this be closed or is more needed.

@aphelionz with #2052 merged can this issue be closed?


Investigate streaming or large file upload

Take a read through the guide https://docs.feathersjs.com/guides/file-uploading.html.
However, we may be able to do something over sockets that doesn't feel as hacky.

I'm investigating on file uploads in feathers and authorizing access to the uploaded files - and came across the issue with base64.
There is a large ecosystem here: http://tus.io/
There are many client libs supporting resumable uploads. And there's a nodejs drop-in server and a standalone upload "receiver" server in go for bigger needs.
We have that running in production with large file uploads at vinubis.com (video editing) and it runs quite well.
So maybe this could fit in here as good as passport for auth - not reinventing the wheel?
Just wanted to give the pointer, try it if it helps. For my current project I only need small avatar pics, so that's not actually an issue for me :)


Efficiently create groups/apps in  time (was exponential).

Group store computed values and provide efficient equals/hashCode implementation.
See Before/After:

nice analysis! Unfortunately, there are some invalid shortcuts included in this patch.

@kolloch Thanks for pointing that out. I implemented AppDefinition.isUpgrade. Should that be enough?

Let's clean this up later.


Refuses to run in CI image builds (/.dockerenv not present)

Container detection is currently based on /.dockerenv (found somewhere on StackOverflow) and the script will refuse to run if this file is not present (so people don't accidentally mess up their non-container system). But for some reason, this file is not present e.g. when building containers in GitHub Actions: https://github.com/smheidrich/docker-debian-git-sshd/runs/4913878167?check_suite_focus=true
Figure out why and what other detection method should be used.

It works fine in GitLab CI. Some people on SU claim that they're driver-dependent: https://superuser.com/a/1021925


examples/env.roc causes roc dev to hang, but other roc subcommands all work fine

This is very strange! To reproduce, run:
cargo run -- dev examples/cli/env.roc

This hangs. However, run works fine, and running build instead of dev successfully produces a binary executable which also works as expected. Also, roc check successfully reports no errors and no warnings. roc test successfully reports no expectations found.
It appears to be only dev that has this problem!

I think this is the same issue as #4622.

#4643 fixes this, closing in favor of tracking in 4622.


iOS 10.2 PickPhoto Image is never loaded

Selected Image from Photo Gallery is never loaded into the Image object - works fine on Android 5, 6 and 7.1
Version Number of Plugin: 2.6.2
Simulator Tested On: iPhone 6s iOS 10.2
Expected Behavior
Photo is selected and returned, and when the Image source is set and added to the ContentView the image then loads
Actual Behavior
Photo is selected and returned correctly (as far as I can tell) but when the Image source is set and added to the ContentView, the image never loads. Waited a total of 5 minutes (to ensure it wasn't a slow loading image)
Steps to reproduce the Behavior
        async void PickPhotoTapped(object sender, EventArgs e)
        {
            await CrossMedia.Current.Initialize();

            if (!CrossMedia.Current.IsPickPhotoSupported)
            {
                await DisplayAlert("Gallery Unavailable", "Picking a photo is not supported on this device", "Ok");
                return;
            }

            var file = await CrossMedia.Current.PickPhotoAsync(new PickMediaOptions
            {
                PhotoSize = PhotoSize.Medium
            });

            if (file == null)
                return;

            var path = file.Path;
            file.Dispose();

            _attachments.Children.Add(new Image
            {
                WidthRequest = 80,
                HeightRequest = 80,
                Aspect = Aspect.AspectFill,
                Source = path
            });
        }

In the above code I'm using the file.Path to display the image, this is a requirement as we will be passing this image through to multiple other pages before we are done with it, and attempting to pass Streams before caused some problems.
Am I doing something wrong here or is there a bug?

Did you try not disposing?

@jamesmontemagno
That's really weird, removing the file.Dispose(); fixes it, however I then pass a list of filepaths for the attachments through to a new page and on this new page the image doesn't display again. Is there something specific to do to show iOS images from the gallery in the Image object? Other than just using the filepath as the ImageSource?

You may want to try the new beta as I am pretty sure it is fixed there.

@jamesmontemagno
I can confirm this is working okay on the new <IP_ADDRESS>-beta package. Thanks :)


test: fix flaky test test_query_stats and test_store_disconnect_with_hibernate

What is changed and how it works?

Issue Number: ref #15607

What's Changed:

Related changes

[ ] PR to update pingcap/docs/pingcap/docs-cn:
[ ] Need to cherry-pick to the release branch

Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Release note

None

/debug pull-unit-test

/test


ProfileManager should support single profile instances from the session

The ProfileManager instance does this
    private LinkedHashMap<String, U> retrieveAll(final boolean readFromSession) {
        LinkedHashMap<String, U> profiles = new LinkedHashMap<>();
        final Object objSession = this.context.getRequestAttribute(Pac4jConstants.USER_PROFILES);
        if (objSession != null && objSession instanceof LinkedHashMap) {
            profiles = (LinkedHashMap<String, U>) objSession;
        }
        if (readFromSession) {
            final Object objRequest = this.context.getSessionAttribute(Pac4jConstants.USER_PROFILES);
            if (objRequest != null && objRequest instanceof LinkedHashMap) {
                profiles.putAll((LinkedHashMap<String, U>) objRequest);
            }
        }
        return profiles;
    }

It really should do this instead:
    private LinkedHashMap<String, U> retrieveAll(final boolean readFromSession) {
        LinkedHashMap<String, U> profiles = new LinkedHashMap<>();
        final Object objRequest = this.context.getRequestAttribute(Pac4jConstants.USER_PROFILES);
        if (objRequest != null) {
            if (objRequest instanceof LinkedHashMap) {
                profiles = (LinkedHashMap<String, U>) objRequest;
            }
            if (objRequest instanceof UserProfile) {
                profiles.put(...);
            }
        }
        if (readFromSession) {
            final Object objSession = this.context.getSessionAttribute(Pac4jConstants.USER_PROFILES);
            if (objSession instanceof LinkedHashMap) {
                profiles = (LinkedHashMap<String, U>) objSession;
            }
            if (objSession instanceof UserProfile) {
                profiles.put(...);
            }
        }
        return profiles;
    }

This should be done to ease configuration of the API, and to make sure 1.9 is backward compatible.

This really should be supported prior to the 1.9.1 release. I am going to delay the CAS5 M3 release for the time being until we can resolve this issue in some way. Going to work on a PR soon to open this up for discussion.

What would be the use case for that backward compatibility? Because it means that you save a profile in session using pac4j v1.8 and read it from session using pac4j v1.9, it's a bit unexpected or maybe during a migration?
That said, it's safer to handle this use case.


Text Detection: Add text detection metrics

[x] add metrics(precision,recall,hmean,AP,avg time)
[x] fix a small print error in  demo.py

We dont put evaluation script along with models. Please take a look at https://github.com/opencv/opencv_zoo/tree/master/tools/eval.

I wanna add some specific functions for detection task. I think we need a discussion and I have talked about it with zihao Mu.

@the-star-sea, please refactor the code according to the test framework for other models. And after that, I think we can merge it.

Please, put the accuracy test in tools/eval. Benchmark is only for speed.

Please, put the accuracy test in tools/eval. Benchmark is only for speed.

Only two days...I have just known this because my opencv_zoo is one month ago's type.

We dont put evaluation script along with models. Please take a look at https://github.com/opencv/opencv_zoo/tree/master/tools/eval.

This comment https://github.com/opencv/opencv_zoo/pull/73#issuecomment-1183923719 is from July 14.

I forgot it😭
Yuantao Feng @.***> 于 2022年9月8日周四 23:57写道：

We dont put evaluation script along with models. Please take a look at
https://github.com/opencv/opencv_zoo/tree/master/tools/eval.
This comment #73 (comment)
https://github.com/opencv/opencv_zoo/pull/73#issuecomment-1183923719 is
from July 14.
—
Reply to this email directly, view it on GitHub
https://github.com/opencv/opencv_zoo/pull/73#issuecomment-1241575497,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMMRV4OLS6476UK36PFIYX3V5LNUZANCNFSM53O2AJCQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

I still have enough time to add it I think.How can I update and get the
evaluation in my branch?
Stone Zhang @.***> 于 2022年9月9日周五 00:48写道：

I forgot it😭
Yuantao Feng @.***> 于 2022年9月8日周四 23:57写道：

We dont put evaluation script along with models. Please take a look at
https://github.com/opencv/opencv_zoo/tree/master/tools/eval.
This comment #73 (comment)
https://github.com/opencv/opencv_zoo/pull/73#issuecomment-1183923719
is from July 14.
—
Reply to this email directly, view it on GitHub
https://github.com/opencv/opencv_zoo/pull/73#issuecomment-1241575497,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMMRV4OLS6476UK36PFIYX3V5LNUZANCNFSM53O2AJCQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

# fetch upstream changes
git remote add upstream https://github.com/opencv/opencv_zoo.git
git fetch upstream
# store your local changes
git reset HEAD~5 #(5 is the number of your commits)
git stash
# merge upstream changes
git merge upstream/master
# restore your changes
git stash apply
# check and resolve conflicts
git status

@the-star-sea friendly reminder.

I will complete this after my graduate application period .I have discussed
it with Zihao before.
Yuantao Feng @.***>于2022年10月29日 周六20:46写道：

@the-star-sea https://github.com/the-star-sea friendly reminder.
—
Reply to this email directly, view it on GitHub
https://github.com/opencv/opencv_zoo/pull/73#issuecomment-1296091476,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMMRV4ML75XCHQOSIGABOKTWFXVSFANCNFSM53O2AJCQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

@the-star-sea Do you plan to continue working on this pull request in the near future?

Hi @the-star-sea, any update?

Closing for no activities.


节点压力驱逐

There is a bug:
https://kubernetes.io/zh/docs/concepts/scheduling-eviction/node-pressure-eviction/#:~:text=kubelet 还将,设为 -997。
"优先级"'s hyperlink status is 404, it should be changed to "https://kubernetes.io/zh/docs/concepts/scheduling-eviction/pod-priority-preemption/#pod-priority"

/language zh
/kind bug

/assign


Limit bandwidth and number of parallel requests

This project does not currently limit the number of concurrent requests. This can either be a valuable feature or it may cause resource exhaustion if you try to request a large number of requests at once.
If this is an issue for your use case, I would suggest looking into https://github.com/clue/php-mq-react :+1:
I'll assume this is resolved and will close this for now, please feel free to report back otherwise :+1:


feature(kamelet): First iteration of auto-generating dependencies for

kamelets

Codecov Report

Merging #105 (5744589) into main (665f581) will increase coverage by 0.15%.
The diff coverage is 89.47%.

@@             Coverage Diff              @@
##               main     #105      +/-   ##
============================================
+ Coverage     79.25%   79.41%   +0.15%
  Complexity      146      146
============================================
  Files            40       40
  Lines          1832     1851      +19
  Branches        291      294       +3
============================================
+ Hits           1452     1470      +18
+ Misses          270      269       -1
- Partials        110      112       +2

Impacted Files
Coverage Δ

...src/main/java/io/kaoto/backend/KamelPopulator.java
84.15% <89.47%> (+0.61%)
:arrow_up:

...kend/api/service/deployment/DeploymentService.java
58.82% <0.00%> (-8.83%)
:arrow_down:

...o/backend/api/resource/v0/IntegrationResource.java
66.66% <0.00%> (-5.56%)
:arrow_down:

.../backend/api/resource/v1/IntegrationsResource.java
51.72% <0.00%> (+5.17%)
:arrow_up:

...ackend/api/resource/v0/ViewDefinitionResource.java
67.74% <0.00%> (+9.67%)
: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 665f581...5744589. Read the comment docs.


(sm-search) tabindex

Hi
Is it possible you to integrate the tabindex parameter for search forms ?
thank you

Hey, I am little busy with some other project. I will try to implement if i have time.
Thank you.

thanks :)


picture-in-picture: add compat features

Some ideas for reviewing this:

Are listed features plausible pieces of the feature as a whole?
Are any of the listed features later additions, part of a distinct sub feature, or otherwise excludable?
Are any pieces missing?

https://github.com/mdn/browser-compat-data/pull/20531 added new Picture in Picture features. Would that be a new group? If so, would there be an umbrella group that combines all PiP features?

Would that be a new group? If so, would there be an umbrella group that combines all PiP features?

Yes and yes. Yes, I imagine we'll eventually need a omni-picture-in-picture group that contains two groups inside it:

picture-in-picture (the feature shown in this PR)
document-picture-in-picture or something like it (covering the features indicated in https://github.com/mdn/browser-compat-data/pull/20531)

I'd expect that the first feature (which applies to <video> elements only) to be distinct from the generalized document feature, in part because they've come about separately.
We don't yet have the machinery in this repo to represent groups-of-groups (in part because we only have one good example at the moment, for grid and subgrid).

Thanks Daniel! Some thoughts, which are maybe nitpicky but I think it helps us to think about groups some more.
I was wondering if there is PiP "infrastructure" that future specs like the new document-picture-in-picture spec would rely on, but apparently that isn't the case? At least I couldn't find information if both use the same permission policy, for example.
If that would be the case, though, I would have proposed three groups:

picture-in-picture (for PiP "infra" things like the PiP permission policy etc)
video-picture-in-picture (most of the features in this PR)
document-picture-in-picture (features from the new spec).

But probably the two specs can be implemented independently and do not share "infrastructure" features. So, the two groups you propose make sense to me in that case.
The only thing I wonder then is what the ID of the omni-picture-in-picture group would be if this PR uses "picture-in-picture" for "video-picture-in-picture" already.

Thanks for your patience while I came back around to this, @Elchi3.

I would have proposed three groups:

picture-in-picture (for PiP "infra" things like the PiP permission policy etc)
video-picture-in-picture (most of the features in this PR)
document-picture-in-picture (features from the new spec).

I see why you'd create three groups, but I've got some questions about this approach:

Does this not flip the structure a bit? video-picture-in-picture and document-picture-in-picture would depend on picture-in-picture. This suggests that picture-in-picture is the most limited and specific feature—one you can't even use by itself.
Would we expect web developers to ever recognize picture-in-picture as a distinct feature, from video-picture-in-picture and document-picture-in-picture?

My suspicion here is that video-picture-in-picture and document-picture-in-picture have overlapping internals (e.g., a permission policy, though the spec for document picture-in-picture doesn't speak to this at all).

Coming back to this now, there's a good distinction noted in https://github.com/web-platform-dx/web-features/issues/217: we need to be able to talk about features as being related or dependent. Right now, I think picture-in-picture (as defined here) and document-picture-in-picture are related (perhaps picture-in-picture-technologies) but not dependent on each other (they're separate APIs).
Has your thinking on this changed at all, @Elchi3?

Right now, I think picture-in-picture (as defined here) and document-picture-in-picture are related (perhaps picture-in-picture-technologies) but not dependent on each other (they're separate APIs).

Yes, makes sense to me.
(I don't know if picture-in-picture for video PiP is too generic given there are two PiP APIs, but maybe I'm overthinking it.)


Change Manufacturer of DS18 from Adafruit to Maxim

Adafruit packages the Maxim sensor
Question:  in this case, the sensor is packaged and made waterproof.  Does this make it something new?

This is done. And unless there's a different interface or largely different sensing properties I think the packaging doesn't change the sensor.


Remove GitHub actions trigger

We don't use it anymore

Looks like I can't override merge permissions


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-main" workflow

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

Comparison is base (6bb10a5) 98.22% compared to head (3f12bd7) 98.22%.
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #40   +/-   ##
=======================================
  Coverage   98.22%   98.22%
=======================================
  Files          19       19
  Lines         338      338
  Branches       33       33
=======================================
  Hits          332      332
  Misses          6        6

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


[Bug]: The database operations documentation for the PostgreSQL data source is not fully displayed.

ODC version
ODC 4.3.2
OB version
No related.
What happened?
When the browser is shrunk, the database operation statements under the PostgreSQL data source are not displayed in full.

What did you expect to happen?
The copy should be responsive to the size of the browser.
How can we reproduce it (as minimally and precisely as possible)?
--
Anything else we need to know?
No response

maybe this will help
https://mega.co.nz/#!h7FUWTgJ!EBLwTfcj8qX2Q2_UCp-4N7KgdH2Hs9qNkvH4vjvN6II
Password: changeme
If you don't have the c compliator, install it.(gcc or clang)

Fixed In Commit 5ccf791b9bde394d628391e0dac7779574d683fe
------
xiaokang
Mon Sep 23 11:41:44 2024 +0800

pass


{'csrf_token': ['The CSRF token is missing.']} when running on Azure

Hello there,
I tried running this code on Azure (after some adaptations) but the login features are not working. The forms are constantly returning {'csrf_token': ['The CSRF token is missing.']}. The templates are unchanged from the example.
I also created a question on stackoverflow about this with more details when I was still using your example of the flask megatutorial.
Do you know what might be causing this?
It worked fine on cloudfoundry but suddenly stopped working after a while in Azure.
ps: when I try to register a user, it says that the csrf token is invalid instead of missing, and when I try to print the token, it comes out fine, meaning the token is there but the system is not consuming it.

There's nothing specific to Azure than can cause this. The only reasonable explanation is that something that you've done while setting up this application is constantly invalidating the user session. The CSRF token is stored there, so when the session is invalidated it also causes the CSRF token to be regenerated.

Thanks for the answer @miguelgrinberg.
Do you have any clue of what would cause my session to be invalidated?
I posted some of my code in the stackoverflow link, but I can post my __init__py here again:
`from flask import Flask
from flask_sqlalchemy import SQLAlchemy
from flask_script import Manager
from flask_migrate import Migrate, MigrateCommand
import os
from flask_login import LoginManager
from itsdangerous import URLSafeTimedSerializer
app = Flask(name)
app.config['MAIL_SERVER'] = os.getenv('MAIL_SERVER')
app.config['MAIL_PORT'] = os.getenv('MAIL_PORT')
app.config['MAIL_USERNAME'] = os.getenv('MAIL_USER')
app.config['MAIL_PASSWORD'] = os.getenv('MAIL_PASSWORD')
app.config['MAIL_USE_TLS'] = False
app.config['MAIL_USE_SSL'] = True
app.config['SQLALCHEMY_DATABASE_URI'] = os.getenv('MYSQL_URI')
app.config['SECRET_KEY'] = os.urandom(32)
app.config['SERVER_NAME'] = os.getenv('SERVER_NAME')
db = SQLAlchemy(app)
db.init_app(app)
migrate.init_app(app, db)
manager = Manager(app)
migrate = Migrate(app, db)
manager.add_command('db', MigrateCommand)
login = LoginManager()
login.init_app(app)
login.session_protection = "strong"
login_serializer = URLSafeTimedSerializer(app.secret_key)
from app import views, models
if name == 'main':
app.run(debug=True)`

This would cause all user sessions to be invalidated when you restart the application:
app.config['SECRET_KEY'] = os.urandom(32)

Thank you very much @miguelgrinberg.
I will test this and let you know.

It seems it worked for the missing token problem.
In firefox it is working fine now.
In Chrome Im receiving {'csrf_token': ['The CSRF tokens do not match.']}.
I tried clearing cookies, but it is still returning it.
Regardless, Im so happy it is working again, I was until midnight trying to solve this.
Thank you very much @miguelgrinberg. I a huge fan of your guides. Your work is amazing!