MarkDB does not recognize YAML citekey

My naming rule is .+\.md$ ,and to put the citekey in the yaml area. But when the file name does not contain @citekey, it cannot match correctly. I tested it many times and did not achieve it. So can this plugin rely only on the citekey configuration in the yaml area? I don’t know where the problem is.

MarkDBConnect-debug.txt

@NaWaErBaoDian 纳瓦尔宝典.md
@daeh

you have a newline before the first ---. Markdown metadata needs to begin on the first line of the file.
See https://help.obsidian.md/Editing+and+formatting/Metadata for config requirements

You can add metadata to your notes by adding a block on the first line of your note. The block must start and end with three hyphens (---).


Update CONTRIBUTE.md

In the twitter thread, there were some comments like, "wow, I made the list!". I lightly modified this document to hopefully make individuals more comfortable adding themselves, and in seeking additional help if they need it.

thank you so much!


HDDS-5359. Incorrect BLOCKCOUNT and BYTESUSED in container DB

What changes were proposed in this pull request?
Negative BlockCount and UsedBytes has been observed in ContainerDB.
The BlockCount is incremented only when the Stream is closed and not when the BlockID is added to the DB. If the OutputStream was not closed properly or if, for any reason, the client starts writing to a new pipeline before the full block is written, it could lead to a Block being present in the container but the key_count (BlockCount) not being incremented for it. When a block is deleted from a container, the blockCount is also decremented. But if the blockCount is wrong to start with, it could lead to a negative value.
When a block is deleted, usedBytes is decrement in memory first after deleting a chunk. And even if the chunkFile does not exist (already deleted), the usedBytes is decremented. This could lead to usedBytes being decremented multiple times for the same chunk and causing the total usedBytes metadata in the DB to become negative. Once all the chunks in all the blocks in that iteration of BlockDeletingService task are deleted, only then is the usedBytes updated in containerDB by taking the in-memory value. This Jira proposes to first update the DB with correct usedBytes (calculated from the BlockInfo after all chunks are deleted) and then update the in-memory metadata. This is the update sequence logic followed for all other state updates.
Also, when a chunk is overwritten, then it is assumed that the size of the chunk remains the same. But it’s possible to overwrite more data into the chunk than originally present. In this case, the used_bytes should be updated with difference in the chunkSizes. (Adding this as a TODO).
This PR has the following fixes:

Change Container DB KeyCount to BlockCount (to avoid confusion on what the keyCount denotes in ContainerData)
Fix BlockCount update logic
Fix UsedBytes decrement logic - update container DB first and then in-memory
Separate ContainerData metrics like read/write counts and bytes to different class
Cleanup and deprecate old Block and Chunk Delete methods
Add a test to verify blockCount and usedBytes are updated correctly on write failures

What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-5359
How was this patch tested?
Added a unit test

Thanks @adoroszlai for reviewing the patch. I addressed some of your comments.
I am looking into the test failure.

Thanks @nandakumar131 for the offline discussion.
As you suggested, I am initializing KeyValueContainer#PendingPutBlockCache only if the containerState is OPEN or CLOSING. Please take a look.
There is no possibility that a container can go back to open state from any of the other states, right? To be on the safer side, we can add a null check before adding/ removing from PendingPutBlockCache. Let me know what you think. Thanks.

Thanks @nandakumar131 for the offline discussion. I updated the patch to remove the null check as discussed.


net: sendfile needs -lsendfile for external linker on Solaris

With Go 1.5.0 on SunOS/amd64 (namely SmartOS), packages employing the external linker and net/* packages (e.g. CouchBase or github.com/mongodb/mongo-tools) will fail due to an undefined 'sendfile' symbol.
The following patch (from pkgsrc's package for go-1.5.0) works around the problem:
https://github.com/jsonn/pkgsrc/blob/37075a88350da1870518cdd61bd6609bbf1c16c5/lang/go/patches/patch-src_net_sendfile__solaris.go
Steps to repeat:
git clone https://github.com/mongodb/mongo-tools
cd mongo-tools
. ./set_gopath.sh
mkdir bin
go build -o bin/mongoimport -tags sasl mongoimport/main/mongoimport.go

Output:
# command-line-arguments
/opt/local/go/pkg/tool/solaris_amd64/link: running gcc failed: exit status 1
Undefined                       first referenced
 symbol                             in file
sendfile                            /tmp/go-link-666650609/go.o
ld: fatal: symbol referencing errors. No output written to $WORK/command-line-arguments/_obj/exe/a.out
collect2: error: ld returned 1 exit status

I'm wondering if cmd/link should automatically add -lxxx
given "cgo_import_dynamic libxxx.so"?
/cc @ianlancetaylor

I don't understand why we need -lsendfile, but not, say, -lsocket.

-lsocket is in net/cgo_solaris.go, I wonder if we should add -lsendfile
there.

Sounds better.

@minux cgo_import_dynamic is a directive for internal linking mode.  I'm not sure it makes sense for it to affect how the external linker is used.  Passing flags to the external linker seems more a job for cgo LDFLAGS or //go:cgo_ldflag.

Thanks, guys, confirming the problem to be fixed.

For the record, libsocket, libnsl, and libsendfile may be filter libraries in a future release of Solaris -- typically such libraries are merged into libc.  So this change won't cause any problems, as the filter libraries will provide the necessary symbol compatibility, but is unnecessary for future releases:
https://blogs.oracle.com/rie/entry/shared_object_filters
http://docs.oracle.com/cd/E36784_01/html/E36857/chapter4-4.html


[x264:x64-windows] build failure

Host Environment

OS: Windows 10 v1903
Compiler: Visual Studio 2017

To Reproduce
Steps to reproduce the behavior:
./vcpkg install x264:x64-windows
It could not cofigure at first, and I find the cause in vcpkg_configure_make.cmake (line 223):
string(REPLACE ";$ENV{SystemRoot}\\System32;" ";${MSYS_ROOT}/usr/share/automake-1.16;${MSYS_ROOT}/usr/bin;$ENV{SystemRoot}\\System32;" NEWPATH "$ENV{PATH}")
This intends to add some paths, however $ENV{PATH} of my system only contains C:\Windows\system32, not C:\Windows\System32, so it fails.
After I modify this, it configures and builds well, but fails again when installing.
install-x64-windows-dbg-err.log
install-x64-windows-dbg-out.log
It seems to be config errors, I have no idea how to fix it after trying some ways, so I come here to seek some help.

By the way, environment variables in system setting contains exactly C:\Windows\System32, not C:\Windows\system32.

There seems to be a lot of issues building this port (x264). I wonder what's going on!
Just downloaded master branch and no issues at all.

@abcping123 Let us know if we can be of any assistance.

@Neumann-A
Could you please help take a look?
It seems that there are still some problems when building x264 after PR #11836 merged.
config-x86-wiindows-dbg-out.log
Unknown option --build=x86_64-pc-mingw32, ignored
Unknown option --disable-silent-rules, ignored
Unknown option --verbose, ignored
Unknown option --disable-static, ignored
Unknown system , edit the configure

config-x86-wiindows-dbg-err.log
./../src/14d026c3bd-bca2ebf740/configure: line 327: rm: command not found
./../src/14d026c3bd-bca2ebf740/configure: line 328: rm: command not found
./../src/14d026c3bd-bca2ebf740/configure: line 344: dirname: command not found
./../src/14d026c3bd-bca2ebf740/configure: line 341: dirname: command not found
./../src/14d026c3bd-bca2ebf740/configure: line 345: grep: command not found
./../src/14d026c3bd-bca2ebf740/configure: line 554: /config.sub: No such file or directory
./../src/14d026c3bd-bca2ebf740/configure: line 565: basename: command not found
./../src/14d026c3bd-bca2ebf740/configure: line 148: rm: command not found
./../src/14d026c3bd-bca2ebf740/configure: line 167: cat: command not found
./../src/14d026c3bd-bca2ebf740/configure: line 171: cat: command not found
./../src/14d026c3bd-bca2ebf740/configure: line 1: rm: command not found

I think it's time for us to switch to ShiftMedia

I met the same questions now. Is there a stable commit of vcpkg which can be used now?

@longnguyen2004 No, there is no need to do that.
@NancyLi1013 That seems to be an error introduced by @ras0219 changes to MSYS. (see https://github.com/microsoft/vcpkg/issues/13327#issue-691726380). It seems like x264 was  forgotten to be removed from the skiplist.

This should be fixed by #13450.

Alright I'll test it out


CT 200 not working

Describe the bug
CT 200 stops working after a specific time. To solve the Problem you have to restart Homeassistant every time.
To Reproduce
Steps to reproduce the behavior:
No actions needed. Just stops working after a wile. Seems to be no communication between CT200 and Homeassistant.
Got some Errors:
Logger: slixmpp.stringprep
Quelle: custom_components/bosch/init.py:14
Integration: Bosch thermostat (Dokumentation, Probleme)
Erstmals aufgetreten: 09:54:03 (1 Vorkommnisse)
Zuletzt protokolliert: 09:54:03
Using slower stringprep, consider compiling the faster cython/libidn one.

Logger: homeassistant.util.loop
Quelle: util/loop.py:136
Erstmals aufgetreten: 09:54:03 (1 Vorkommnisse)
Zuletzt protokolliert: 09:54:03
Detected blocking call to load_default_certs with args (<ssl.SSLContext object at 0x7fbe27ef5e50>, <Purpose.SERVER_AUTH: _ASN1Object(nid=129, shortname='serverAuth', longname='TLS Web Server Authentication', oid='<IP_ADDRESS>.<IP_ADDRESS>.1')>) inside the event loop by custom integration 'bosch' at custom_components/bosch/init.py, line 234: self.gateway = BoschGateway( (offender: /usr/local/lib/python3.12/ssl.py, line 713: context.load_default_certs(purpose)), please create a bug report at https://github.com/bosch-thermostat/home-assistant-bosch-custom-component/issues For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#load_default_certs Traceback (most recent call last): File "", line 198, in _run_module_as_main File "", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/main.py", line 223, in  sys.exit(main()) File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/src/homeassistant/homeassistant/setup.py", line 165, in async_setup_component result = await _async_setup_component(hass, domain, config) File "/usr/src/homeassistant/homeassistant/setup.py", line 461, in async_setup_component await asyncio.gather( File "/usr/src/homeassistant/homeassistant/setup.py", line 463, in  create_eager_task( File "/usr/src/homeassistant/homeassistant/util/async.py", line 45, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 742, in async_setup_locked await self.async_setup(hass, integration=integration) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup result = await component.async_setup_entry(hass, self) File "/config/custom_components/bosch/init.py", line 151, in async_setup_entry _init_status: bool = await gateway_entry.async_init() File "/config/custom_components/bosch/init.py", line 234, in async_init self.gateway = BoschGateway(

Logger: homeassistant.util.loop
Quelle: util/loop.py:77
Erstmals aufgetreten: 09:54:04 (1 Vorkommnisse)
Zuletzt protokolliert: 09:54:04
Detected blocking call to load_verify_locations with args (<ssl.SSLContext object at 0x7fbe27ef5e50>,) in /usr/local/lib/python3.12/site-packages/slixmpp/xmlstream/xmlstream.py, line 813: self.ssl_context.load_verify_locations(cafile=ca_cert) inside the event loop; This is causing stability issues. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#load_verify_locations Traceback (most recent call last): File "", line 198, in _run_module_as_main File "", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/main.py", line 223, in  sys.exit(main()) File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/local/lib/python3.12/site-packages/slixmpp/xmlstream/handler/coroutine_callback.py", line 60, in pointer_wrapper await pointer(stanza) File "/usr/local/lib/python3.12/site-packages/slixmpp/features/feature_starttls/starttls.py", line 63, in _handle_starttls_proceed if await self.xmpp.start_tls(): File "/usr/local/lib/python3.12/site-packages/slixmpp/xmlstream/xmlstream.py", line 828, in start_tls ssl_context = self.get_ssl_context() File "/usr/local/lib/python3.12/site-packages/slixmpp/xmlstream/xmlstream.py", line 813, in get_ssl_context self.ssl_context.load_verify_locations(cafile=ca_cert)

** Debug SCAN **
http://jsonblob.com/1296393173562417152
Best Regards

Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht
Logger: custom_components.bosch
Quelle: custom_components/bosch/init.py:418
Integration: Bosch thermostat (Dokumentation, Probleme)
Erstmals aufgetreten: 03:41:54 (1564 Vorkommnisse)
Zuletzt protokolliert: 10:12:22
Bosch object of entity Lia is no longer available. Error requesting data from /programs/list
Bosch object of entity Lars is no longer available. Error requesting data from /programs/list
Bosch object of entity Schlafzimmer is no longer available. Error requesting data from /programs/list
Bosch object of entity Arbeitszimmer is no longer available. Error requesting data from /programs/list
Bosch object of entity Keller is no longer available. Error requesting data from /programs/list

Possibly a duplicate of #454


Series of buttons in input group

There are both code for .input-group-btn > .btn + .btn and input-group-btn > btn-group in input-group.scss. Bootstrap supports the both markup?

  <input type="text" class="form-control">

    <button class="btn btn-primary" type="button">Button</button>
    <button class="btn btn-primary" type="button">Button</button>

  <input type="text" class="form-control">

      <button type="button" class="btn btn-primary">Button</button>
      <button type="button" class="btn btn-primary">Button</button>

If not support either one, scss code will be more simple. And also it would be helpful if the document mention about a btn-group in the input group .

Bug reports must include a live demo of the problem. Per our contributing guidelines, please create a reduced test case via CodePen or JS Bin and report back with your link, Bootstrap version, and specific browser and OS details.

Demo: https://jsbin.com/sivavuyuxa/1/edit?html,css,output
Both markup are the same results. I do not think this is a bug.

Both are in the docs and the source code, so yes.

I updated the demo to btn-outline-xxx from btn-xxx
https://jsbin.com/giyuwobuxi/edit?html,css,output
Screenshot:

The right side buttons border are different according to the markup.


Ensure Algolia attribution is present on search dropdown

Hello!
Just wanted to pop in to mention that the Algolia logo in the search dropdown doesn't appear to be visible in Firefox (oddly enough). Screenshot time!
Firefox 56 (OS X):

Check that bottom right corner...
Chrome 61 (OS X):

I see that our very own @Haroenv touched this topic in https://github.com/facebook/react/pull/11032. Could be a good place to start looking?
For the sake of completeness, I've also looped in @vjeux via email, which isn't a GitHub Issue but oh well! 😉

Whoops, I didn't test it in FF, it works in Safari though 😃

I am doing some tests on this and it looks like its an svg issue on how firefox detects the svg passed as background img. I am trying to figure it out but do not know enough about svg.

@renatoselenica, oh good catch! I think we forgot to encode the hash

Fantastic - thanks everybody!


TypeError: init() missing 1 required keyword-only argument: 'intents'

I really hope this is an error on my part but trying to launch this atm seem to result in
(aibot) C:\Users\Maxim\Desktop\various\FUCK\AI>python main.py
Traceback (most recent call last):
  File "C:\Users\Maxim\Desktop\various\FUCK\AI\main.py", line 56, in <module>
    main()
  File "C:\Users\Maxim\Desktop\various\FUCK\AI\main.py", line 47, in main
    client = ChatBot(args.maxlines)
  File "C:\Users\Maxim\Desktop\various\FUCK\AI\Bot\bot.py", line 18, in __init__
    super().__init__()
TypeError: __init__() missing 1 required keyword-only argument: 'intents'

Not sure what could cause this as i have both discord and aitextgen installed (both most recent versions)
can provide more as needed

see #9 , it's kind of both on your end and my end, havent gotten around to fixing it yet but its easy for you to get around

oh and you'll also need to launch it with your token so doing python main.py just by itself won't ever work for unrelated reasons. you either do python main.py --test (which should work for you right now) to talk to it one-on-one in the command line, or you do it with --token to actually put it live on discord

oh no the not working without --token or --test i know about! usually it however says that it requires a token which is not what happened here
however some more info
I did install discord.py (was 2.0.1 before, now 2.0.0) and --test seems to run fine however --token [token] results in the same error as above

turns otu im an idiot! i forgot to install requirements.txt! apologies for the troubles

no problem enjoy :)


New nuget packages not shipping on merge

Describe the bug
Publishing of pre packages from v2_develop has stopped working with error:
/home/runner/work/_temp/729717ff-0270-463a-80f6-2cbe70f5b9be.sh: line 2: Import-Module: command not found

For example, see this build

You need to add powershell to the environment if you want to build it in that fashion.
Otherwise you can just dotnet build on them in sequence.
I'd say add powershell. There are other useful things we can do.

Though of course the dotnet build way is less to figure out if you want a quick solution.

Or...
Another option is to add a configuration to the solution intended for CI builds that doesn't exclude compiling the analyzer library.
That might actually be the best thing to do anyway, because we can also have it not do anything we don't need it to do a lot easier that way.

That method also meshes well with having other build targets or msbuild project files used for CI builds.
When you do that, then people don't see it in VS and wonder WTF it is, and it just gets used in combination with the solution.
So many options. And most aren't even mutually exclusive. 😅

Fixed. Sorry about that.

Would you like me to shift back to doing the stuff I was talking about in the thread for enhancing the build process, instead, now that I'm no longer actively doing anything to @BDisp's Region branch til he finishes with his improvements?
As part of the github workflow improvements, making the runners fork-friendly (beyond just suppressing them), so that people can test without the noise of failed deployments and such will be a good thing. This issue and the others directly related to the gh build runners can be caught before merge time if that's more friendly. And that actually might simply come down to a checkbox in the project, but they've been upgrading and changing things a lot so I'll have to go make sure that's not different from the last one I had to set up, a few months ago.

I'm game for that.
I've gotten this projects CI/CD working only because I am good at copy pasting, not knowledge.
I can't even spell YAML.

YAML  YAML
FTFY. 😅
To be fair, the documentation is really bad. It very rarely says enough to actually understand something.
And I've never seen an official schema, either. The links that look like they might lead to one don't go to one. All I want is a schema!


Please check all of the platforms you are having the issue on (if platform is not listed, it is not supported)

[ ] iOS
[x] Android
[ ] UWP
[ ] watchOS
[ ] tvOS
[ ] Tizen
[ ] .NET Standard

Feature Library

[ ] Core
[ ] BluetoothLE
[ ] Beacons
[x] Locations
[ ] HTTP Transfers
[ ] Notifications
[ ] Sensors

Version of Library
MyGet: <IP_ADDRESS>7
Version of OS(s) listed above with issue
Android 10, SDK version 29
Steps to Reproduce

Give the Access_background_location permission
GpsManager.StartListner with UseBackground = true on Android 10

Expected Behavior
Listner starts
Actual Behavior
Exception thrown: System.ArgumentException:** 'Invalid State Denied'
Sugestion
In the file Android\GpsManagerImpl.cs on line 41 shiny is asking permission for ACCESS_BACKGROUND_LOCATION should this not be android.permission.ACCESS_BACKGROUND_LOCATION
(might be wrong, so just a suggestion, anyways thank your sharing this awesome library)

You are correct.  I’ll get that fixed up.  Thanks.
Feel free to send a PR in the future.

Fixed in the latest beta


[SR-9461] Resolve duplicate output in swift bulid

Previously, we would re-update the progress animation with the previous description when a command with shouldShowStatus returning false starts. Now, with the new build animation, it makes more sense to completely disregard those commands, both in the counting and the output. Yams now builds with the following output:
[1/7] Compiling CYaml src/writer.c
[2/7] Compiling CYaml src/parser.c
[3/7] Compiling CYaml src/reader.c
[4/7] Compiling CYaml src/emitter.c
[5/7] Compiling CYaml src/api.c
[6/7] Compiling CYaml src/scanner.c
[7/7] Compiling Swift Module 'Yams' (16 sources)

@swift-ci please smoke test


Confusing "Figure already exists" error message with 404 scenario

@mriedem commented on Mon Feb 28 2022
Information

Qiskit IBM Provider version: latest (actually qiskit-ibmq-provider 0.18.3)
Python version: n/a
Operating system: n/a

What is the current behavior?
qiskit-experiments parallel experiments first try to create the parent experiment and then the children experiments and upload plots (figures) for the child experiments. If the parent experiment fails to create then the children experiments will also fail (this seems like a separate issue where there are cascading failures that don't stop the processing), and then trying to create figures for those child experiments will fail with something like this:
Unable to save the experiment data: Traceback (most recent call last):
  File "/nas/systems/pok/pok008_system1/2021_03_24_F518_Bangkok/playing/mattias/qiskit-experiments/qiskit_experiments/database_service/utils.py", line 152, in save_data
    return True, new_func(**kwargs)
  File "/home/labuser/.virtualenvs/controller/lib64/python3.8/site-packages/qiskit/providers/ibmq/experiment/ibm_experiment_service.py", line 1104, in create_figure
    response = self._api_client.experiment_plot_upload(experiment_id, figure, figure_name,
  File "/usr/lib64/python3.8/contextlib.py", line 131, in __exit__
    self.gen.throw(type, value, traceback)
  File "/home/labuser/.virtualenvs/controller/lib64/python3.8/site-packages/qiskit/providers/ibmq/experiment/utils.py", line 32, in map_api_error
    raise IBMExperimentEntryNotFound(error_msg + f" {api_err}") from None
qiskit.providers.ibmq.experiment.exceptions.IBMExperimentEntryNotFound: 'Figure figure_47e90a4d_2022-02-21T09:57:47.352206_0.svg already exists. \'404 Client Error: Not Found for url: https://api.quantum-computing.ibm.com/resultsdb/experiments/47e90a4d-b3dd-4964-9345-4884cebd8382/plots. {"errors":["Experiment 47e90a4d-b3dd-4964-9345-4884cebd8382 does not exist"]}\''

Note that this is actually using qiskit-ibmq-provider since qiskit-ibm-provider isn't released yet, but it's the same code.
The bug is that the error message says Figure figure_47e90a4d_2022-02-21T09:57:47.352206_0.svg already exists which is misleading. It's hard-coded here:
https://github.com/Qiskit/qiskit-ibm-provider/blob/f4ff3b0dcf04ecb6cb21aea4e3045f312f77bbff/qiskit_ibm/experiment/ibm_experiment_service.py#L1121
The actual issue is the 404 on the experiment ID in the path - the experiment doesn't exist so you can't upload a plot for it. The "figure already exists" is confusing since it's a 404 rather than a 409 case.
Steps to reproduce the problem
Try to upload a figure for an experiment which doesn't exist.
What is the expected behavior?
I'd expect to see something about the experiment not existing - which is part of the error message, just not the first part.
Suggested solutions
Maybe generalize the string to map_api_error to be like f"Creating figure {figure_name} failed.".

Moving this issue from @mriedem (raised in qiskit-ibm-provider) because the experiment service will be implemented in qiskit-ibm-experiment.
@gadial - can you take a look?

This is a serious issue which I also encountered today independently and occurs in many places in the code; will try to fix this asap.

Fixed in #25


[Feature Request]: Expose onDismiss event on popover

Description
Can the Popover component expose an onDismiss Event?
In my case, I have an a copy icon that, once clicked, copies some content, changes to a checkmark and opens a Popover. Once the Popover is closed I'd like to revert the checkmark back to a copy icon.
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate requests

Hi @solamanhuq !
Is there a reason why you're not using the existing Copy to Clipboard pattern? See https://cloudscape.design/components/copy-to-clipboard/.

hey @timogasda ! thanks for following up!
Plainly, I like how Github handles Copy to Clipboard. Call it preference but it feels more responsive.

changing the icon to a green checkmark is highly visible to  abled end users...no reading involved.
Naturally we want to change the icon back.

Perhaps a counter argument is a lack of accessibility, but isn't that the purpose of the popover anyway? An additional visual indicating the same thing doesn't limit access to impaired users.

Thanks for providing the extra feedback here. We don't currently plan to change the copy to clipboard pattern as we believe that having a single feedback/success mechanism (the popover) is optimal, and as such don't see a strong need for this additional event.


README uses unexported functions

The only exported function is add_to_deps, but the readme uses other as well.
In other words,
using PkgDevTools
update_deps()

fails

Yeah, we can export the user-facing pieces


Support the Echo Flex Motion Sensor Add-on

I have the new Echo Flex with Motion Sensor add-on, see https://www.amazon.com/Echo-Flex/dp/B0814BKDJ8?th=1 .
While Alexa app can trigger events in HA when motion is detected (or no motion is detected for a configurable time span), I'd like to have a presence detection and/or motion sensor integration in HA.
Any plans to add features for Echo Flex Add-ons to the project?
Another Flex Add-on, which I do not own, is Smart Night Light. There may come more.

If you can generate alexapy.alexawebsocket logs that show the motion sensor is reporting itself, then we may have an ability to add a motion sensor. It's possible it's not exposed externally.

Thanks for your reply.
Alas, I have no idea how to generate alexapy.alexawebsocket logs. Is there a description for this somewhere, so I can try to generate it?

See here. You can specifically enable alexapy.alexawebsocket.

OK, I'll do that when I come back from holidays!

OK, I now have 40 pages of logs. What kind of data is of interest? How would I find the right log entries for you?

See if there are any websocket logs that happen when motion happens. It may be easiest to watch the logs while trying to trigger the motion sensor.
You should be seeing something like
 2020-01-01 00:56:35 DEBUG (MainThread) [alexapy.alexawebsocket] Received WebSocket MSG.


Support schema definitions

Currently, this repo consists of SVG and XMI for describing the model. Developing a SBOM schema by vector image or using XMI (an XML format that no tool understands) is a non-starter. I cannot see how this effort will be successful if we are looking at images without the ability discover, or dynamically browse the schema we're developing.
This seems to be multiple anti-patterns laid on top of each other in order to satisfy a standards body's requirements. It's actually quite crippling when you factor in that only a single individual in the working groups knows how to use the tool and has been doing all the development.
If you want increased participation in this effort, first-class support for XSD and JSON schema should be the approach. Let the community use the vast selection of tools available to understand and help develop the schema. Then use whatever conversion utility is required to generate the XMI to satisfy the standards body.
Without this capability, this project will likely never receive PRs to add corrections or other changes to the model as I don't think anyone will take the time to submit PRs against a vector image or XMI.

Philippe-Emmanuel, I believe our proposed path is to iterate on the modeling using a UML tool (see list of UML tools here - https://en.wikipedia.org/wiki/List_of_Unified_Modeling_Language_tools ). The tool you are using is GenMyModel (https://www.genmymodel.com/). Can you confirm?

The current xmi model (posted about 4 hours ago), cannot be imported into GenMyModel.
When importing it, the error reads:

Project cannot be created
Sorry but we couldn't detect the type of this model

The xmi also cannot be imported into StarUML (which also supports xmi 2.0 and 2.1). The issue with xmi, is that there are so many incompatibilities between the various tools it basically makes it unusable for sharing.
Of interest, I also have the same problem with SPDX which about two weeks ago published their model in xmi format, neither GenMyModel or StarUML work.
If the current model was created with GenMyModel (which I believe it was), then its export function is broken because it cannot be reimported.
So we currently have an xmi specification with tool-chain incompatibilities which prevent us from working on the model.  We need to solve this issue if we are to successfully collaborate on the model.
Again, since xmi is such an issue, we should be developing with standards that are widely supported and interchangeable like XML Schema and JSON Schema. Developing to these specs first would allow us to rapidly prototype and then once we have something we think can be submitted, then worry about xmi. This xmi-first approach is inherently broken. I've wasted too many hours today dealing with it. Done.

I can provide (later, I’m connecting in London right now) the XMI from GenMyModel
Philippe-Emmanuel Douziech
Principal Research Scientist, CAST Research Labs
M: +33 6 69 95 49 59tel:+33 6 69 95 49 59
CASThttp://www.castsoftware.com/ | Software Intelligence for Digital Leaders | Bloghttp://www.castsoftware.com/blog | LinkedInhttps://www.linkedin.com/company/162909/ | Twitterhttps://twitter.com/OnQuality
On 13 Dec 2019, at 02:53, Steve Springett<EMAIL_ADDRESS>wrote:

The current xmi model (posted about 4 hours ago), cannot be imported into GenMyModel.
When importing it, the error reads:
Project cannot be created
Sorry but we couldn't detect the type of this model
The xmi also cannot be imported into StarUML (which also supports xmi 2.0 and 2.1). The issue with xmi, is that there are so many incompatibilities between the various tools it basically makes it unusable for sharing.
Of interest, I also have the same problem with SPDX which about two weeks ago published their model in xmi format, neither GenMyModel or StarUML work.
If the current model was created with GenMyModel (which I believe it was), then its export function is broken because it cannot be reimported.
So we currently have an xmi specification with tool-chain incompatibilities which prevent us from working on the model. We need to solve this issue if we are to successfully collaborate on the model.
Again, since xmi is such an issue, we should be developing with standards that are widely supported and interchangeable like XML Schema and JSON Schema. Developing to these specs first would allow us to rapidly prototype and then once we have something we think can be submitted, then worry about xmi. This xmi-first approach is inherently broken. I've wasted too many hours today dealing with it. Done.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://github.com/cdfoundation/sig-security-sbom/issues/6?email_source=notifications&email_token=AFRJPERFHHJEI6T4MTYOLZLQYL2JHA5CNFSM4JTXYEU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGYXPXY#issuecomment-565278687, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFRJPERT6YGYMCBVPQPTTODQYL2JHANCNFSM4JTXYEUQ.

I‘ll also try and share my GenMyModel project online
Philippe-Emmanuel Douziech
Principal Research Scientist, CAST Research Labs
M: +33 6 69 95 49 59tel:+33 6 69 95 49 59
CASThttp://www.castsoftware.com/ | Software Intelligence for Digital Leaders | Bloghttp://www.castsoftware.com/blog | LinkedInhttps://www.linkedin.com/company/162909/ | Twitterhttps://twitter.com/OnQuality
On 13 Dec 2019, at 10:48, Philippe-Emmanuel Douziech<EMAIL_ADDRESS>wrote:
 I can provide (later, I’m connecting in London right now) the XMI from GenMyModel
Philippe-Emmanuel Douziech
Principal Research Scientist, CAST Research Labs
M: +33 6 69 95 49 59tel:+33 6 69 95 49 59
CASThttp://www.castsoftware.com/ | Software Intelligence for Digital Leaders | Bloghttp://www.castsoftware.com/blog | LinkedInhttps://www.linkedin.com/company/162909/ | Twitterhttps://twitter.com/OnQuality
On 13 Dec 2019, at 02:53, Steve Springett<EMAIL_ADDRESS>wrote:

The current xmi model (posted about 4 hours ago), cannot be imported into GenMyModel.
When importing it, the error reads:
Project cannot be created
Sorry but we couldn't detect the type of this model
The xmi also cannot be imported into StarUML (which also supports xmi 2.0 and 2.1). The issue with xmi, is that there are so many incompatibilities between the various tools it basically makes it unusable for sharing.
Of interest, I also have the same problem with SPDX which about two weeks ago published their model in xmi format, neither GenMyModel or StarUML work.
If the current model was created with GenMyModel (which I believe it was), then its export function is broken because it cannot be reimported.
So we currently have an xmi specification with tool-chain incompatibilities which prevent us from working on the model. We need to solve this issue if we are to successfully collaborate on the model.
Again, since xmi is such an issue, we should be developing with standards that are widely supported and interchangeable like XML Schema and JSON Schema. Developing to these specs first would allow us to rapidly prototype and then once we have something we think can be submitted, then worry about xmi. This xmi-first approach is inherently broken. I've wasted too many hours today dealing with it. Done.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://github.com/cdfoundation/sig-security-sbom/issues/6?email_source=notifications&email_token=AFRJPERFHHJEI6T4MTYOLZLQYL2JHA5CNFSM4JTXYEU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGYXPXY#issuecomment-565278687, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFRJPERT6YGYMCBVPQPTTODQYL2JHANCNFSM4JTXYEUQ.

The XMI  that was shared cannot be opened in StarUML, but can be opened in GenMyModel.  So it appears that in order to look at the model, we'll always need to be online, and we'll always need to use this single tool.
The exported XMI does not contain a diagram. So there's no way to visualize the relationships between the various objects without having to resort to images. This is so frustrating. Seriously, if we were modeling in XSD, anyone could use virtually any XML authoring tool and visualize the model while they author it.
These are logistics that should have been worked out back in Nashville prior to inviting myself and a host of others to join, only to find out we actually cannot contribute.
If the standards body requires essentially broken standards with tools containing broken implementations of those standards, then I don't see a path forward. I certainly don't see a way for me to contribute to this specification.

Hello @stevespringett
I appologize for this.
The way I worked with CISQ workgroups in the past was about sharing illustrations and text document explaining the model to submit to the OMG. I would then collect feedback from work group members in any form, then update the model, generate new illustrations and text document, share them, and iterate.
People were not so interested in co-developping the model, only about reviewing and commenting.
That is the process I proposed in Nashville. But I understand you would like to interact with the model itself, and that raises the issues you've faced.
Again, sorry about this.
I'll work on generating an XSD you could use, but it'll take me some time.
Meanwhile, free-form comments based on illustrations and word documents to identify improvement/correction/... areas are welcome.
Would it work for you?

So, don't go out of your way for me. Take it up on the next call and decide on a path forward. If the group is fine with yourself doing all the work, then that's fine. If the group wants to jointly collaborate on it, then consider this ticket.
Simply supplying an XSD however, doesn't provide the necessary transparency or traceability necessary for collaboration as there's no way to trace pull requests or other changes made to the XSD back to the XMI master model. This is ironic since the SBOM specification we're developing is suppose to facilitate transparency and traceability, yet, we're unable to do it ourselves.
If you look at specs like JSON Schema for example, the entire spec was designed and collaborated on GitHub, where changes, issues, and pull requests to the XML and JSON sources are fully tracked. In this way, it's possible to review every change made to find out why something is designed the way it is.

Philippe-Emmanuel made his generation tool available. See comments below:

My generation tool is an R script now available in GitHub buildDocxAndXmi.R. It needs only be executed.
I run it with R version 3.6.0 from within Rstudio (either Rstudio desktop on Windows and Mac OS X, either Rstudio Server on a Centos 7 linux server).
The model JSON files are the ones I shared a while ago in GitHub https://github.com/cdfoundation/sig-security-sbom/tree/master/modeling/model_configuration  and in Google drive https://drive.google.com/open?id=1lt178cCqyL9_QjmJNOWUstHWqO0IAWAE .
The tool can handle multiple locations to try multiple model files. Currently, it expects files in ./model/plb/ subdirectory.


The Sphinx docstring hover may be more pretty

Thank you for a great tool! It's a big pleasure to use it!
Environment data

Language Server version: v2021.3.4
OS: Ubuntu 18.04
Python 3.7, pipenv 2020.11.15

Expected behaviour
Here is example of Jedi's hover

Actual behaviour

Code Snippet / Additional information
code snippet from
https://sphinx-rtd-tutorial.readthedocs.io/en/latest/docstrings.html#an-example-class-with-docstrings
class SimpleBleDevice(object):
    """This is a conceptual class representation of a simple BLE device
    (GATT Server). It is essentially an extended combination of the
    :class:`bluepy.btle.Peripheral` and :class:`bluepy.btle.ScanEntry` classes

    :param client: A handle to the :class:`simpleble.SimpleBleClient` client
        object that detected the device
    :type client: class:`simpleble.SimpleBleClient`
    :param addr: Device MAC address, defaults to None
    :type addr: str, optional
    :param addrType: Device address type - one of ADDR_TYPE_PUBLIC or
        ADDR_TYPE_RANDOM, defaults to ADDR_TYPE_PUBLIC
    :type addrType: str, optional
    :param iface: Bluetooth interface number (0 = /dev/hci0) used for the
        connection, defaults to 0
    :type iface: int, optional
    :param data: A list of tuples (adtype, description, value) containing the
        AD type code, human-readable description and value for all available
        advertising data items, defaults to None
    :type data: list, optional
    :param rssi: Received Signal Strength Indication for the last received
        broadcast from the device. This is an integer value measured in dB,
        where 0 dB is the maximum (theoretical) signal strength, and more
        negative numbers indicate a weaker signal, defaults to 0
    :type rssi: int, optional
    :param connectable: `True` if the device supports connections, and `False`
        otherwise (typically used for advertising ‘beacons’).,
        defaults to `False`
    :type connectable: bool, optional
    :param updateCount: Integer count of the number of advertising packets
        received from the device so far, defaults to 0
    :type updateCount: int, optional
    """

Is the suggestion to look like jedi's?
Note that jedi's output here (as converted to markdown in VS Code, at least) is incorrect as it's treating random indented blocks as code. We recently fixed that in Pylance to try and preserve the indention in the docstring, so those lines are properly treated as regular text in our tooltip (which is the expectation).

Thank you for your reply!
Yes, I suggest it to look like Jedi's.
Well, it's hard to explain in specific words.
I would like the text to look less dense.
On the other side, it supposed to be a docstring's responsibility.

Baffled by VS Code docstring support. Is it markdown? is it sphinx? is it google style? Is it some undocumented mess combining elements of all flavours? I am confused and frustrated with it.

Hi, at this point it's close to 2 years since @jeremyvital4 's excellent summary of what's desired. Should another ticket be opened cause this one is closed and probably forgotten?

I created a new issue from @jeremyvital4's comment: https://github.com/microsoft/pylance-release/issues/4414


Interacting with Julti Scene After Clicking on Lock Display Crashes All Instances

When interacting with the Multi Scene feature after clicking on the "Lock Display" option, all open instances of the application crash simultaneously.
Crash Log: View Log
Video:
https://github.com/DuncanRuns/Julti/assets/83808600/7ce0f931-d27b-4961-b6d7-69d12f804121

https://obsproject.com/kb/minecraft-java-edition-troubleshooting
if you dont use fullscreen or wouldnt mind switching to windowed/borderless, then you can try obs > tools > scripts > check use window capture for julti scene sources > generate scenes

After a lot of Trials I have managed to get this working, At first Windowed capture did not work at all, but if you go into OBS and right-click the window and manually Capture Method "Windows 10 (1903 and up)" for every instance it works.
The output seems to be a lot 'dimmer'? like a lower color gambit but as long as its verifiable it's fine.


Cleaned up a lot of code

a lot of the "code" written are comments

this is DISGUSTING. and yet beautiful.

yeah no, its only disgusting


Redo of (PR #56)

Redo of (PR #56) - Initial Implementation of General Diagnostic Cluster

Hey coool, CLA worked now!
I review soon


ignoring unetr tests

Signed-off-by: Wenqi Li<EMAIL_ADDRESS>Description
workaround for https://github.com/Project-MONAI/tutorials/issues/276
Status
Ready
Checks

[ ] Notebook runs automatically ./runner [-p <regex_pattern>]

Thanks for the quick fix.
Maybe we also need to remove this line?
https://github.com/Project-MONAI/tutorials/blob/5283b2648ce59e84d0f4bafadbfba67f8dbd8079/runner.sh#L35
Thanks.


Make sure there's always a profile set

Without this, we can have forms with no default profile set in the form.

We do make the first profile the default one in the back end, but that's too far down the workflow and that makes the new _validate_posted_profile_options function to fail because the selected_options contains info about the profile, for example {'profile': None} instead of the options corresponding to the default profile.
This could have been also fixed by moving the default just before the check https://github.com/batpad/kubespawner/blob/68a71f939e73325469b5e664a43b9b0b440b7b69/kubespawner/spawner.py#L3196-L3197
But since all the other options have defaults set by the form (it's not clear to me from the HTML why, but removing all defaults, still show defaults in the form :/ ), why not have the profiles also have the same.
cc @yuvipanda

Wait, this breaks having a default profile when the API is used instead of the form :(. Investigating...

I think the only change needed here is the on in the html form

@GeorgianaElena I'm somewhat confused too, particularly around usage when this just gets used via API. Should the code changes here outside of the form be reverted?
I agree all this points to the code needing to be simplified.

Closing this in favor of https://github.com/batpad/kubespawner/pull/2


Replaced 'kubectl apply' with 'kubectl create' in README

Updated as per issue 1317
Version bump so that folks copy/pasting get the latest version

https://github.com/actions-runner-controller/actions-runner-controller/issues/1317

Quite strange, when arriving on the main repo pages, the README still mentions  kubectl apply...

Quite strange, when arriving on the main repo page, the README still mentions kubectl apply, even if the default branch is indeed master...

The new simplified documentation refactored the readme - looks like it just slipped back in. :)


Standardize types of values accepted as resources in Job (resolves #1063)

resolves #1063
memory and disk can now only accept ints and humanized strings.
cores can accept only ints and floats.

Very good. Will merge once tests pass.

Jenkins, test this please.

x/1.5 can be rewritten in integer math as x*2/3
that's more readable, too.

Better?

Doesn't feel minimal to me. There are redundant checks in there. The str() invocation is redundant (and I mentioned this before). And I forgot, please add doctests (also as mentioned on Slack earlier).

Oops forgot the doctests.
I added the str so we handle int, float and str. Anything else gets a generic error.I felt this was minimal and handled every case.

def _parseResource( name, value ):
    """
    Parse a Toil job's resource requirement value and apply resource-specific type checks. If the
    value is a string, a binary or metric unit prefix in it will be evaluated and the
    corresponding integral value will be returned.

    :param str name: The name of the resource

    :param None|str|float|int value: The resource value

    :rtype: int|float|None

    >>> _parseResource('cores', None)
    >>> _parseResource('cores', 1), _parseResource('disk', 1), _parseResource('memory', 1)
    (1, 1, 1)
    >>> _parseResource('cores', '1G'), _parseResource('disk', '1G'), _parseResource('memory', '1G')
<PHONE_NUMBER>,<PHONE_NUMBER>,<PHONE_NUMBER>)
    >>> _parseResource('cores', 1.1)
    1.1
    >>> _parseResource('disk', 1.1)
    Traceback (most recent call last):
    ...
    TypeError: The 'disk' requirement does not accept values that are of <type 'float'>
    >>> _parseResource('memory', object())
    Traceback (most recent call last):
    ...
    TypeError: The 'memory' requirement does not accept values that are of <type 'object'>
    """
    assert name in ('memory', 'disk', 'cores')
    if value is None:
        return value
    elif isinstance( value, str ):
        value = human2bytes( value )
    if isinstance( value, int ):
        return value
    elif isinstance( value, float ) and name == 'cores':
        return value
    else:
        raise TypeError( "The '%s' requirement does not accept values that are of %s"
                         % (name, type( value )) )

Less code, more tests, more precise documentation.

Hmmm.. ok! I implemented you method!


Verify proto libraries support unknown fields

We need to verify that the 3rd party libraries we use support unknown fields, and support accesses the bytes for canonical serialization. (C++ and Golang)

It appears support was added in Golang in this PR:
https://go-review.googlesource.com/c/protobuf/+/244937/

It would seem that this is supported in C++ as per this stack overflow:
https://stackoverflow.com/questions/16607074/accessing-field-of-protobuf-message-of-unknown-type-in-python
I realize it refers python but directly talks about how it's done in C++. It seems the FieldDescriptor will be returned and you have access to serialized data and field number (which should do the trick).

BOOST_AUTO_TEST_CASE( unknown_field_test )
{
   koinos::block_store::block_item bi;
   koinos::block_store::block_record br;

   br.set_block_id( std::string( "123 " ) );
   br.set_block_height( 123 );

   koinos::protocol::block b;
   b.set_id( std::string( "456" ) );

   koinos::protocol::block_receipt r;
   r.set_id( std::string( "456" ) );

   *br.mutable_block() = b;
   *br.mutable_receipt() = r;

   *br.add_previous_block_ids() = std::string( "789" );
   *br.add_previous_block_ids() = std::string( "101112" );

   bi.ParseFromString( br.SerializeAsString() );

   BOOST_REQUIRE_EQUAL( bi.SerializeAsString(), br.SerializeAsString() );
}

func TestUnknownField(t *testing.T) {
	bi := block_store.BlockItem{}
	br := block_store.BlockRecord{}
	br.BlockId = []byte{0x01, 0x02, 0x03}
	br.BlockHeight = 123

	b := protocol.Block{}
	b.Id = []byte{0x04, 0x05, 0x06}

	r := protocol.BlockReceipt{}
	r.Id = []byte{0x04, 0x05, 0x06}

	br.Block = &b
	br.Receipt = &r

	br.PreviousBlockIds = append(br.PreviousBlockIds, []byte{0x07, 0x08, 0x09}, []byte{0x0A, 0x0B, 0x0C})

	brBytes, err := proto.Marshal(&br)
	assert.NoError(t, err)

	err = proto.Unmarshal(brBytes, &bi)
	assert.NoError(t, err)

	biBytes, err := proto.Marshal(&bi)
	assert.NoError(t, err)

	assert.True(t, bytes.Equal(brBytes, biBytes))
}


Git initalizes to main branch but cookiecutter project urls use master

🐛 Bug Report
The git init instructions set up the repo trunk to main. However, the default project urls point to master, e.g. project_name/blob/master/LICENSE
📈 Expected behavior
The URLs in README.md and PULL_REQUEST_TEMPALTE.md should not be broken after a freshly created repo

The current GitHub repository defaults to using main as the main branch, so we recommend also using git branch -M main as the main branch during development.

Are you sure @Undertone0809 ? For example, when I look at the template for README.md I see 19 instances of master being referenced: https://github.com/Undertone0809/python-package-template/blob/main/{{ cookiecutter.project_name.lower().replace('%20'%2C%20'').replace('-'%2C%20'')%20%7D%7D/README.md?plain=1

Oh, I'm sorry. I optimized it in #98

Thank you!


Storage API

This implements a new storage API for python integrations, allowing storing and retrieving data for cache purposes. It implements a simple backend storing data into files, inside a new var directory.
See https://github.com/DataDog/architecture/pull/455 for the RFC.

Is the RFC fully approved ? it's still marked as draft with many comments. Should we finish the RFC first ?


gufe objects not giving informative signatures

Our objects are not returning useful signatures. They all return a <Signature (*args, **kwargs)>.
This is annoying when using our objects in IDEs, e.g., using shift-tab for quick help in Jupyter.
Expected behavior would be to see the actual signature coming from the __init__.
I suspect the source of this problem is our metaclass. Specifically, I think we're actually seeing the signature from _GufeTokenizableMeta.__call__. Not an urgent issue, but I wanted to document it since I'm pretty sure I've identified the reason, although I don't have a trivial solution.
In [1]: import inspect

In [2]: import gufe
LICENSE: Could not open license file "oe_license.txt" in local directory
LICENSE: N.B. OE_LICENSE environment variable is not set
LICENSE: N.B. OE_DIR environment variable is not set
LICENSE: No product keys!
LICENSE: No product keys!
LICENSE: No product keys!
LICENSE: No product keys!
g
In [3]: gufe.__version__
Out[3]: 'v0.2.post227+g69ad4d2'

In [4]: inspect.signature(gufe.ChemicalSystem)
Out[4]: <Signature (*args, **kwargs)>

In [5]: inspect.signature(gufe.SmallMoleculeComponent)
Out[5]: <Signature (*args, **kwargs)>

In [6]: inspect.signature(gufe.ProteinComponent)
Out[6]: <Signature (*args, **kwargs)>

In [7]: inspect.signature(inspect.Signature)
Out[7]: <Signature (parameters=None, *, return_annotation, __validate_parameters__=True)>

Of course, someone has asked on SO: https://stackoverflow.com/questions/49740290/call-from-metaclass-shadows-signature-of-init
Looks like we need to modify the __signature__ attribute per PEP 362.

Fixed in #216.


Hide/show child nodes of a branch

closes #105

Do we want this to be a client-side only feature or server-side as well? Right now, there's still a bug left that the hidden state is not updated across all clients immediately (though I'd assume it calls map.draw.update() whenever something changes), but nodes are correctly hidden if the client updates the page.
Regarding an icon: Somehow very tricky to implement correctly and synchronize across all clients simultaneously.

Do we want this to be a client-side only feature or server-side as well? Right now, there's still a bug left that the hidden state is not updated across all clients immediately (though I'd assume it calls map.draw.update() whenever something changes), but nodes are correctly hidden if the client updates the page.
Regarding an icon: Somehow very tricky to implement correctly and synchronize across all clients simultaneously.

good question, I would say as it only affects visibility it should only be on the client side? otherwise people might confuse this for that a user deleted a branch.

good question, I would say as it only affects visibility it should only be on the client side? otherwise people might confuse this for that a user deleted a branch.

Does it make sense to keep the changes to the data model then? Since those changes are synced server-side, inevitably leading new clients to consider selected nodes hidden as well.

good question, I would say as it only affects visibility it should only be on the client side? otherwise people might confuse this for that a user deleted a branch.

Does it make sense to keep the changes to the data model then? Since those changes are synced server-side, inevitably leading new clients to consider selected nodes hidden as well.

Either we sync it across clients so everybody is watching the same and we have it in our data model - or we just store that property on the client side without adding it to the data model. I think I would prefer the latter one.

Works up to 99% percent, but there's still a weird and oddly specific bug where if two clients hide the same branches at the same time (so branch A and B), client A will unhide branch A when clicking on branch B.
Also missing: Changing the eye icon in the toolbar based on whether or not any child nodes are hidden.

Works up to 99% percent, but there's still a weird and oddly specific bug where if two clients hide the same branches at the same time (so branch A and B), client A will unhide branch A when clicking on branch B.
Also missing: Changing the eye icon in the toolbar based on whether or not any child nodes are hidden.

i dont really understand this problem if hiding/showing is a local operation 🤔

Works up to 99% percent, but there's still a weird and oddly specific bug where if two clients hide the same branches at the same time (so branch A and B), client A will unhide branch A when clicking on branch B.
Also missing: Changing the eye icon in the toolbar based on whether or not any child nodes are hidden.

i dont really understand this problem if hiding/showing is a local operation 🤔

It's not really consistently reproducible, but it's there - I'm trying to figure out if it maybe has something to do with how nodes selected by other users are rendered (maybe it affects the selectedNode variable in nodes.ts?). It's purely a client side issue though, most probably in how D3 renders the nodes, especially when other clients are involved.

Think I found the issue: The NodeUpdated event gets called for Client B whenever Client A hides certain nodes. However, if Client B has already hidden the same set of nodes, the "hidden" values gets overwritten with null, since UtilsService.get(newNode, propertyPath) doesn't return a proper value. That means Client B needs to click twice to unhide already hidden nodes, since it's set from null to true to false.
This can also lead to very funny issues when Client A hides a child, Client B hides every node except the root node and Client A then decides to also hide the root node, because this then hides every node except the originally hidden child.

a web socket update. An mmp event is fine as it's the local map that was updated. That should, however, not trigger a web socket

notifyWithEvent is true by default, forgot to change that to false.
Good point about the local data model - I'll have to test that. Hiding nodes is much more stable now, though I do have odd one-off cases where the parent nodes get hidden whilst children are still visible. I'll set the PR to open for review soon and then we can both test and iron out any kinks.

Updating the data model works fine even when nodes are hidden. One thing that's still missing is some visible way to tell nodes are hidden, either by updating the icon in the toolbar or by attaching an SVG icon inside the drawing area to nodes.

Updating the data model works fine even when nodes are hidden. One thing that's still missing is some visible way to tell nodes are hidden, either by updating the icon in the toolbar or by attaching an SVG icon inside the drawing area to nodes.

a small svg icon somewhere in the node sounds good 👍 the toolbar should also change (thats already done for add/remove image). But I think an additional item inside the node makes also sense as otherwise one might forget it.

Looks good. Two bugs that need more checking:

Undo/Redo is bugged - I got very strange results with it with nodes flying around in space without being attached. If possible I wouldn't consider visibility changes as un/redoable. But thats just on first thought.
Hiding nodes and then exporting the image looks like this:

Not sure what the preferred behavior for this feature is on exports. Either completely hide it (like it is now) or just show it - but without this visibility note thingy. The same is btw true for the link, which just shows "link" - but thats a separate issue.

Not sure what the preferred behavior for this feature is on exports. Either completely hide it (like it is now) or just show it - but without this visibility note thingy. The same also happens for attached links, which just show "link" - but thats a separate issue.

Re this: I think keeping notes invisible when exporting is the preferred option. However, it seems like it doesn't work with Material Icons, so I'm guessing removing the link text ("visibility_off") is the better option.

I'll take a look at undo/redo.

I don't think there's much we can do about undo/redo without a rework. The issue is that if we hide two nodes, that's two steps in the snapshot, with the farthest node being the first step in the snapshot to be undone. Similar weird behaviour can be observed when creating a node with text and undoing it: Creating the node is one step, with the text being a separate step, so it takes two presses of undo to delete a single node.

Not sure what the preferred behavior for this feature is on exports. Either completely hide it (like it is now) or just show it - but without this visibility note thingy. The same also happens for attached links, which just show "link" - but thats a separate issue.

I've removed all text on export now, so neither "link" nor "visibility_off" should appear on export.

There are still bugs: If another user adds nodes to a hidden parent node, it gets weird:


[WIP] feat(lazy-imports): lazy import workaround

it actually works already, but I stumpled onto something else while working on this when there is scoped css in the game. Try to look into this too.
Funny thing came up, it looks like this worked in my scenario due to the reason that I use "modern: client" in my nuxt app. See https://github.com/nuxt/nuxt.js/issues/7311

You can close this PR if you want to, it's only working due to a bug in nuxt, which leads to this behaviour (see https://github.com/nuxt/nuxt.js/issues/7311). On the other side, we can use this bug for now to get async loading up and running ;)

I've posted an example module to workaround this issue in nuxt:
https://github.com/vuejs/vue/issues/9847#issuecomment-626154095


How to get going, the basics and Android & iOS auth

Since no documentation exists for Drywall, what is the best way to get a good grip around Drywall's core functioning to add/remove/modify features?
Also, what would be the best way to make it work with Android/iOS?
Thanks 😄

Thanks for opening an issue.

Since no documentation exists for Drywall, what is the best way to get a good grip around Drywall's core functioning to add/remove/modify features?

Our README covers installation, setup and running the app. The wiki has more about the inner workings.
Remember that Drywall is just a boilerplate, built with other modules/technologies. The documentation of those tools plus what we have here should be sufficient. After digging in and exploring/understanding more of the code base, by all means please open specific issues and suggestions.

Also, what would be the best way to make it work with Android/iOS?

I'm not sure exaclty what you mean. You could customize the API to support mobile/desktop app clients, but those decisions aren't baked in. I also suggest checking out Frame, which is the Drywall API, built with hapi instead of express, has much better testing and doesn't come with all the front-end stuff.

Thanks a lot, I will go through the recommended links.


Prompted to restart to update multiple times for every monthly version

VSCode Version:  1.49.2
OS Version: macOS Catalina 10.15.7

Steps to Reproduce:

Seems like just having vscode open will eventually prompt for an update of the same version

Does this issue occur when all extensions are disabled?: Yes
Every few days the gear has a new notification, saying that I should restart to update vscode. More often than not it's the same version that was already updated several times prior (unless an actual new update has been released). The release page for the month shows as well.

@jasonlewicki to clarify. What you see is (as an example):

You have version 1.49.1 installed
You restart VS Code to update to 1.49.2
After a while you see the badge on the gear again to update.
You restart VS Code, you still sit on 1.49.2 (because that's the latest stable version of VS Code).

@jasonlewicki ahh, ok I think i see what's going on. The monthly updates have minor updates. What I'm seeing on my end is:
"Hey, restart to update"
restarts
*tab popup that says: "Welcome to the AUGUST 2020 update! and in very small print is the incremental update version"
then a few days later:
"Hey, restart to update"
restarts
*tab popup that says: "Welcome to the AUGUST 2020 update! and in very small print is the incremental update version"
I guess, for my perspective, to make it not feel like groundhog day, it would be great to have the release notes say so, and/or when this update was released (and in larger font). Because right now it just looks like the same August update over and over..
Thanks

For reference, this is what a minor version update looks like:

@gregvanl do you remember why we chose to not highlight the incremental version number more?

The highlight might depend on if the client had already installed a previous major/minor version.

@kieferrm I know we decided to leave the version in the main header as major.minor and I don't think users would notice if we changed the point release value.
I think the current bold Update X.YY.Z in a separate section below the main header is quite visible and is a good balance between alerting users and letting them ignore point release details.
We could increase the font size by making these H2s or adding update-specific CSS but right now we're just using standard Markdown paragraphs with bold text.

Closing as bolded point release values just below main header seems like a good balance.


Library seems to fail when sending > 11 bytes of data

I can't seem to get anything over 11 bytes of data to send.
When I write: myLora.txBytes(txBuffer, sizeof(txBuffer)); if txBuffer is > 11 bytes, it will return 0 and take almost
no time to process. I have also made sure to have callend the end() function on my software serial device.
Any ideas as to why this happens? Btw, I am using an esp32 and the rn2903 is running from hardware serial.

Kevin192291, I have been struggling with ESP32 DEV module and RN2903 LoRa P2P Radio’s on HardwareSerial, could we communicate about your success?
Paul Wilkie
<EMAIL_ADDRESS>

When sending fails after a specific number of bytes, then it seems like there is a timing issue.
Are you sure the baud rate is set correct?
The default baud rate for this chip is 57600 bps.
The autobaud is a bit tricky, as you must pull a pin low and then immediately send a specific bit pattern with the desired baud rate.
For example set the serial to 600 bps and write 0x00 then switch to the desired baud rate and write 0x55.
But to avoid issues with the baud rate, first try the default baud rate and make sure the start and stop bits are set correct.
For example there is also a mode with "1.5" stop bit, which takes 1.5 times the normal length of a bit period.

I see, I have removed the auto baud from my initialization code. I was already setting the serial port to 57600, here is what I have:
uint8_t txBuffer[17];

void setup()
{
  // Open serial communications and wait for port to open:
  Serial.begin(115200); //serial port to computer
  Serial2.begin(57600); //serial port to radio

  Serial.println("Startup");
  initialize_radio();
  Serial.println("Radio Initialized Complete");
}

void initialize_radio()
{
  //reset rn2483
  pinMode(LORA_RESET, OUTPUT);
  digitalWrite(LORA_RESET, LOW);
  delay(100);
  digitalWrite(LORA_RESET, HIGH);
  delay(100); //wait for the RN2xx3's startup message
  Serial2.flush();

  //check communication with radio
  String hweui = myLora.hweui();
  while(hweui.length() != 16)
  {
    Serial.println("Communication with RN2xx3 unsuccessful. Power cycle the board.");
    Serial.println(hweui);
    delay(1500);
    hweui = myLora.hweui();
  }

  //print out the HWEUI so that we can register it via ttnctl
  Serial.println("When using OTAA, register this DevEUI: ");
  Serial.println(myLora.hweui());
  Serial.println("RN2xx3 firmware version:");
  Serial.println(myLora.sysver());

  //configure your keys and join the network
  Serial.println("Trying to join TTN");
  bool join_result = false;

  /*
   * OTAA: initOTAA(String AppEUI, String AppKey);
   * If you are using OTAA, paste the example code from the TTN console here:
   */
  const char *appEui = "omitted!";
  const char *appKey = "even more omitted!!!";
  join_result = myLora.initOTAA(appEui, appKey);

  while(!join_result)
  {
    connectAttempts++;
    if(connectAttempts > 4) {
      ESP.restart();
    }
    Serial.println("Unable to join. Are your keys correct, and do you have TTN coverage?");
    delay(1000); //delay a minute before retry
    join_result = myLora.init();
  }
  Serial.println("Successfully joined TTN");

}

and later on in the loop I have:
int result = myLora.txBytes(txBuffer, sizeof(txBuffer));
however, by changing the txBuffer array to 7 elements instead of 17 it will work, like so
int result = myLora.txBytes(txBuffer, 7);
It will also work if i change the actual size of the array up top too.

See this part of the library:
https://github.com/jpmeijers/RN2483-Arduino-Library/blob/9a66cf836482294e371aaae7712f44c7bd0b0990/src/rn2xx3.cpp#L332-L344
Can you change the buffer allocation to something like this:
char msgBuffer[size*2 + 1] = {0};

Just to make sure the buffer is allocated with zeroes (and thus automatically zero-terminated) before it is converted to a String object.

Just made the update the update to both the library with the same results, it seems to be exactly the same.
then after that I tried adding the zero to the end of my array and no luck with that as well (uint8_t txBuffer[17] = {0};)
Then just to double check, I added a txBytes call right after the ttn connection like so:
uint8_t txStartupBuffer[11] = {1,2,3,4,5,6,7,8,9,10,11}; //(at the top)
...
delay(1000); //delay a minute before retry
join_result = myLora.init();
}
Serial.println("Successfully joined TTN");
myLora.txBytes(txStartupBuffer, sizeof(txStartupBuffer)); //Works perfectly!!!
delay(1000);
myLora.txBytes(txBuffer, sizeof(txBuffer)); //nothing
I am not sure if this will be useful, but here is the json from the successful 11 bytes sent:
{
  "@type": "type.googleapis.com/ttn.lorawan.v3.ApplicationUp",
  "end_device_ids": {
    "device_id": "esp32device",
    "application_ids": {
      "application_id": "cropwatch-ec-soil"
    },
    "dev_eui": "0004A30B00EB24FF",
    "join_eui": "70B3D57ED0030779",
    "dev_addr": "01CC43D4"
  },
  "correlation_ids": [
    "as:up:01ECT6RQFGZCGM6G8406PDM9MK",
    "gs:conn:01ECSXYWE82DWGES72FSKMRZ8W",
    "gs:uplink:01ECT6RQ925Y7XC3CM98MFKAJA",
    "ns:uplink:01ECT6RQ93GN32KFHRTQ05SQH9",
    "rpc:/ttn.lorawan.v3.GsNs/HandleUplink:01ECT6RQ93PDN5YRZHGQANJWB1"
  ],
  "received_at": "2020-07-09T16:33:03.984948336Z",
  "uplink_message": {
    "session_key_id": "AXM0bENROmfCTicMG1OXWg==",
    "f_port": 1,
    "frm_payload": "AQIDBAUGBwgJCgs=",
    "decoded_payload": {
      "f_port": 1,
      "raw": [
        1,
        2,
        3,
        4,
        5,
        6,
        7,
        8,
        9,
        10,
        11
      ]
    },
    "rx_metadata": [
      {
        "gateway_ids": {
          "gateway_id": "kevinsgateway"
        },
        "time": "2020-07-09T16:33:04Z",
        "timestamp":<PHONE_NUMBER>,
        "rssi": -109,
        "snr": -14.5,
        "uplink_token": "ChEKDwoNa2V2aW5zZ2F0ZXdheRCM7+iOBA=="
      }
    ],
    "settings": {
      "data_rate": {
        "lora": {
          "bandwidth": 125000,
          "spreading_factor": 10
        }
      },
      "coding_rate": "4/5",
      "frequency": "905300000",
      "timestamp":<PHONE_NUMBER>
    },
    "received_at": "2020-07-09T16:33:03.779542903Z"
  }
}

I just realized, I tested a working device, and on messages that do sent, I get the value:
data_rate_index just above, "coding_rate" here is an example of a working version using thethingnetwork.h library:
{
  "@type": "type.googleapis.com/ttn.lorawan.v3.ApplicationUp",
  "end_device_ids": {
    "device_id": "the-things-uno",
    "application_ids": {
      "application_id": "name"
    },
    "dev_eui": "omitted",
    "join_eui": "omitted",
    "dev_addr": "omitted"
  },
  "correlation_ids": [
    "as:up:01ECVHWGMRXRQ21N3WRVWC86T9",
    "gs:conn:01ECVA4459S8CFAZ7ZXKR9TZCF",
    "gs:uplink:01ECVHWGEB5XARN05BN2F36P8J",
    "ns:uplink:01ECVHWGEB9A9WBQ1KA1MD2ARS",
    "rpc:/ttn.lorawan.v3.GsNs/HandleUplink:01ECVHWGEB9TWA26CKRSS51QCG"
  ],
  "received_at": "2020-07-10T05:06:36.824709377Z",
  "uplink_message": {
    "session_key_id": "AXM3HaWvCjLNPERuod8eWw==",
    "f_port": 1,
    "f_cnt": 2,
    "frm_payload": "AGQI3wwHAVUAAAAAGK0I/QYY",
    "decoded_payload": {
      "f_port": 1,
      "raw": [
        0,
        100,
        8,
        223,
        12,
        7,
        1,
        85,
        0,
        0,
        0,
        0,
        24,
        173,
        8,
        253,
        6,
        24
      ]
    },
    "rx_metadata": [
      {
        "gateway_ids": {
          "gateway_id": "kevinsgateway"
        },
        "time": "2020-07-10T05:06:36Z",
        "timestamp": 376066731,
        "rssi": -54,
        "snr": 11,
        "uplink_token": "ChEKDwoNa2V2aW5zZ2F0ZXdheRCrpamzAQ=="
      }
    ],
    "settings": {
      "data_rate": {
        "lora": {
          "bandwidth": 125000,
          "spreading_factor": 7
        }
      },
      "data_rate_index": 3,     <----------------------------That is not there when using RN2xx3 library!!!
      "coding_rate": "4/5",
      "frequency": "904100000",
      "timestamp": 376066731
    },
    "received_at": "2020-07-10T05:06:36.619778535Z"
  }
}

I added this to the bottom of the txBytes method:
String dataToTx = String(msgBuffer);
  _debug.print("string: ");
  _debug.println(dataToTx);
  _debug.print("string length");
  _debug.println(dataToTx.length());
  _debug.print("string Data Sizeof");
  _debug.println(sizeof(dataToTx));
  return txCommand("mac tx uncnf 1 ", dataToTx, false);

Here is my output:
string:<PHONE_NUMBER>00000000000000000000000000000D
string length40
string Data Sizeof12
Library Pre from txCommand says:
12

it appears to me that after String dataToTx(msgBuffer);
the output size is always 12... Not sure why yet.

This looks correct. sizeof is returning the size of the type (a string
object) which would be done at compile time. It is not returning the
length of your string within your string object because sizeof does not
know how to inspect your object to extract the string.
Regards
Mark
On Wed, 15 Jul 2020, 05:42 Kevin<EMAIL_ADDRESS>wrote:

I added this to the bottom of the txBytes method:
String dataToTx = String(msgBuffer);
_debug.print("string: ");
_debug.println(dataToTx);
_debug.print("string length");
_debug.println(dataToTx.length());
_debug.print("string Data Sizeof");
_debug.println(sizeof(dataToTx));
return txCommand("mac tx uncnf 1 ", dataToTx, false);
Here is my output:
string:<PHONE_NUMBER>00000000000000000000000000000D
string length40
string Data Sizeof12
Library Pre from txCommand says:
12
it appears to me that after String dataToTx(msgBuffer);
the output size is always 12... Not sure why yet.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jpmeijers/RN2483-Arduino-Library/issues/78#issuecomment-658541865,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFAGDCUBWMKRVECZ27RLUCTR3UXS7ANCNFSM4OU4RZKQ
.

Is there a way for me to lower the spread factor with this library?

Is there a way for me to lower the spread factor with this library?

The data rate (DR, see setdr) reflects the spreading factor.
For EU settings:
dr = 12 - sf  for sf>= 7 && sf <=12.
For US settings:
dr = 10 - sf
Make sure to only set the data rate for dr >= 0 && dr <= 5.


Add test for TestDataCentrallyAvailable

Will close #7

I think also the file name needs to change now... sorry!


Hide device name and id

PR includes

[x] Bug Fix

Related issues
Resolve #695
QA Instructions, Screenshots, Recordings
https://github.com/taskany-inc/crew/assets/95316053/e4ccc24f-7699-4736-ab38-ca0c6bae462a

I think there should be notification about copied text

https://github.com/taskany-inc/crew/assets/95316053/b9a78ebd-b918-4921-bdd4-10c34f9aa8dd


Listen for back button press

Removes the need to listen for onBackPressed in the Activity. Sample updated to reflect this. Fixes #10.

Sorry for the late response. There's been some good discussion, and we're going to mull over it tonight and tomorrow. In the meantime, @iPaulPro would you mind rebasing on the current master? We just merged a fairly significant change to the sample structure.

@hzsweers No worries. I already merged the latest master, so you should see the big green button. :-)
I also submitted the CLA yesterday morning (before the PR).

Just a couple small comments otherwise it looks good. Sorry for the extended delay.

Merged and updated the API after

Sorry about that! Been super busy. Thanks :-)

No worries, thanks for the PR! This is released now in v1.3


chore: release 1.2.179

:robot: I have created a release *beep* *boop*
1.2.179 (2022-10-11)
Bug Fixes

buildah: git add result in broken symlinks (4013833)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/werf/werf/releases/tag/v1.2.179 :sunflower:


feat: track full Sealed Headers in canonical chain

blocked by https://github.com/paradigmxyz/reth/pull/2769
This tries to track full SealedHeaders instead of their hash.
I'm not 100% sure this is feasible, but ideally we always have a x amount of sealed headers in the chain, which makes things like #2765 easier and would prevent 1 guaranteed look up for on FCU

What's the current plan here?


4.0

Resolves https://github.com/slaughter550/intercom-laravel/issues/4

@JackWH is there anything else you think should be added to V4?

@slaughter550 Thanks for the update, and apologies for my slow response! Some suggestions below... First two would be great, second two are just nice-to-haves:

The current composer.json file locks the Intercom API version to a specific release ("intercom/intercom-php": "3.2.0"). It would be best to use semantic version ranges, so we can always benefit from any minor-version improvements as soon as they are released by Intercom. This issue prevented me from being able to use the delete user API calls added v3.2.0 of the API in June, until the dependency version was bumped in this library in September.

PhpStorm doesn't support autocomplete when using the Intercom facade, as shown in the screenshot below. I'm using Laravel IDE Helper to add PhpStorm autocomplete for everything else, and I know other package facades are able to support autocomplete too, but I'm not sure specifically how to add it. Might be as easy as a @mixin docblock tag? Or maybe more involved, I'm not sure...

Update the package requirements to support PHP 7.1+ only (required as per Intercom API v4 requirements), and therefore upgrade codebase to take advantage of 7.1 features and syntax.

Native support for queueing or retrying Intercom API requests would be useful. In my application, I'm recording user events in numerous places. If the Intercom API goes down (which seems to happen far more often than I'd like), the requests fail. To save littering my code with try catch statements, I ended up creating a wrapper for a Laravel queued job to make the API request, when it can be asynchronous. This way if the API goes down, it will automatically re-try later. Native support for this would be neat.

Hope that helps!

@slaughter550 Sorry, wrote those comments before I'd checked what had changed on this PR!
Point 1 still applies (though against v4 instead of v3). Point 3 might need to be revised to PHP v7.1 instead of v7.0 which it is now, as Intercom API v4 only supports v7.1 and above.

@JackWH

Addressed
Can you tell me which package facades do it and I'll see if I can find what makes them tick?
Addressed.
I agree it fails very often. I will look into a config option for failures. Whether to queue or throw


Use intermediate PR_TITLE variable to secure workflow

The changed workflow was not even run, thus, I merge.


Logout user from the application

IMPORTANT: Where possible all PRs must be linked to a Github issue
Fixes #282
Type
Choose one: (Bug fix | Feature | Documentation | Testing | Code health | Release | Other)
Checklist

[ ] I have written Unit tests for any new feature(s) and edge cases for bug fixes
[x] I have added any strings visible on UI components to the strings.xml file
[ ] I have updated the  CHANGELOG.md file for any notable changes to the codebase
[x] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the project's style guide
[x] I have built and run the fhircore app to verify my change fixes the issue and/or does not break the app

Pull Request Test Coverage Report for Build #132

0 of 0   changed or added relevant lines in 0 files are covered.
92 unchanged lines in 4 files lost coverage.
Overall coverage decreased (-5.5%) to 54.816%

Files with Coverage Reduction
New Missed Lines
%

src/main/java/org/smartregister/fhircore/domain/Pagination.kt
5
14.29%

src/main/java/org/smartregister/fhircore/auth/account/AccountHelper.kt
24
64.71%

src/main/java/org/smartregister/fhircore/activity/BaseSimpleActivity.kt
28
69.23%

src/main/java/org/smartregister/fhircore/fragment/PatientListFragment.kt
35
33.01%

Totals

Change from base Build #131:
-5.5%

Covered Lines:
626

Relevant Lines:
1142

💛  - Coveralls

Looks good, however, only thing remaining is send logout to keycloak if network available so that refresh toke expires https://stackoverflow.com/questions/46689034/logout-user-via-keycloak-rest-api-doesnt-work. In case network if not available may be just logout of device @ndegwamartin


Remove non-active profiles

Some of the profiles in the list are 404 links.
A script in travis (https://travis-ci.org/) using https://github.com/dkhamsing/awesome_bot can be used to check for 404 links.
I can work on this.

On Wed, 2 Oct 2019, 19:14 Swati Garg<EMAIL_ADDRESS>wrote:

Some of the profiles in the list are 404 links.
A script in travis (https://travis-ci.org/) using
https://github.com/dkhamsing/awesome_bot can be used to check for 404
links.
I can work on this.

Sure.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tapaswenipathak/Women-GitHubers/issues/149?email_source=notifications&email_token=AA7TVIUNL7DPVCH5BWIWJTDQMSQS7A5CNFSM4I4WRCOKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HPEINUQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA7TVITS7F6GMG6ZVCBUZLLQMSQS7ANCNFSM4I4WRCOA
.


BIGTOP-3725. Puppet 3 is removed from EPEL for CentOS 7.

Description of PR
Puppet RPM for CentOS 7 provided in EPEL was apparently removed. This PR is a workaround for it.
https://issues.apache.org/jira/browse/BIGTOP-3725
How was this patch tested?
I locally ran ./build.sh trunk-centos-7 in docker/bigtop-puppet and then docker/bigtop-slaves, and confirmed both succeeded.
For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'BIGTOP-3638. Your PR title ...')?
[x] Make sure that newly added files do not have any licensing issues. When in doubt refer to https://www.apache.org/licenses/

+1，
Successfully ran ./build.sh  trunk-centos-7 in docker/bigtop-puppet and  docker/bigtop-slaves on Arm64 too.

Thanks for the review, @iwasakims and @guyuqi!


Fixes 'google-services.json is missing' error

Resolves #3

Thanks!
I can't reproduce the issue, but the app still works after removing apply plugin: 'com.google.gms.google-services' from android/build.gradle. So, I think removing it will help some people prevent facing this issue.
I don't want to remove react-native-system-notification dependency from this module, because I plan to use this module to create notifications. It more focuses on creating notification, and react-native-gcm-android focuses on GCM. Although it has some issue so I don't use it, let it stay here now.
Can you add a commit not to remove react-native-system-notification in this PR? And I will merge it.

Yeah I was thinking about how our app would generate notifications while its not running and doing it via the background service in your module would be great :). Restored the dependency.

Currently this module support to create notification when the app is not running(closed).
See this
When the app is closed and receive GCM notification, it will create BackgroundService to launch a React Native instance to handle notification. After finishing, BackgroundService will be destroyed.

@oney Can you create a new release for NPM after the commit 8 days ago? ^

@fender No problem. Done in 0.1.6


Cinnamon updates 2022-08-15

Description of changes
Previous one: https://github.com/NixOS/nixpkgs/pull/185864
Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

cinnamon.cinnamon-common: 5.4.9 → 5.4.10

[ ] live previews: Use clones when valid, and static images in certain
[ ] windowAttentionHandler: Fix new window focus issue with Firefox.
[ ] keybindings.js: Use a js Map to track keybindings and handle
[ ] osdWindow.js: Use correct allocation size for the fill level instead
[ ] Remove rtl workaround for the triangle arrow direction, (#10980)
[ ] windowAttentionHandler: remove notification fallback, re-add all
[ ] windowManager.js: get rid of (non-cinnamon) popup menu animations.
[ ]<EMAIL_ADDRESS>Fix panel scrolling behavior.
[ ] windowManager.js: Complete the workspace switch immediately if
[ ] panel.js: Don't create a (horizontal) panel barrier for a vertical
[ ] panel.js: No barriers when there is only a single monitor.
[ ] panel.js: global.screen -> global.display
[ ] More issue templates, not everything is a bug report (#11011)
[ ] Fix bug remplate, remove question template.
[ ] Remove unused soup (#11002)

Files: meson.build

[ ] 5.4.10

Tagged: 5.4.10
Files: meson.build

[ ] keybindings.js: Use bindings.get() - this.bindings is a Map.
[ ] Re-add soup 2.4 bindings as a runtime-only dependency, and add
[ ] Reimplement the locate pointer functionality
[ ] cs_sound.py: Add some more sound ids to ignore.
[ ] keybindings.js: Fix incorrect check.

Tagged: master.lmde5 master.mint21

cinnamon.nemo: 5.4.2 → 5.4.3

[ ] fix spelling error spotted by lintian
[ ] App chooser: Quote custom executable file paths (#3041)
[ ] 5.4.3

Tagged: 5.4.3 master.lmde5 master.mint21
Files: meson.build

cinnamon.xreader: 3.4.3 → 3.4.4

[ ] ev-window.c: Don't try to handle keyboard events manually.
[ ] 3.4.4

Tagged: 3.4.4 master.lmde5
Files: meson.build

sticky: 1.11 → 1.12

[ ] buffer, do_insert_text: always reassign location text iter to former pos
[ ] 1.12

Tagged: 1.12


Issues with peer dependencies found

Dependents using this library face warnings which are erroneous in the context of a development workflow. Here's an example of the warnings generated (outlined with box):

I believe this can be addressed by adding peerDependenciesMeta and setting "optional": true. See note here.

adding build-esm breaks my svlete-kit, getting strange errors of imports not found, at least in dev...
Without it runs fine.

@ar4hc Good to know and probably part of the reason NPM has the manifest property I added in #77, which should squelch the warning if you want to run against a fork while we wait for the maintainer to version the package. Be good to get some feedback too on the pull.

I get errors like this with npm when installing nightwind with sveltekit

I get errors like this with npm when installing nightwind with sveltekit

This nightwind? https://github.com/jjranalli/nightwind

After upgrading to PNPM 7 I'm no longer receiving the warnings.

Oops. Closed in error. Updated OP to add a note on how to squelch the errors.


OutputInfo::line_size should be a method

As of v0.17.14, the OutputInfo struct has a pub field line_size that seems to be computed entirely from other fields - namely width, height and bit depth.
Since the field is public, it is possible for the API user to mutate it and put the whole OutputInfo in an inconsistent state where the values of the fields end up conflicting each other.
It would be nice to turn one of these fields into a method that computes data from the other values, so that it's no longer possible to create structs with conflicting values.

Also, FrameInfo seems to be a better name for it than OutputInfo, and we might want to change it while we're at it.

The OutputInfo object is only returned from next_frame so it seems harmless to have all public fields. Though it is a bit awkward that it gets returned at the same time as the frame data, even though you have to pass in a properly sized &mut [u8]  to the function in the first place


Logic cloning2

Initial PR. Logic cloning is still disabled for the following reasons:

All the ORFS tests don't seem to trigger any cloning operations
For a synthetic testcase, the results from cloning are slightly worse

It is possible that logic cloning is a redundant transform which won't add much value when we have

Buffer insertion
Upsize
Load splitting (which is very similar to logic cloning)
Fanout removal (which sort of makes logic cloning irrelevant)

It is also possible that a we need to try a different order of applying these transforms or apply multiple transforms to check which one is best instead of applying them in a specific order and picking the first "winner" (transform that makes an improvement in timing).

Are you trying to request a review?

@openroadie This might be a case where an integration test isn't as good a fit. @cdleary and I created a C++ unit testing framework that would probably be helpful here.
See examples

https://github.com/The-OpenROAD-Project/OpenROAD/blob/master/src/cts/test/cts_unittest.cc
https://github.com/The-OpenROAD-Project/OpenROAD/blob/master/src/odb/test/cpp/TestDbWire.cc

case where an integration test isn't as good a fit. @cdleary and I created a C++ unit testing framework that would probably be helpful here.

Thanks. I will take a look. Now that we have a collection of transforms (and I still need to do the buffer chain -> inverter chain transform).... it will become an interesting exercise to figure out exactly how to apply these various transforms (and in which order) to get the best results. Might have to use some kind of ML model where we supply it the topology with delays/drive strengths/parasitics etc... and we get a optimized sub-circuit back.  I do not think there are too many different configurations of gates between flops that we need to do all this incremental computation for every net (esp. during the stage where they are not detailed placed).

@maliberty and @openroadie it looks like all of the requested changes have been completed, is this ready.


[IOTDB-2074] Fix NullPointerException when recovering compaction in MacOS

Coverage decreased (-0.1%) to 67.303% when pulling 7dab04b353cee15e932241efb75ba7c72855151a on choubenson:fixCompactionBug into 99f06aaa9a6438e5ec3311fc6ac7e4f3ef192c4f on apache:master.


[1908] Only rollover active courses and providers

Context
Changing the rollover script so that it no longer rolls over courses which weren't published last cycle. Only courses which have the status withdrawn or published will be rolled over. Accredited bodies, which accredit courses will always be rolled over even if they have no courses.
Changes proposed in this pull request

Add a rollable? method which encompasses content_status logic.
We don't rollover courses unless they are rollable?.
We don't rollover providers unless they are rollable?.
Remove failing MCB test as this is now redundant (all of MCB can now be removed).

Guidance to review

Run  bundle exec rake rollover:create_recruitment_cycle"[YYYY, "YYYY-MM-DD", "YYYY-MM-DD"]. This is year, application_start_date and application_end_date respectively.

Ensure you have providers, locations and courses in your database.

In Publish, change can_edit_current_and_next_cycles in development.local.yml to true.

Navigate to a provider organisations/{provider_code} check that you can click on Current cycle but not Next cycle.

Look for a rollable? provider, e.g one with published or withdrawn courses.

Run bundle exec rake rollover:providers"[{provider_code}]"  and check that the provider is successfully rolled over.

Look for a non rollable? provider, e.g one that doesn't accredit courses, or have courses, or only has courses that are draft or rolled_over.

Run bundle exec rake rollover:providers"[{provider_code}]" and check that the provider is not rolled over.

You can rollover all providers, however there is currently an ongoing issue with email validation which will cause issues. See this trello ticket. You can fix the emails manually (which are in the trello ticket) and run bundle exec rake rollover:providers. This will take around 20 minutes.

Checklist

[ ] Make sure all information from the Trello card is in here
[ ] Attach to Trello card
[ ] Rebased master
[ ] Cleaned commit history
[ ] Tested by running locally

 [L] Only rollover active courses and providers


Version Kubernetes Tentacle Chart

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
<EMAIL_ADDRESS>Patch Changes

fbc9a76: Add support for changeset versioning
3704cc2: Allow Tentacle service account to interact with config maps

I manually updated the PR to fix the Chart.yaml version and update the workflows


The master edition don't support cocos2dx-3.6

Can u support old edition for 3.6?
CCArmatureDisplay.h
/**
* Modify for cocos2dx 3.7, 3.8, 3.9
*/
cocos2d::PolygonInfo& getPolygonInfoModify();

Mesh is based on the cocos2d::PolygonInfo and cocos2dx-3.6 no cocos2d::PolygonInfo, so the lowest version can only support up to cocos2dx-3.7.

did u have edition support cocos2dx-3.6 or 3.x?


Increase data stored in the url

We store some data in the url (e.g., image position, selected analysis task).  It would be good to add frame selection, viewed annotations, task options that aren't the default, etc. so that a url could better recreate the state of the viewer.
There could be enough options that this would exceed the sensible browser url size (although this varies by browser, 2k is the same limit).  Perhaps we should save this state to a database collection and have a reference to it (maybe when a sharable link is asked for?).

If we decide to look at using a database then there is the consideration of server side vs. client side.  That is, if the goal is along the lines of allowing a client to restart where they left off, instead of a server-side database to interpret the user's URL, we could have a client-side cookie (or cookies) to tell the server the current state.  Or some combination where the cookies would give the server some context for interpreting a URL that specified only some options.
This approach wouldn't allow a user to easily share state from one client computer to another client computer, so if that's a desired outcome then never mind.

I think sharing is a key component to this.  You want to be able to share a link with a colleague.

So agreed sharing is the key---  would it be possible to use a zipped /
compressed version of the query string/URL string which would be smaller ?
On Tue, Apr 25, 2023 at 10:00 AM David Manthey @.***>
wrote:

I think sharing is a key component to this. You want to be able to share a
link with a colleague.
—
Reply to this email directly, view it on GitHub
https://github.com/DigitalSlideArchive/HistomicsUI/issues/299#issuecomment-1521842453,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFODTRSI7DJINS25XKQVULXC7KINANCNFSM6AAAAAAXLAYM6Y
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
David A Gutman, M.D. Ph.D.
Associate Professor of Neurology
Emory University School of Medicine

would it be possible to use a zipped / compressed version of the query string/URL string

Maybe -- we do this in some other instances (geojs editable tutorials, for instance), and it works up to a point.


Freeze when clicking on autocompletion suggestions in iPython console

From<EMAIL_ADDRESS>on 2014-11-03T03:42:18Z
Hello everyone, I experience the following problem on python 3.3.5, using Spyder 2.3.1 with rope py3k 0.9.4, and iPython 2.3.0 (also tried on 2.2.0) under Windows 7.

Type statement in iPython console
Press tab to get autocompletion suggestions
Mouse click on a given suggestion.

This will cause Spyder to hang for 5-10 seconds, before resuming normal operation. Autocompletion doesn't happen. Everything works fine if I navigate in the suggestions with the keyboard arrows and validate with the return key.
Click to complete also works fine in the code editor. Thank for having a look if you can reproduce it.
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=2038

From ccordoba12 on 2014-11-18T17:57:48Z
Status: Duplicate
Labels: -MS-v2.3.3
Mergedinto: 1908

From ccordoba12 on 2014-11-03T16:06:57Z
Thanks for the report. We'll see what we can do about it.
Labels: -Priority-Medium -Cat-CodeCompletion Priority-High Cat-IPythonConsole MS-v2.3.3


duck player page

Current dependencies on/for this PR:

main

PR #412

PR #418

PR #421   👈
PR #420

PR #417

PR #419
PR #414

This comment was auto-generated by Graphite.