fixed for dot-parsed networkx graphs

Hi, while using the dimod library with networkx to solve the minimum vertex cover problem, I noticed that the dimod library is having issues with networkx graph objects generated from dot files using read_dot function.
The dimod function _init_components was using a (u,v) tuple in a for loop. It worked well for all other graphs except those generated from dot files. The quadratic parameter was a collection of dicts which in my case did not always have 2-element keys. When the bias was different than -1.0, the dict contained a 3-element key with a zero at the end (always).
To solve this issue i changed how the function iterates over a quadratic collection to avoid the "too many values to unpack" error.

Codecov Report

Merging #768 (e0097a7) into main (a201e2f) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #768   +/-   ##
=======================================
  Coverage   92.00%   92.00%
=======================================
  Files          63       63
  Lines        4666     4668    +2
=======================================
+ Hits         4293     4295    +2
  Misses        373      373

Impacted Files
Coverage Δ

dimod/bqm/adjdictbqm.py
94.75% <100.00%> (+0.04%)
: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 a201e2f...e0097a7. Read the comment docs.

Hi @filipceglik , thanks for the PR. I think we definitely want to support networkx graphs created this way, but I am worried that the current solution will have unintended side-effects. Are you referring to graphs constructed with read_dot?
Could you post a short example of the code that's not working for you?

Hi @arcondello, absolutely. I have a function in my code which returns the networkx graph using the read_dot function. Perhaps this is a bug in the read_dot function but I wasn't able to track where this might be going wrong. I am pasting the code below. At one point the quadratic variable has keys with 3 items inside of them for the bias different that -1.0.

Please bear in mind that I am not a professional developer, just someone who noticed this behavior for this particular case so please keep me informed on any issues this solution might create and I am sure we can work some correct solution if it indeed turns out to be a bug in the dimod.

Hi @filipceglik , thanks! I actually meant an example of a dotfile, I am not familiar with that format. Sorry for the confusion!
Agree that we should get this working.

Hi @filipceglik , does your program look something like
G = nx.drawing.nx_agraph.read_dot(dotfile)
bqm = dimod.BQM.from_networkx_graph(G)

or are you constructing the BQM some other way?

Hi @arcondello,
I am really sorry, I haven't seen your reply and I just looked at the PR.
This is the most logic of my program, it's parsing the dotfile and uses the dwave quantum computing API to determin the minimum vertex cover of a graph.
I am creating the sampler using
EmbeddingComposite(DWaveSampler(endpoint=ENDPOINT, token=TOKEN, solver=SOLVER))


can you add create if long message

hello sir
can you create if the message is too long or large on font phone size?
thank you

If the device font size changed then the dialog doesn't scroll text, also the button doesn't appear to dismiss or do other action.

I'll check into that ASAP

@fajaranugrah you can grab v1.0.3 now. It should be fixed.

@mjn1369 thank you


New possible feature: [disabledDates]="invalidDates" [disabledDays]="[0,6]"

Hi,
as usual I thank you for your help and great tool.
I was thinking if it is possible to add a new feature for this data-time-picker to disable the selection of specific dates or days (Monday, Tuesday, ...) maybe passing to arrays as input to the component like:
<owl-date-time
                          ...
                          [disabledDates]="invalidDates"
                          [disabledDays]="[0,6]">
                          ...
</owl-date-time>

PrimeNG Calendar has similar fetaure.
It would be great to have it here too.
Again thanks a million

I could also use an eventDate for special days that i want to know when im using the datepicker.

No need for this. Because there is a property [owlDateTimeFilter], and you could provide a function to filter dates. You could read more about this from the README.md and demo page.

Hi @DanielYKPan
thanks a million for your help. I tried it and it works fine.


add support for map_d

This PR adds support for alpha texture maps (map_d), as listed here: https://en.wikipedia.org/wiki/Wavefront_.obj_file

Thanks for the PR! I will incorporate this into a new build (0.1.4) and publish to npm soon.

awesome, thanks! :)


Custom error message for loading incompatible MakeCode hex.

We should find out if there is a more definitive way to determine whether a hex file was created with MakeCode.


Fix URL in openqa-investigate comments (to include scheme and host)

This is likely still not enough because somehow test results don't show up any more and links are longer now, e.g. see https://openqa.opensuse.org/tests/2172606#comments

pair-programmed with mkittler


cleaned up Gemfile, added .ruby-gemset, rubocopped

Minor cleanup and refresh. @lindt Please review, comment, and merge. My team is actively using this tool. 👍

Thanks!

@lindt I know this is an old PR, but I would like to keep up with this gem and breathe new life into it.

@mnohai-mdsol  If this gem does not get resuscitated, you are welcome to use cuke_linter. It does most of what this gem does and is actively developed/maintained.


Test: Create a Phenopacket -

Test :
Create a phenopacket with minimum data .
Verify that phenopacket displays in the list of phenopackets

you can edit phenopacket.

Creation with minimum data has passed.
Also downloaded the json, it checks out okay.
Made an edit.
Downloaded the json, it checks out okay.


Error when executing PixArtCheckpointLoader

I've loaded up the sample workflow and the models specified in the readme. I've redirected the nodes to the correct models and checked that they're loading. When I run the workflow, however, it spits out this error:

Error occurred when executing PixArtCheckpointLoader:
PatchEmbed.init() got an unexpected keyword argument 'bias'
File "F:\Tools\ComfyUI\execution.py", line 155, in recursive_execute
output_data, output_ui = get_output_data(obj, input_data_all)
File "F:\Tools\ComfyUI\execution.py", line 85, in get_output_data
return_values = map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True)
File "F:\Tools\ComfyUI\execution.py", line 78, in map_node_over_list
results.append(getattr(obj, func)(**slice_dict(input_data_all, i)))
File "F:\Tools\ComfyUI\custom_nodes\ComfyUI_ExtraModels\PixArt\nodes.py", line 30, in load_checkpoint
model = load_pixart(
File "F:\Tools\ComfyUI\custom_nodes\ComfyUI_ExtraModels\PixArt\loader.py", line 51, in load_pixart
model.diffusion_model = PixArtMS(**model_conf.unet_config)
File "F:\Tools\ComfyUI\custom_nodes\ComfyUI_ExtraModels\PixArt\models\PixArtMS.py", line 110, in init
super().init(
File "F:\Tools\ComfyUI\custom_nodes\ComfyUI_ExtraModels\PixArt\models\PixArt.py", line 92, in init
self.x_embedder = PatchEmbed(input_size, patch_size, in_channels, hidden_size, bias=True)

Could you let me know where I've gone wrong?

What version of pytorch do you have? I've only tested it on 2.0/2.1 so far. (You can check by running python -m pip show torch inside your venv)

What version of pytorch do you have? I've only tested it on 2.0/2.1 so far. (You can check by running python -m pip show torch inside your venv)

First I apologise for not seeing your reply sooner and thank you for responding. I've checked the torch version and it's version 2.1.1. Will that be a problem?

No that version should be fine. Maybe it's the timm package then? That one I only tested with version 0.6.13 so far, so you could try up/downgrading it to that version (i.e. python -m pip install timm==0.6.13)


v0.8.8_05: Random color age bar is shown

SEVERITY:  Major
MODULE: Pop by age chart
Platform:

Windows 7 / Chrome 48.0
Windows 7 / Firefox  43.0
MAC / Safari 9.0

RELEASE: v0.8.8
STEPS TO REPRODUCE:

Navigate to the URL : http://static.gapminderdev.org/vizabi/release/v0.8.8/preview/popbyage.html
Pop by age Chart will be loaded.
Click “Full” under RESPONSIVENESS
Click “Color”
Click drop down and select “GDP per capita”
Click OK
Click the drop down again and select “indicator/age”
Note that random color age bar is shown

ACTUAL RESULTS:
Random color age bar is shown by changing drop down option
EXPECTED RESULTS:
Age bars color should be according to selected color scale
SCREENSHOT:

Nice, probably because the scale starts at 1 and age starts at 0.

@jheeffer looks like it. the extrapolation of color scales in d3 gives such effects


feature request: --waterfall

how about adding a --waterfall command line option?

Could you explain what is it?

Runs the tasks in series, each passing their results to the next as in https://github.com/caolan/async#waterfall

Thank you.
Hmm, what is the result of CLI tool?
It sounds like pipe: npm run a | npm run b | npm run c
But I'm not sure it's possible.

Yes it is a pipe. The same way we try to avoid doing task1 && task2 && task 3 it might be beneficial to pipe the result of one task into another. The output of the last task would be the output of the CLI.
E.g. get-json-async | jq 'json selector' | write-to-file

OK, I will challenge to add --waterfall option.

I'm sorry, I'm busy now.
I will do this by early next month, but if someone can make a PR, please don't wait for me.

I do not work on osx or win very much but both supports pipe (powershell and git bash...). Would these be equivalent?
npm-run-all -w \"get-json-async\" \"jq 'json selector'\" \"write-to-file\"
and
npm-run-all get-json-async | jq 'json selector' | write-to-file
I do not see the purpose npm-run-all has (lack of imagination?) unless we can do globs parallel:
npm-run-all -p -w  \"get-json-async\" \"jq 'json selector'\" \"write-to-file\"
in which case wouldn't interpreting the pipe be more intuitive than the flag?
npm-run-all -p get-json-async:* | jq 'json selector' | write-to-file

This has not implemented yet :sweat_smile:
I have not gotten enough time for this issue for long time...

npm-run-all -w \"get-json-async\" \"jq 'json selector'\" \"write-to-file\"
and
npm-run-all get-json-async | jq 'json selector' | write-to-file

Yes, it's the plan.
npm-run-all executes npm-scripts from right to left in --waterfall, then connects those by pipe.


Why can't persistence type be specified via the connection string?

My code relies on the automatic store creation behavior that occurs upon first accessing via a context. However, this seems to mean I have no choice about the persistence type. I actually want the re-writable type, but have no means of specifying that (iOS application).
It seemed logical to me to have an extra parameter in the connection string that allows the persistence type to be specified in case the store needs to be created, but maybe I'm missing something.

You can set the default type in the configuration from your code:
Configuration.PeristenceType = PersistenceType.Rewrite;

Alternatively the iOS configuration provider does also read system settings from NSUserDefault.StandardUserDefaults (the key will be BrightstarDB.PersistenceType).
Will either of those work for you ?

Ah, wasn't aware of that - thanks.


chore(apps): add sanity testing containers

What this PR does / why we need it:
We want to be able to run a separate suite of sanity tests against our applications being released as docker containers in our ecosystem. This is a part of the shift left automation effort of providing more tooling to quality test our releases before they hit production.
We also want to be able to write sanity tests in the format that we are already familiar with through our standard unit tests instead of the previous format in whale which were running through postman. This unifies our test paradigm into a single workflow which lessens the cognitive impact of the testing part of our workflows.
It's set up to support running tests in parallel for vertical scaling capabilities and I have written some minor reasoning for key methods in this PR through code comments. Please read those for additional details on this solution.
Which issue(s) does this PR fixes?:

Partially Resolves

https://github.com/DeFiCh/jellyfish/issues/942

Additional comments?:
Thing to note is that we are not providing any unit tests with this PR since we want to achieve final workflow for sanity testing to be run separate from the standard unit testing. To keep this PR specific to the setup of creating sanity containers I will add the initial tests once there is a strategy for splitting from the standard testing protocols in another PR.
The reason for this is because sanity testing requires us to build our application containers which increases the time, especially on certain architectures. So we make sanity testing opt in for local development and provide them as separate runners in our workflow to not bloat our regular unit tests.
This is part of the whale consolidation efforts noting the final stretch tasks that we need to finish before being 100% migrated. Remaining efforts trailing of this PR will after some internal communication be an approximate of:

Create a separate test runner for sanity testing.
Port sanity tests from whale postman to new sanity test files in jellyfish.
Move over any changes to whale that has not been ported since last update.
Add whale app, whale-api-client, and whale-api-wallet to the release workflow of jellyfish and decommission whale.

But looking at the structure, doesn't seems easy to further extend it for playground use. (for wallet side e2e use)

But looking at the structure, doesn't seems easy to further extend it for playground use. (for wallet side e2e use)

Could you elaborate on the points you think makes it hard to extend, ?
I think from a container perspective the only thing the solution does here is build the image you need and enables you to run an instance from it. Providing a base which enables tooling for the things that are repeatable between each individual requirement, then creating the specific requirements in their own classes such as this initial PR introduces through WhaleSanityContainer.
That said if we identify thing in the base that aren't shared across all our applications then we would want to move them into further abstractions. The idea is definitely that this will require some adjustments when new requirements come in that doesn't meet expectations of our other apps.
Happy to improve this with more contributions as I am sure there may be requirements in our other applications not being considered in this initial solution.

But looking at the structure, doesn't seems easy to further extend it for playground use. (for wallet side e2e use)

Could you elaborate on the points you think makes it hard to extend?
I think from a container perspective the only thing the solution does here is build the image you need and enables you to run an instance from it. Providing a base which enables tooling for the things that are repeatable between each individual requirement, then creating the specific requirements in their own classes such as this initial PR introduces through WhaleSanityContainer.
That said if we identify things in the base that aren't shared across all our applications then we would want to move them into further abstractions. The idea is definitely that this will require some adjustments when new requirements come in that doesn't meet expectations of our other apps.
Happy to improve this with more contributions as I am sure there may be requirements in our other applications not being considered in this initial solution.

Perhaps it's alright for playground, since the block minting bot is done via RPC.

Perhaps it's alright for playground, since the block minting bot is done via RPC.

Also if there are anything we need to adjust for when we start adding sanity testing for our other apps, then it should be pretty straight forward to do so. Initially as mentioned this PR currently is just setting up a strategy to build our app containers and being able to run and test against their endpoints for now, and there is definitely room for modifications as we need to expand its capabilities.
Thanks for the feedback 👍🏻

I have some minor changes as I ran into a issue with having the images being built at jest runtime. Will update description once I push the updated version.

I feel like the randomized number used in this PR should be replaced by an incremental number
3000, 3001, 3002 ... 5000
1, 2, 3 ... 100000

Not sure why runnning locally doesn't work for me on my linux machine.
Works for mac right now though.
 FAIL  apps/whale/__sanity__/WhaleSanityContainer.sanity.ts (51.611 s)
  /_actuator
    /_actuator/probes/liveness
      ✕ Status in JSON body is ok (1 ms)
    /_actuator/probes/readiness
      ✕ Status code is 503 (1 ms)

  ● /_actuator › /_actuator/probes/liveness › Status in JSON body is ok

    waitForCondition is not ready within given timeout of 30000ms.

      16 |         resolve()
      17 |       } else if (expiredAt < Date.now()) {
    > 18 |         reject(new Error(`${message} is not ready within given timeout of ${timeout}ms.`))
         |                ^
      19 |       } else {
      20 |         setTimeout(() => void checkCondition(), interval)
      21 |       }

      at checkCondition (packages/testcontainers/src/utils.ts:18:16)
          at runMicrotasks (<anonymous>)

  ● /_actuator › /_actuator/probes/readiness › Status code is 503

    waitForCondition is not ready within given timeout of 30000ms.

      16 |         resolve()
      17 |       } else if (expiredAt < Date.now()) {
    > 18 |         reject(new Error(`${message} is not ready within given timeout of ${timeout}ms.`))
         |                ^
      19 |       } else {
      20 |         setTimeout(() => void checkCondition(), interval)
      21 |       }

      at checkCondition (packages/testcontainers/src/utils.ts:18:16)
          at runMicrotasks (<anonymous>)

Test Suites: 1 failed, 1 total
Tests:       2 failed, 2 total
Snapshots:   0 total
Time:        51.701 s


ci(precommit): update

🤔 but i'm not a first-time contributor. hmm, i guess my commits have been squashed out of existence.

pre-commit run -a:
black....................................................................Failed
- hook id: black
- files were modified by this hook

reformatted copier/errors.py
All done! ✨ 🍰 ✨
1 file reformatted, 38 files left unchanged.

isort....................................................................Failed
- hook id: isort
- files were modified by this hook

Fixing /Users/carlos.meza/git/GitHub/copier/copier/errors.py

prettier.................................................................Failed
- hook id: prettier
- files were modified by this hook

CHANGELOG.md
.github/workflows/ci.yml

Codecov Report

Merging #484 (308da87) into master (600ebdb) will decrease coverage by 12.79%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           master     #484       +/-   ##
===========================================
- Coverage   95.65%   82.86%   -12.80%
===========================================
  Files          40       40
  Lines        2580     2579        -1
===========================================
- Hits         2468     2137      -331
- Misses        112      442      +330

Flag
Coverage Δ

unittests
82.86% <100.00%> (-12.80%)
:arrow_down:

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

Impacted Files
Coverage Δ

copier/errors.py
97.29% <100.00%> (+51.35%)
:arrow_up:

tests/test_complex_questions.py
17.73% <0.00%> (-82.27%)
:arrow_down:

tests/test_prompt.py
14.64% <0.00%> (-73.89%)
:arrow_down:

tests/test_templated_prompt.py
76.92% <0.00%> (-23.08%)
:arrow_down:

tests/conftest.py
69.23% <0.00%> (-23.08%)
:arrow_down:

copier/user_data.py
72.33% <0.00%> (-21.39%)
:arrow_down:

tests/test_vcs.py
84.00% <0.00%> (-16.00%)
:arrow_down:

tests/test_updatediff.py
88.09% <0.00%> (-11.91%)
:arrow_down:

copier/cli.py
85.71% <0.00%> (-10.72%)
:arrow_down:

tests/test_migrations.py
91.47% <0.00%> (-8.53%)
:arrow_down:

... and 4 more

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 600ebdb...308da87. Read the comment docs.

This has conflicts. Do you have plans on continuing with this PR?
Closing just to keep the list clean, but feel free to reopen if so. Thanks!


Remove unwanted categories and add everything under on section for now

Kindly assign me this

Also, remove these link and add a GitHub link to the repo

Also this


What should I see in ESPhome log ( Using LilyGO T-CAN485 board) on succesfull connection

Hi, I have adventured to try to use this to access my JÄSPI Tehowatti  Air heat pump ( This is 99.9% same as NIBE ). I purchased the LilyGO board and got it running in ESPhome. I get the board online and I see this in log, but heat pump still goes to error state approx 5 seconds after turning MODBUS on in heat pump. Tried also swapping A/B cabels (no effect)
Should I see some additional info on the LOG like discussion with heat pump ?

This is ( the Yamal file I run ) with only very few modifications ( sorry for some reason <> code is not rending it correctly, at least in preview)
`
esphome:
name: tehowatti-air
friendly_name: tehowatti_air
esp32:
board: esp32dev
framework:
type: arduino
Enable logging
logger:
baud_rate: 0
Enable Home Assistant API
api:
encryption:
key: "XXXXX"
ota:
password: "XXXXX"
wifi:
ssid: XXXX
password: XXXXX
fast_connect: true # Fast connect to connect to my hidden network
It is recommended to disable powersave mode on wifi, to make sure the device does not miss UDP requests sent.
power_save_mode: none
The device needs a static IP. Either do that here with the manual_ip node, or do it via another way (router)
Optional manual IP
manual_ip:
static_ip: <IP_ADDRESS>
gateway: <IP_ADDRESS>
subnet: <IP_ADDRESS>
Load nibe component
external_components:

source: github://elupus/esphome-nibe

Set pins required for LilyGo T-CAN485 board
output:

platform: gpio
id: ENABLE_PIN # Enable the chip
pin:
number: GPIO19
inverted: true
platform: gpio
id: SE_PIN # Enable autodirection
pin:
number: GPIO17
inverted: true
platform: gpio
id: ENABLE_5V_PIN # Enable 5V pin for RS485 chip
pin:
number: GPIO16
inverted: true

Configure uart that will be used
uart:
rx_pin: GPIO21
tx_pin: GPIO22
baud_rate: 9600
Configure NibeGW
nibegw:
udp:
# The target address(s) to send data to. May be a multicast address.
# When using Home Assistant: this is your Home Assistant IP.
target:
- ip: <IP_ADDRESS>
port: 9999 #The Nibe Home Assistant integration listens to 9999 by default
# List of source address to accept data from, may be empty for no filter
source:
  - <IP_ADDRESS>

# Optional port this device will listen to to receive read requests. Defaults to 9999
# read_port: 9999

# Optional port this device will listen to to receive write request. Defaults to 10000
# write_port: 10000

acknowledge:
- MODBUS40
Constant replies to certain requests cabe made
constants:
- address: MODBUS40
token: ACCESSORY
data: [
0x0A, # MODBUS version low
0x00, # MODBUS version high
0x01, # MODBUS address?
]
Some helper functions to restart ESPHome from HA
button:

platform: restart
name: Nibegw Restart
platform: safe_mode
name: Nibegw Safe Mode Boot`

Found it from the step-be step instructions


Feature: compress RGB(A) data to PNG (memory or file)

Quick reading of oxipng source indicates this should be possible via the RawImage struct but I'm not familiar enough with making python bindings/extensions in Rust to make even a PoC implementation of this.

Hi @rambo, thanks for the bug report. This has now been added in the latest v9 release. See usage instructions here: https://github.com/nfrasser/pyoxipng/blob/main/README.md#oxipngrawimage


Allow Parquet map key to be optional

What's the problem?
When HDFS Parquet files are written by flink, and there is a map type column in the schema, then its key type is optional. It will cause CH to throw exception when reading such parquet files because arrow lib forbidden optional key in map.
Like this:
$ hadoop jar parquet-tools-1.9.0.jar  schema hdfs://path/to/flink/written/parquet/file

  optional group log_extra (MAP) {
    repeated group key_value {
      optional binary key (UTF8);
      optional binary value (UTF8);
    }
  }
  optional group event_info (MAP) {
    repeated group key_value {
      optional binary key (UTF8);
      optional binary value (UTF8);
    }
  }

Refer to the map definition of flink: https://nightlies.apache.org/flink/flink-docs-release-1.16/docs/dev/table/types/#constructured-data-types
How to solve it
Remove the restriction in arrow lib.

@Avogar Can you review this pr? Thanks very much !


ChatGPTProvider close method should close httpClient too

Why are the changes needed?
ChatGPTProvider not close httpClient.
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

httpClient is reused by sessions. Closing it when closing the session is not appropriate.

@bowenliang123 is right, @Kiss736921 I apologize for my offline misleading comments.

@pan3793 Don't mind，I didn't read the code carefully. Also thanks for guide. And thanks @bowenliang123 .

It could be improved in performance and robustness with the pooling of http client, by getting client instance from when opening chat session and returning back when closing session.


Improve multilabel metrics

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

Project coverage is 100.00%. Comparing base (42c8e9c) to head (e8eada8).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #247   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           89        89
  Lines         2199      2196    -3
  Branches       200       200
=========================================
- Hits          2199      2196    -3

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


Remove execution-unit calculation from serialisers

and added print script name that can be overridden by cli arg.

Keeping the exunits will be useful for future price estimation (without needing the final built transaction), so I think we want to keep that in


Add print_extra_action utility for printing Bazel ExtraActionInfo protos [phab:D189]

Created by schroederc at 2015-04-15 21:31:18:

zarko accepted this revision at 2015-04-15 22:20:55

schroederc closed via commit bea3251536d5c5dcfb964bd960d6c5e4d58f4c72 at 2015-04-15 22:28:48


Add exit_to field for highway=motorway_junction objects

exit_to is a common key for motorway junction objects.  I figure iD should examine the other end(s) of the ramp in question (assuming the node is the start of a *_link way).

Adoption of exit_to, exit_to:left, and exit_to:right plateaued in late 2012, whereas destination and variants like destination:ref and destination:street have had much greater momentum since then and are used much more frequently:

OSRM developers have explained why exit_to is ill-suited for routing engines. Mappers in the U.S. have known of exit_to’s limitations for quite some time; there are junctions where even exit_to:left and exit_to:right aren’t enough to fully express all the branches’ destinations.
#4178 proposes adding destination fields as an alternative to the feature requested in this issue.

Thanks for the analysis @1ec5 .. looks like #4178 is the preferred way forward 👍


Azure Release Pipeline

Hi
Thanks for such awesome tool, But is it possible to use this in my Release pipeline as task?

I would also be interested in this, did you manage to find out ?

I made it work in a POC pipeline by having two tasks:
steps:
- task: DotNetCoreCLI@2
  inputs:
    command: 'custom'
    custom: 'tool'
    arguments: 'update Versionize -g'

- task: PowerShell@2
  displayName: 'Versionize'
  inputs:
    targetType: 'inline'
      script: |
        versionize --skip-dirty --skip-commit

I made it work in a POC pipeline by having two tasks:
steps:
- task: DotNetCoreCLI@2
  inputs:
    command: 'custom'
    custom: 'tool'
    arguments: 'update Versionize -g'

- task: PowerShell@2
  displayName: 'Versionize'
  inputs:
    targetType: 'inline'
      script: |
        versionize --skip-dirty --skip-commit

@nerdybynature Thanks for the snippet. I'm in a similar situation (just using AWS pipeline). Just wondering: Are you also pushing tags to master branch as shown in the documentation "git push --follow-tags origin master"
For me to achieve this, I would need to create a new SSH key every time the pipeline runs and I would have to delete the key from AWS after it's pushed the code. This sounds a bit excessive to me but I cannot figure out another way. If I don't push I cannot keep incrementing the version.
How did you handle this situation?

@volkanpaksoy
Yes, I've managed to do it the following way.
(I run a forked and modified version of the tool but that shouldn't be an issue.)
steps:
- task: DotNetCoreCLI@2
  displayName: Install Versionize Tool
  inputs:
    command: custom
    custom: tool
    arguments: 'update -g Forked.Versionize --ignore-failed-sources --add-source { my nuget feed url }'

- script: |
    git config --global user.email<EMAIL_ADDRESS>    git config --global user.name "pipeline-bot"
    versionize-forked --skip-dirty
  displayName: "Run Versionize"

The important part is the git config commands just before running the tool.
Then at the end of our pipeline I run:
steps:
- task: PowerShell@2
  displayName: 'Git push changes and version tag'
  inputs:
    targetType: 'inline'
    script: |
      $pushUrl = "$(Build.Repository.Uri)".Substring("$(Build.Repository.Uri)".IndexOf("@dev.azure.com"))
      git push https://$(System.AccessToken)$pushUrl --follow-tags HEAD:master

End result:

@nerdybynature
Thank you very much for sharing your solution. I'm going to investigate if AWS has something equivalent to System.AccessToken.

Yes, I created a new pipeline and choose GitHub on the "Where is your code?" step.
I also just tried creating a public repo with minimal code on Github, it throw the same error.
And then I tried to move the repo to Azure Devops Repo, it works fine. So seems like it is only happening on Github repo

I finally got approval to run pipelines and was able to reproduce your issue.
One workaround that I found was to change the git remote url before running versionize, e.g.:
git remote set-url origin "{your-url}.git
I noticed when pushing back to GitHub from the pipeline that I needed to add a GitHub Personal Access Token for it to work.

@nerdybynature thanks a lot for helping.
Though I face another issue, when running versionize on Azure Devops, the version does not update
tried feat: feat(core): fix: fix(core) but the version remain 1.0.0
if running locally, the version can be updated.

Do you always get the same result?
What was the version set in your .csproj file? What is the version now?
Did you have a proper versioning tag in your repo before running versionize? E.g. v0.4.2

Yes, always get the same result
The version in .csproj is 1.0.0
I added the version before running versionize

Are you running git push --follow-tags after versionize?

Yes I can actually share my task here
 - task: CmdLine@2
      displayName: Versionize
      inputs:
        script: |
          git checkout master
          dotnet tool install --global Versionize
          git config --global user.email<EMAIL_ADDRESS>          git config --global user.name "Azure DevOps"
          git remote set-url origin "https://github.com/$(OrgName)/$(RepoName).git"
          versionize --skip-dirty
          git commit --amend -m "chore(release): [skip ci]  New version release"
          git push --follow-tags https://$(GH_TOKEN)@github.com/$(OrgName)/$(RepoName).git master

I have to checkout to master as azure devops is fetching a detached branch based on the last commit.
then I have to amend the commit message to put the [skip ci] text in it otherwise it will trigger another build when verisonize push the changes, so it would dead-looped
But I believe all these dont affect because I tried quite a lot of combination, I did put the versionize --skip-dirty at the very beginning and it would return
Discovered 1 versionable projects
  * /home/vsts/work/1/s/xxxxxxxxx/xxxxxxx.csproj
√ bumping version from 1.0.0 to 1.0.0 in projects
√ updated CHANGELOG.md
√ committed changes in projects and CHANGELOG.md
√ tagged release as 1.0.0

Share my working Azure Devops task here.
 - task: CmdLine@2
      displayName: Versionize
      inputs:
        script: |
          git checkout master
          dotnet tool install --global Versionize
          git config --global user.email "$(Email)"
          git config --global user.name "$(Name)"
          git remote set-url origin "https://github.com/$(OrgName)/$(RepoName).git"
          versionize --skip-dirty
          git commit --amend -m "chore(release): [skip ci] New version release"
          git push --follow-tags https://$(GH_TOKEN)@github.com/$(OrgName)/$(RepoName).git master

@nerdybynature
My bad, I just notice the other issue related to version not updated
There need to be at least one tag already push as a base tag for it to work,
Problem solved, thanks!

Glad it got sorted out!

I'll go ahead and close this since the original question seems to have been answered (great examples).


Log filtering suggestions

One of the most useful tips we give techs when viewing logs is what to filter on in CMTrace to see pertinent information.
ie.) Filter smsts.log on entry text containing "the action" or "the group". Filter InventoryAgent.log where entry text contains "destination".
Could useful filters be added?

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

ID: 972d8899-c8a4-28c5-fabe-5ab294bac22d
Version Independent ID: 7f772e7a-836c-a18d-df8d-c3d115cb3d9f
Content: Log files for troubleshooting - Configuration Manager
Content Source: sccm/core/plan-design/hierarchy/log-files.md
Product: configuration-manager
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

Yes, thanks @PotentEngineer for the idea. I'm thinking about an entirely separate article on tools to include a section on CMTrace with all of its goodness. I'll use this issue to track that work. :)

Sounds good. I'll happily add some tricks.
-Daniel Ratliff
On Fri, Jun 15, 2018, 10:58 AM Aaron Czechowski<EMAIL_ADDRESS>wrote:

Yes, thanks @PotentEngineer https://github.com/PotentEngineer for the
idea. I'm thinking about an entirely separate article on tools to include a
section on CMTrace with all of its goodness. I'll use this issue to track
that work. :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/SCCMdocs/issues/603#issuecomment-397648696,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWnIP1k_hOslXRgSDR0RXOSqycfvDF14ks5t88uNgaJpZM4Uo_hY
.

A whole new article on CMTrace coming soon! I included your two filter suggestions. Once it's published, I welcome the community's contributions with more suggestions and tips and examples! The article is in review, will merge to our private release branch today or tomorrow. It will publish live with 1806 content soon. So I'm closing this issue.


Crash on running tests: attempt to index upvalue 'xml_etree'

I have a dead-simple Rust project with a single test file in tests/poker.rs. cargo nextest runs the tests just fine. When I run :lua require("neotest").run.run(vim.fn.expand("%")), I get:
Error executing vim.schedule lua callback: ...ck/packer/start/plenary.nvim/lua/plenary/async/async.lua:18: The coroutine failed with this message: ...pack/packer/start/neotest-rust/lua/neotest-rust/init.lua:182: attempt to index upvalue 'xml_tree' (a function value)
stack traceback:
        [C]: in function 'error'
        ...ck/packer/start/plenary.nvim/lua/plenary/async/async.lua:18: in function 'callback_or_next'
        ...ck/packer/start/plenary.nvim/lua/plenary/async/async.lua:45: in function <...ck/packer/start/plenary.nvim/lua/plenary/async/async.lua:44>

Looking at the site of the crash, I'm guessing it is caused by this recent neotest commit: https://github.com/nvim-neotest/neotest/commit/bd24d4615da20502f8d58822241be53758e82121


Request for clarification: why only one engine?

The readme states:

The VM must be initialised by creating an instance of an engine (wasm::Engine/wasm_engine_t) and is shut down by deleting it. Such an instance may only be created once per process.

I removed the block. Then spun an engine up and down, then another up. But when creating a store, it crashed. Backtraces point into v8. Looks like there is some kind of history effect.
So is this restriction a self imposed one to avoid the necessity to deal with a buggy v8, or is there some fundamental reason that no subsequent engines can be created?
Motivation: I have tests that would profit from the ability to toggle the creation of engines many times in the scope of a linux process.

It's inherent in the implementation of V8 (and presumably other engines) that they cannot be initialised twice. It should never be needed either, creating a new store gives you a fresh "instance" of the VM.

Accepted.


Employ assign_coords to address api deprecations in 0.15.1

Pull Request Checklist:

[x] This PR addresses an already opened issue (for bug fixes / features)

This PR fixes #405

[x] Tests for the changes have been added (for bug fixes / features)
[ ] Documentation has been added / updated (for bug fixes / features)
[ ] HISTORY.rst has been updated (with summary of main changes)
[ ] bumpversion (minor / major / patch) has been called on this branch
[ ] Tags have been pushed (git push --tags)

What kind of change does this PR introduce?
Unpins xarray to allow 0.15.1 and changes API usage in tests

Does this PR introduce a breaking change?
Yes? Performing operations on a coordinate now REQUIRES DataArray.assign_coords(dict( ... )), Operations like da["lon"] += 180 will now loudly fail.

Other information:
This is more of a hotfix to keep us in line with xarray. I don't think this requires a History update or a bump2version patch.

Pull Request Test Coverage Report for Build 1727

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 89.233%

Totals

Change from base Build 1726:
0.0%

Covered Lines:
2130

Relevant Lines:
2387

💛  - Coveralls


MiCloud 2h Air purifier

I’ve noticed that Air purifier 2h add my micloud account doesn’t have fan control at all :)

The Air Purifier 2H has no steeples fan control, at least in the miot protocol which is used here:
http://miot-spec.org/miot-spec-v2/instance?type=urn:miot-spec-v2:device:air-purifier:0000A007:zhimi-mc2:1

Ok, thanks :)

Im using the same Air Purifier, it seems that fan speed control of 2H model is achievable via official Xiaomi app and also by using attributes, so I think it lacks of implementation in particular model presets:
Air Purifier 2S (zhimi.airpurifier.mc1) and 2H (zhimi.airpurifier.mc2)
Power (on, off)
Preset modes (auto, silent, favorite)
Buzzer (on, off)
Child lock (on, off)
LED (on, off)
Favorite Level (0...16)
Attributes:
model
temperature
humidity
aqi
mode
filter_hours_used
filter_life_remaining
favorite_level
child_lock
led
motor_speed
average_aqi
learn_mode
extra_features
turbo_mode_supported
button_pressed
filter_rfid_product_id
filter_rfid_tag
filter_type
illuminance
buzzer

Since this plugin is using the miot protocol for communication with the device, for older devices which use the cloud for emulation of the protocol, not all functionality will be available. I suspect that the official xiaomi app uses the old miio protocol to communicate with the device hence it is possible there.
As an example those particular devices here are simply missing the fan control in the miot spec hence it is not possible.


OSX client cannot connect on fresh install

Appears to be an issue with SSL (which is default) for connecting to localhost server:
Trying to start a new server...
working directory: /Applications/veles.app/Contents/Resources/veles-server
python script name: srv.py
python interpreter executable: /Applications/veles.app/Contents/MacOS/../Resources/veles-server/venv/bin/python3
arguments:
srv.py
--cert-dir
/Users/user/Library/Application Support/Codisec/Veles
veles+ssl://@<IP_ADDRESS>:3135
/Users/user/Library/Application Support/Codisec/Veles/veles.vdb
Waiting for a new server to start...
Process of locally created server started.
INFO:root:Świtezianka server is starting up...
INFO:root:Opening database...
INFO:root:Loading plugins...
INFO:root:Starting SSL server...
NetworkClient::connect
client interface: <IP_ADDRESS>
server host: <IP_ADDRESS>
server port: 3135
NetworkClient: bind successful.
NetworkClient: New connection status: Connecting.
INFO:veles.server.proto:Client url: VELES+SSL://:476C9D1E89AD56029E382904F33CAA72C8A4FC7F3F9CF53228618D5B892B0F26@<IP_ADDRESS>:3135
INFO:root:Ready.
NetworkClient: unexpected error: The root CA certificate is not trusted for this purpose
NetworkClient: New connection status: Not Connected.
NetworkClient: Socket error - The host name did not match any of the valid hosts for this certificate
NetworkClient: TCP socket disconnected.
Disabling SSL in the Connect menu, and reconnecting twice seems to work.

Note: This seems to happen only on macOS-es.
I managed to reproduce the problem and I'm looking into it now.


vuex state not reading the "state" property of node?

i'm passing a state object to the tree via vuex(with a specific node selected), but it doesn't respect that i'm passing it in as selected?

Please give me more details or example.

i'm trying to auto select the first node in the tree when binding via vuex.  so i'm setting the state variable selected to true, but the tree ignores it when binding the object?


what is the migration_lock ??

what is the migration_lock ?? why we have this in the database

Nice!

migration_lock is a table that can be used by third party dialects to lock the migration table to prevent concurrent processes running migrations from interfering with each other. Not all database engines have global, or table locks. The migration_lock table has a single row that can be used as a lock if needed.


Add sushi

Adds in sushiswap pools pulled from the Graph (which sushiswaps own analytics page uses behind the scenes. https://analytics.sushi.com/pairs). We can't get swaps that come from pools not in dex_liquidity_pools, BUT dex_liquidity_pools can't pick up pools we're missing the original creation tx for.
This all boils down to we are missing swaps from any pools created before February (as far as events_emitted data goes back too). This pulls pools from theGraph to augment our own numbers -- we still don't get the creation tx but we get the important info we need to parse swaps (if we do have the creation tx we use our data).
Also this increases the incremental refresh lookback to 7 days from 2 in dex swaps, which will remove some null USD values.

please remove commented code

approved!


Slow startup on new version

This issue tracker is only for technical issues related to bitcoin-core.
General bitcoin questions and/or support requests and are best directed to the Bitcoin StackExchange.
For reporting security issues, please read instructions at https://bitcoincore.org/en/contact/.
Describe the issue
New version takes too much time to start , here is the logs
2017-12-13 03:48:26 Using obfuscation key for C:\d\data\blocks\index:<PHONE_NUMBER>000000
2017-12-13 03:50:07 Compacting 1@0 + 8@1 files
another example:
2017-12-14 17:17:30 Using obfuscation key for C:\d\data\blocks\index:<PHONE_NUMBER>000000
2017-12-14 17:19:13 Compacting 1@0 + 8@1 files
Can you reliably reproduce the issue?
Yes
If so, please list the steps to reproduce below:
1.close the core and run it again
Expected behaviour
Slow start up
Actual behaviour
it use to take less than 10 s to start now more than 3 min
Screenshots.
If the issue is related to the GUI, screenshots can be added to this issue via drag & drop.
What version of bitcoin-core are you using?
List the version number/commit ID, and if it is an official binary, self compiled or a distribution package such as PPA.
Machine specs:

OS: Windows 10
CPU: Core i5
RAM:8GB
Disk size:500GB
Disk Type (HD/SDD): HD

Any extra information that might be useful in the debugging process.
This is normally the contents of a debug.log or config.log file. Raw text or a link to a pastebin type site are preferred.

This is confirmed, though the reason for the slowdown is as of yet unclear.

The slowdown is caused by the full proof-of-work verification on startup. This was actually disabled in 0.11 (probably because of the same performance reasons). But it's important to check the chain of work on startup. So we'll have to improve the performance of those checks, in the meanwhile i created a command-line switch to skip the verification if you're in a hurry.

Update: this new version doesn't seem to have the SSE2 optimized Scrypt routines enabled. Fixing that. Takes about 30 seconds (25%) off the startup time on a full verification. But it's still too slow. Looking at other avenues to pursue, stay tuned.

Update: changed the default behavior to rely on the checkpoints, and do PoW verification only after the last known checkpoint. This reduces the startup time by roughly 90%. It's still possible to do full verification if desired.


Sample average approximation in perturbed model

It would be nice to be able to fix the random samples once and for all.
Once solution would be to store the RNG within the Perturbed object: see https://docs.julialang.org/en/v1/stdlib/Random/

Done


KAFKA-13153: Disallow KRaft broker registration if the node.id is already in use by a controller

Kraft brokers were previously able to register with the same node.id as a controller without failing startup but they would not unfence themselves because they never catch up to the last committed metadata offset. This PR explicitly disallows controllers and brokers from sharing node.ids and it also changes the node.id in the default config file for the Kraft broker from node.id=1 to node.id=2.
https://issues.apache.org/jira/browse/KAFKA-13153

This renders colocated KRaft useless.


 Say I have an input field with a required attribute I would expect that form.FormController.$error is {"required":false}, but it is just {}.
Because of this I can't use my custom validation handler inside ngRepeat.

This works in 1.3.16 / 1.4.0. If the error ist set, in both cases the whole ngModelCtrl is available in the error array.


fqdn: remove unused fields in type Config

These are unused after commit ec972c7e6bc5 ("daemon, fqdn: remove DNS
poller implementation").
Follow-up for #13229

test-me-please

@aanm FYI, I've pushed another commit with a cleanup of (*NameManager).GetDNSNames after you reviewed.

test-me-please


MINOR Replace use of deprecated getFixtureFactory() with FixtureTestState

I've left a couple of places that use getFixtureFactory() in methods that are also deprecated themselves

Bump @tractorcow @dhensby - would be cool to get action points from here

I think it's fine as is

All good @tractorcow?


First step in getting packer to work again.

Issues resolved:

Fix for #1399 "unknown filesystem type 'vboxsf'.
Cause: You were missing the (proper version of) the guest additions in the box.
You need to install a plugin to install/upgrade these at .vagrant up' time.
vagrant plugin install vagrant-vbguest
packer/scripts/vbox.sh now mounts  the version of VBoxGuestAdditions that corresponds to your version of VirtualBox.
Hardcoded version removed.
Finally the guest can mount folders using this in the Vagrantfile:
config.vm.synced_folder ".", "/vagrant"

Fix for #1891 "Update Vagrant box"  Now 1611 Centos 7 iso

Verify checksum against
"27bd866242ee058b7a5754e83d8ee8403e216b93d130d800852a96f41c34d86a"
Improvements

packer/kickstarts/vagrant.cfg creates a separate sudoers file for vagrant
packer/vagrant.json l77-82 adds option to use a cached iso on OSX in /Users/Shared
packer/kickstarts/vagrant.cfg adds info in /etc/passwd
packer/scripts/vagrant.sh one line less.

The ansible provisioner is untouched in this PR.

FYI: This does not completely fix #1891 because we have to upload the updated vagrant box to Atlas.

You need to push it with your token/license, I have no enterprise version...
demo:mantl bas$ packer push --name dockpack/mantl packer/vagrant.json
Error starting upload: upload: This feature requires Vagrant Enterprise or Terraform Enterprise. Please contact<EMAIL_ADDRESS>to start or extend your trial.

Thanks @bbaassssiiee I was simply pointing it out so that the issue doesn't get closed out when this is merged.

Travis build was already failing for a while.

My gut says the Travis failures are due to the terraform upgrades that happened separately.


Vim9: unexpected extra error message when executing ":echoerr" from mapping

Describe the bug
In Vim9 script, executing :echoerr with :exe from a mapping or custom Ex command might print an extra unexpected error message.
To Reproduce
Run this shell command:
vim -Nu NONE -S <(cat <<'EOF'
    vim9script
    nno <F3> <cmd>exe Func()<cr>
    def g:Func(): string
        try
            return 'echoerr "some message"'
        catch
        endtry
        return ''
    enddef
    feedkeys("\<F3>")
EOF
)

These 2 lines are printed (which causes a hit-enter prompt):
Error detected while processing :
some message

Expected behavior
Only this line is printed (and no hit-enter prompt):
some message

Environment

Vim version: 8.2 Included patches: 1-2533
OS: Ubuntu 16.04.7 LTS
Terminal: xterm(366)

Additional context
If Func() is rewritten as a legacy function, the exact same code only prints 1 line:
vim9script
nno <F3> <cmd>exe Func()<cr>
fu g:Func()
    try
        return 'echoerr "some message"'
    catch
    endtry
    return ''
endfu
feedkeys("\<F3>")

some message

Personally, I don't care whether it's considered as a bug and fixed or not.  I think executing :echoerr is an ugly hack, which can have other unexpected side-effects.  Still, in legacy Vim script, some plugin authors use this technique when they implement a custom Ex command or mapping, and they don't want a multiline stacktrace to be printed in case of an error.
  The second snippet does not.  See here for a real example.
If they try to refactor their plugins in Vim9 script, these plugin authors might find the new behavior unexpected.

I forgot to mention that – for some reason – the try/catch is necessary to reproduce the issue, which seems confusing and inconsistent:
vim9script
nno <F3> <cmd>exe Func()<cr>
def g:Func(): string
    return 'echoerr "some message"'
enddef
feedkeys("\<F3>")

some message

vim9script
nno <F3> <cmd>exe Func()<cr>
def g:Func(): string
    try
        return 'echoerr "some message"'
    catch
    endtry
    return ''
enddef
feedkeys("\<F3>")

Error detected while processing :
some message


Feature/readme fix

What?
Fix gif image sizes on readme so that all are visible without scrollbar
Why?
Visibility/ readability
How?
Adjust width of images on readme

Thanks @AsadJeewa 👍


General: allow users to make "Public analyses"

Related to this phase 1 ticket: https://github.com/VEuPathDB/web-eda/issues/392
Discussed in 9/18 ClinEpi UX meeting:
Front end needs UI development to support users making their strategies public. We won’t have this in place for Phase 1.

We need to guide users towards how to make their strategy public
We need to provide a way for users to fill out the study description

Perhaps users could fill out the study description (needed for making an analysis public) within a notes tab (see https://github.com/VEuPathDB/EdaClinepiPhase2NewIssues/issues/15)
UI for making public analyses could guide them to filling out a designated section within the notes tab

this issue is basically a duplicate of https://github.com/VEuPathDB/web-eda/issues/620


Why is gutter dependent on fluid setting?

I want to use a gutter in the normal grid setting (specified width), but I see in the code that fluid is required to use a gutter. I wonder why that is?

Mmh... Not sure... I followed flexboxgrid.css. I need to take a look but I don't have enough time now ;) Feel free to send a PR

If someone is here looking for a workaround, you can try something like this: https://github.com/dbmedialab/shiny/blob/master/src/atoms/Grid.js

I seems that this issue (outerMargins only being applied to fluid grids) is affecting many users.
@LoicMahieu Will you consider merging #87 to fix this issue?


system_modes: 0.9.0-3 in 'galactic/distribution.yaml' [bloom]

Increasing version of package(s) in repository system_modes to 0.9.0-3:

upstream repository: https://github.com/micro-ROS/system_modes.git
release repository: https://github.com/ros2-gbp/system_modes-release.git
distro file: galactic/distribution.yaml
bloom version: 0.11.1
previous version for package: 0.9.0-1

launch_system_modes
* More flexibility in specifying the default mode, any mode can be now default mode
  https://github.com/micro-ROS/system_modes/issues/69

system_modes
* More flexibility in specifying the default mode, any mode can be now default mode
  https://github.com/micro-ROS/system_modes/issues/69

system_modes_examples
* More flexibility in specifying the default mode, any mode can be now default mode
  https://github.com/micro-ROS/system_modes/issues/69

system_modes_msgs
* More flexibility in specifying the default mode, any mode can be now default mode
  https://github.com/micro-ROS/system_modes/issues/69

Holding for Galactic Sync


[Documentation / FAQ] Add "can toybox be compiled in a static manner, like busybox", and "is ncurses required"

You guys have a FAQ already, but most of the entries link to a video. I can not watch a whole
video. I would prefer short statements as answers. (Both a video AND the answer may be the
best solution).
I came specifically here right now because I had problems with busybox. I can not compile it
with ncurses; I can compile htop and other applications that depend on ncurses fine, so this
is a flaw in busybox's build system. Unfortunately the last change to busybox appears to
have been +1 year ago so the project may be dead. Hopefully toybox can replace that use
case I have for busybox.
Why do I use busybox?
I compile it via static option from the make menuconfig menu. I need it in case I break some
shared library on my custom linux system. Hopefully toybox can replace busyboxy here.
Anyway. For this issue request I would like to suggest two new entries into the FAQ:
(1) can toybox be compiled in a static manner, like busybox
(2) is ncurses required for the above ^^^

Hopefully this could be added to the FAQ. Perhaps the FAQ can be a separate .md document
rather than be put into the main README here, but this is entirely up to you of course.
Thank you for reading this issue request.

The last commit to https://git.busybox.net/busybox/log/ was 8 weeks ago. I suspect Alpine Linux and Buildroot and so on would notice if it was dead?
How do "most of the entries" link to a video? There are 17 questions in the FAQ and only three links to videos from that page: one to my 2013 talk on why toybox exists (also in the nav bar on the left), one to a talk from an ex-debiain maintainer about why time based releases are a good thing (me citing my sources for where I got the idea, it was from that talk), and one to a 38 second clip of the 1980 hitchhiker's guide to the galaxy BBC television miniseries about vogon poetry (citing where I got the phrase "in brief: avoid").
The relevant FAQ entry for your question seems to be https://landley.net/toybox/faq.html#cross which doesn't link to a video. There's more about static linking in the next FAQ entry https://landley.net/toybox/faq.html#targets and I found those by doing a ctrl-f search for "static" in the page.

I came specifically here right now because I had problems with busybox. I can not compile it with ncurses; I can compile htop and other applications that depend on ncurses fine, so this is a flaw in busybox's build system. Unfortunately the last change to busybox appears to have been +1 year ago so the project may be dead. Hopefully toybox can replace that use case I have for busybox.

i am statically building both toybox and busybox using a musl-cross toolchain from

either: https://skarnet.org/toolchains/
or: https://musl.cc/

i just looked at my build scripts and up to busybox 1.36.1, ncurses is not required – at least not for my feature enabled.
depending on the feature enabled in toybox you might require building and installing libressl and libz into the toolchain first.
you might want to know that gnu coreutils can now also be build single-binary and statically linked with musl-cross toolchain if that satisfies your use-case.


Improve Ownership Ergonomics of PromqlResult and Related Types

Summary
The existing library API only provides immutable references to the internal data of the Promql query result. This may be good for encapsulation but it becomes very limiting when ownership of the data is required. In the current implementation, owning the data requires cloning it, which can be very expensive if the data is large.
This PR attempts to mitigate that by allowing the user of the library to own the internal types by explicitly calling the relevant into_* methods.
Changes

The custom as_variant and is_variant methods on the Data type have been removed. Instead, the EnumAsInner derive macro is used to generate the same methods automatically. Additionally this also adds the into_variant methods which allow user to own the internal types.
PromqlResult, InstantVector, and RangeVector implement into_inner method
Sample now implements Copy

Thank you for the PR. I will merge it and probably cut a new release by the end of the week. Right now I am a little busy with the day job.

Thank you for the PR. I will merge it and probably cut a new release by the end of the week. Right now I am a little busy with the day job.

Great! Let me know if I need to make any further changes to the PR.

I merged your PR and released a new version that contains your changes.
Thanks again!


update ChatRoom.js to ensure empty messages don't get added to the chat

TASK 530 (ADO) - Ensure empty messages don't get added to the chat room
Description

Empty messages, including trimmed leading and trailing spaces, should not be output to the chat
Fixed an issue with overflow on the chat messages making them not viewable when the UI is not stacked
Fixed aria-label attribute for screen reader use

What to test for/How to test

Attempt to add an empty message, or a series of spaces -> nothing should be output to the char


Expand StyleDefinitions to include animations and attack speeds

Check if all ItemDefinition.weaponStyle()'s are correct compared to manual checks in player.combat.melee.weapon
Check if the combat_style info in StyleDefinitions is actually the same as used in the animation? - No style 12 "fun" has mouse_toy and rubber_chicken which have different attack animations
Move all melee weapon animations and attack_delay into a yaml file
Animations should allow one for all
Attack speeds (should be same as animations as they can vary per attackType?)
Remove majority of files in player.combat.melee.weapon
Check as many animations as possible on osrs/rs3

Attack speeds don't belong here as they can vary depending on type. E.g. battleaxes are 6 where axes/hatchets are 5 but they both have the same style


The problem about data flow graph?

Hi everyone:
I am a beginner for tensorflow, and do not understand something about the demo in tutorial files, like following:

During testing, how can accuracy call the trained model for mnist.test.images and mnist.test.labels.
Does the trained model flow to the accuracy?
Can anyone help me? Thanks a lot!

this question is more suitable for stackoverflow.

@JohnnyY8 accuracy is just a node of the graph, a bfs can traversal the whole graph.

@suiyuan2009 Thank you.


Include updates

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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 26.637%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
594

Relevant Lines:
2230

💛  - Coveralls


Support Solexa qualities through HTSJDK

We can use SolexaQualityConverter.
Probably implement as a ReadTransformer after #36.

Only support for the new IO (#36). Closed by 268a97167a6cac60c6a9516039291aff163775bc


Cluster already exists?

Hi:
I need some help to run kafka-manager success,Thanks...
Kafka-manager Version : <IP_ADDRESS>/14
(1) After i added a new cluster,the list of kafka-manager doesn't show the new cluster  witch i made before,until i restart kafka-manager.
(2) An exception came out from kafka-manager like : "Yikes! Ask timed out on [ActorSelection[Anchor(akka://kafka-manager-system/), Path(/user/kafka-manager)]] after [5000 ms]", when i check Cluster Topics/test2,but the other one***(Topics/test1)*** is right.
(3)

second question could be solved by : #143

The consumer polling has been disabled by default, it was too aggressive and didn't work right for large clusters.  Please try <IP_ADDRESS>.  There is a hard java 8 requirement now.


Apply label template transforms to prefix, suffix and note

We've got this cool new label template system which lets the user create templated macro names like "{integration_time_ms}ms-{gain_db}dB" which are rendered at the time each Measurement is saved, providing customized graph legend, "label" metadata and thumbnail title.
We might as well drop the other shoe and apply the same transforms to prefix, suffix and note fields. I would find this useful myself.

https://github.com/WasatchPhotonics/ENLIGHTEN/pull/67


[backport] Make caffe model loading faster (~2.4 times on my benchmark)

Backport of #3523

jenkins, test this please

jenkins, test this please

jenkins, test this please

LGTM!


baltimore email template

email<EMAIL_ADDRESS>template:
[Dear Eric T. Costello,
My name is (NAME) and I am a Baltimore resident. In the midst of this pandemic and public outcry against police brutality, it feels more inappropriate than ever to propose increases to the BPD budget from $530 Million to $545 million. I urge you to ethically reallocate the Baltimore City Expense Budget, divesting interest in the BPD, and investing social services and education programs, effective at the beginning of FY 2021. Investment in programs such as the Affordable Housing Trust Fund, Baltimore Children and Youth Fund, Safe Streets Baltimore, the Office of Employment and Development, or the Department of Health, shows our commitment to communities and the vision that all Baltimore residents deserve to thrive. Historically, the city government has spent far more on police than on public health, homeless services, youth services, and other vital agencies. It’s time to defund the BPD’s harmful expansion into homeless services, schools, youth services, mental health, and other social services where police don’t belong. It’s time to protect investments in human services, the social safety net, and racial and economic justice. I am writing to insist that the upcoming BBMR budget hearings for FY 2021 reflect the voices and needs of Baltimore’s citizens. I am asking that city officials lobby intense care, attention and effort towards finding sustainable, longterm change.
Thank you, (Name) June 4, 2020]

on it! Do you mind if we also add in the city council as recipients?

no not at all here is a page with all their contact.
http://www.baltimorecitycouncil.com/council-members
also important to not i did not make this template, anna krooks (@annay2k)
made it.
Thank you for all the work you are doing.
Patrick
On Fri, Jun 5, 2020 at 2:42 PM emilyhuntsman<EMAIL_ADDRESS>wrote:

on it! Do you mind if we also add in the city council as recipients?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/teddywilson/defund12.org/issues/273#issuecomment-639698735,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AP3JB2EPUS3KY46H3Q3RZ2DRVE4ALANCNFSM4NUY3NDA
.

I will submit this for approval

This is written for State Senators and Delegates of the MD State Legislature -- so people could use the link I gave above to figure out who their state senator and delegates are for their particular district -- or could just do all of them together. Here is the list of them all together, thanks!
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>


getTimestamp and getTime don't use info about CH server's time zone.

Hello.
While working with dates I faced with a TimeZones problem.
More specifically, clickhouse doesn't use timezone in dateTime representation, ok. But when jdbc driver converts a dateTime string with the SimpleDateFormat here it uses timezone of the host, where jdbc is running but not the clickhouse server!
So, it was not clear to figure out the bug in our system when In our db data stored in UTC, but clients work in, let's say CST. And this is the place where UTC data was shifted to CST that led to a terrible mess.
I think, It would be better to set timezone in jdbc as a property and do this at ClickHouseResultSet initialization time: (That actually I do now).
sdf.setTimeZone(TimeZone.getTimeZone("UTC")); // or property value

But also I believe that there is a way to get proper timezone of the clickhouse server and use it, instead of local host timezone.
Thanks.

Hello, thanks for report.
I think the solution must be like this:

if use_server_timezone=true, then on connection init query select timezone(), if fails - throw exception.
if use_timezone is not empty, use timezone provided in this property
if both - throw exception on connection init.

Note: native client uses exactly this logic, based on the use_client_time_zone setting (it is false by default).

Merged to master. Will be in next release using server timezone by default.
Please note that this will work only with recent versions of ClickHouse since the function timezone() was added in the end of January. For earlier versions the properties must be overridden to use explicit timezone.
This also will be described in release notes.


Requesting Espanso

Describe the package
Espanso is a text expansion tool that has been in my workflow for a while. Given the quality of life improvements already available on Universal Blue, this seems like a great addition. Their flatpak addition also seems to have stalled for now.
Image
All Images

I'd love to try this but ideally we'd have a package for this. Maybe we can toss this in a COPR or something. (Appimage isn't an option I'm willing to support)

There's a COPR now, if it gets put into Fedora then it'll be real easy: https://discussion.fedoraproject.org/t/espanso-copr-available-for-testing/88921

Oh wow! That was quicker than I thought, I didn't know this could happen on such short turn around times!

Update:
I have installed the COPR as suggested on Discord in the following manner,

Downloaded the repo file from https://copr.fedorainfracloud.org/coprs/eclipseo/espanso/
Added it to /etc/yum.repos.d
Installed it as rpm-ostree install espanso-wayland.
Now I am able to follow the guide to enable espanso-wayland as a systemd service and it launches.

However, I still have the following issues,

I am unable to use setcap as indicated,
sudo setcap "cap_dac_override+p" $(which espanso-wayland) I get the error Failed to set capabilities on file /usr/bin/espanso-wayland' (Read-only file system)
A window/process that I am unable to dismiss is created. If I kill it with ps -ef | grep 'espanso-wayland' and then kill, then it doesn't run at all. Here is a video for it.
Screencast from 2023-09-11 22-54-38.webm

Any tips would be really helpful!

Just checking in to see if any of you have tried this!

@castrojo Can you let me know what help is required? I'd be happy to learn and help if I can.

Someone needs to PR in the copr and enable the package and then probably fix the issues you ran into.

Please see https://github.com/ublue-os/bazzite/commit/ed975d1601e4f0c0305efe5da8ad3049549d317d
For a method of setting capabilities for binaries.

@m2Giles  Is this the specific line that you refer to ExecStartPre=/usr/bin/mount --bind /usr/local/bin/.sunshine /usr/bin/sunshine?

Please read through the following to understand what is going on.
https://universal-blue.discourse.group/t/selinux-workarounds-for-binaries-with-the-wrong-label/342?u=m2giles
Instead of SELinux issues, your binary doesn't a capability it needs to function. So you can use the following ExecStart=/usr/sbin/setcap  cap_dac_override+p /usr/bin/espanso-wayland)
If espanso-wayland is a symlink you will need to modify it for following the symlink instead.

Sigh, copied the wrong line, I was referring to ExecStart=/usr/sbin/setcap cap_sys_admin+p /usr/bin/sunshine instead of what I had put in.
Thank you for the details, I'll check the links and report back to see if this works.

Do you guys feel like this should be added by default? I suppose that if it isnt added by default you'd need to layer it (a problem for bootc adoption). Implementing this should be too hard but it really depends on it being a default or not

Are we still interested in this? Espanso is packaged in Terra's repo with the SELinux fixes and it works flawlessly.

We're in the process of trimming down our third party repos so not looking to add another.
However @tulilirockz what do you think about tossing this into ublue-os/staging so we can play with it? I think it's worth a shot, there's killer features in there that I think are worth investigating!


Added typehints to iterator functions

To avoid notices in PHP 8.1+.

This PR fixes PHP 8.1 compatibility all right, but it breaks compatibility with PHP 7.4 because the mixed type is not available there. It's also a BC break because code that overrides those methods likely won't have native return types already.
The better solution would be to add the ReturnTypeWillChange attribute instead.

Superseded by #48


feat: adds phone auth via gotrue-js 1.17.0

:tada: This PR is included in version 1.21.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add cloudflare_api_shield_operation resource to cloudflare-go

This change adds support for the following API Shield related endpoints related to endpoint management:

Add operations to a zone
Delete an operation
Retrieve information about an operation

Description
This change adds support for the following API Shield related endpoints related to endpoint management to cloudflare-go. This is so they can be used from the library and will enable this feature to be added to terraform in the future.
Has your change been tested?

Unit tests
Local testing using API

Types of changes
What sort of change does your code introduce/modify?

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] This change is using publicly documented in cloudflare/api-schemas
and relies on stable APIs.

Codecov Report

Merging #1397 (bc05376) into master (b9ac804) will increase coverage by 0.23%.
Report is 265 commits behind head on master.
The diff coverage is 52.38%.

@@            Coverage Diff             @@
##           master    #1397      +/-   ##
==========================================
+ Coverage   48.33%   48.57%   +0.23%
==========================================
  Files         133      140       +7
  Lines       13023    13898     +875
==========================================
+ Hits         6295     6751     +456
- Misses       5201     5482     +281
- Partials     1527     1665     +138

Files Changed
Coverage Δ

access_audit_log.go
79.31% <ø> (ø)

access_bookmark.go
72.44% <ø> (ø)

access_keys.go
71.42% <ø> (ø)

access_organization.go
53.84% <ø> (ø)

access_service_tokens.go
51.85% <ø> (ø)

account_members.go
65.54% <ø> (ø)

account_roles.go
53.84% <ø> (ø)

accounts.go
50.81% <ø> (ø)

addressing_address_map.go
39.04% <ø> (ø)

addressing_ip_prefix.go
45.45% <ø> (ø)

... and 122 more

... and 1 file with indirect coverage changes

solid first pass -- only some conventions/consistency based updates here to get it inline with the existing library.
thanks!

@jacobbednarz have resolved the comments, fixes are in this commit https://github.com/cloudflare/cloudflare-go/pull/1397/commits/583a0d227aeb5d06bbfbb9d9df4aedf0eb887219

thanks @djhworld 👏 you rock.