Added Blocks type for Unmarshalling

Currently there is a problem with unmarshalling into a Block interface, since the decodeBlock function is unexported. This is an issue when trying to use the Block type outside of the API, such as loading a Block from a JSON file. A Block itself cannot be defined to unmarshal into, as it is an interface and can't be a receiver, but a []Block can be, as done here.
[]Block cannot be unmarshalled into as it is an interface. This defines a Blocks type, which is just a []Block, and an UnmarshallJSON method so that a JSON string/byte slice can unmarshall into a []Block.

This type can be used in the other requests as well (and defined as part of the request/response structs) to also use this unmarshalling code.

Go 1.14 doesn't have os.ReadFile I guess. Will update that momentarily.

Ahh, it used to be just ioutil.ReadFile

The problem this is trying to resolve is loading block arrays from JSON strings/files. At the moment this will cause the same error as the Property arrays. The main reason for this is that decodeBlock is unexported, so I'm not able to use that outside of the package.
This does not solve single block unmarshalling though. A way to possibly solve this is by having the Block interface also implement the json.Unmarshaler interface: https://pkg.go.dev/encoding/json#Unmarshaler. This would also solve the array problem and technically make this redundant, but it would require that each block type struct implement UnmarshalJSON so I'm not sure if that's the best idea.


Evaluation on broom and curl dataset

I really appreciate to your great work!!
And I have a question though.
I think there are no multi-view image for evaluation on broom and curl scene dataset.
Could you let me know how to evaluate it?
I guess that the only way to evaluate it is creating validation dataset from original nerfies dataset or loading the original one using their data format.
Am I right or do we have some other ways?
If you give me the answer, it would be really helpful!! :)
thank you!

Hi for broom and curl, it comes from https://nerfies.github.io/, where the images are capture from stereo cameras, but in our repo we didn't provide all the images for evaluation.


Add well known PortalTarget class and examples

Adds PortalTarget (as discussed) as a well known class that can be used to globally customize the default portal target used by the portal action.
I also:

Added examples of the different target approaches (see screenshot below)
Changed the portal logic to put the portal back in its original parent if it becomes disabled (rather than doing nothing)
I expect this was just an oversight so far. If a portal is initially disabled, it just stays in its original parent, so it seems to make sense to consider that its "disabled state". And if a user doesn't want the portal to move, they just shouldn't change the options.
I primarily made the change, because it meant that I needed less code for the examples, but I think that it's the intuitive behaviour.

Thanks @myieye!


http component not loading

Home Assistant release (hass --version):
0.31.0
Python release (python3 --version):
3.4.2
Component/platform:
http with ssl
Description of problem:
Not able to get http frontend to load.
Oct 23 15:43:52 automation hass[807]: INFO:homeassistant.core:Bus:Handling <Event call_service[L]: domain=persistent_notification, service_data=title=Invalid config, message=The following platforms contain invalid configuration:  http  (please check your configuration), notification_id=invalid_config, service=create, service_call_id=1977835472-1>

Oct 23 15:43:52 automation hass[807]: ERROR:homeassistant.bootstrap:The following platforms contain invalid configuration:  http  (please check your configuration)not a file for dictionary value @ data['http']['ssl_certificate']. Got '/etc/letsencrypt/live/redacted/fullchain.pem'

Oct 23 15:43:52 automation hass[807]: not a file for dictionary value @ data['http']['ssl_key']. Got '/etc/letsencrypt/live/redacted/privkey.pem'. Please check the docs at https://home-assistant.io/components/http/

Oct 23 15:43:52 automation hass[807]: ERROR:homeassistant.bootstrap:Not initializing api because not all dependencies loaded: http

Oct 23 15:43:52 automation hass[807]: ERROR:homeassistant.bootstrap:Not initializing frontend because not all dependencies loaded: api

Oct 23 15:43:52 automation hass[807]: ERROR:homeassistant.bootstrap:Not initializing logbook because not all dependencies loaded: fronted

Oct 23 15:43:52 automation hass[807]: INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: new_state=<state persistent_notification.invalid_config=The following platforms contain invalid configuration:  http  (please check your configuration); title=Invalid config @ 2016-10-23T15:43:52.878321-04:00>, entity_id=persistent_notification.invalid_config, old_state=None>

Expected:
Problem-relevant configuration.yaml entries and steps to reproduce:
http:
  ssl_certificate: '/etc/letsencrypt/live/redacted/fullchain.pem'
  ssl_key: '/etc/letsencrypt/live/redacted/privkey.pem'

Traceback (if applicable):

Additional info:
I don't know if this is related to the new version or not, because I just implemented this.  I was having issues getting LetsEncrypt to work and figured that I would try a possible solution (https://community.home-assistant.io/t/ssl-config-error/5173/2) another user has suggested.  I updated to 0.31 and all was well.  Stopped HASS, installed python3-openssl, installed LetsEncrypt, added the new configuration lines, and nothing... Well nothing except errors shown above!

Are you sure your files exist and is readable by the user you use for hass?

Ouch that hurts my pride.  chown'ing the files was the first thing that I did and took for granted that it worked as expected.  They are symlinks and it didn't nothing to the actual directory or files!  Thanks for making me rethink what I had done!
The errors are gone, but I can't get to either my http or https internally or externally.  I'm going to close this... Thanks!


dependency not implemented in each generation

I am using the blueprint_example template, and there is the following chunk of code:
Parameter(
name="cutoff_time",
param_range=[0.01, 1.0],
constraints={"low": 0.01, "high": 1.0},
number_points=2,
distribution="uniform",
param_type="continuous",
depends_on={"name": "coherence_time", "function": linear_dep},
# todo: test if this dependency is also used in each generation
),
it seems that the dependency is not implemented in each generation, but the parameter value for cutoff_time goes way beyond the limit set by the dependency.

Hey there :) Thanks for bringing this up!
That is indeed very much possible, as it seems that there are also no proper unittests implemented for this currently.
Is this a feature that you need or would like to see implemented? Then I can fix it for you :)

Thinking about this a bit: Can you briefly describe the use-case you have for this and why the dependency is necessary?
There are a few choices in where to implement this precisely and it would be helpful to learn a bit about how this is intended to be used.

@SouPhyzics any input on this? Is this a feature you would like to see implemented? If yes, can you describe your use-case a little bit, so I can understand at which point of the code this should be done.
I would be especially curious to hear your input on why this should be done on each generation of the optimization.
Is the use case that you have multiple parameters (x,y,z), where z =F(y) depends on y and you optimize over only (x,y) and then want to update z to the set of (x,y) that come out of every generation?

Hi @dmark04 , apologies for the late response, I was away at a conference followed by a leave.
Thanks for checking this out. Yes, the dependency us something I want to implement in my optimization.
I am using YOTSE for optimizing different parameters for quantum teleportation over a repeater chain, where the cutoff_time is a tunable parameter (it does not contribute to the hardware cost), but have significant effect on the fidelity and rate of teleportation over the repeater chain. I want the cutoff_time to be dependent on the coherence time, such that cutoff_time / coherence_time \in [0.01, 1]. For an updated point in a new generation, both the coherence time and efficiency of elementary link entanglement generation are updated, so I also want this dependency for the cutoff time to be updated over every generation. This is exactly the same as you explained in your example with (x, y, z).
Looking forward to your response. Cheers,
Soubhadra

Hello @dmark04 , is there any update regarding this? Thanks.

Hey @SouPhyzics , this time I was on leave :)
I think the use-case is now clear to me! I will try and implement this as soon as possible.

Hi @dmark04, that sounds good.
Do you have a timeline in mind when it will be done?
Also, I am having trouble setting the hyperparameters, i.e. I am unable to understand a clever estimate or guess for the hyperparameters. Could you or someone please provide any suggestions regarding this? Thanks.

Hi there @dmark04, I think it's best if we have a zoom call to clarify this. Does sometime on Friday (26 Apr) or next week (29 Apr - 3 May) work for you?


[Extensibility Enhancement] Expose InLine Parameter in Codeunit 8904 "Email Message" - AddAttachment()

We need to be able to specify the Content-Disposition property of email attachments. I suppose the InLine Property does just that, but is not exposed.
So the proposal is to add this procedure in EmailMessage.Codeunit.al
procedure AddAttachment(AttachmentName: Text[250]; ContentType: Text[250]; InLine: Boolean; AttachmentInStream: InStream)
begin
    EmailMessageImpl.AddAttachment(AttachmentName, ContentType, InLine, AttachmentInStream);
end;

and the implementation in EmailMessageImpl.Codeunit.al like this:
procedure AddAttachment(AttachmentName: Text[250]; ContentType: Text[250]; InLine: Boolean; AttachmentInStream: InStream)
begin
    AddAttachmentInternal(AttachmentName, ContentType, InLine, AttachmentInStream);
end;

procedure AddAttachmentInternal(AttachmentName: Text[250]; ContentType: Text[250]; InLine: Boolean; AttachmentInStream: InStream) Size: Integer
var
    EmailMessageAttachment: Record "Email Message Attachment";
    NullGuid: Guid;
begin
    AddAttachment(AttachmentName, ContentType, InLine, NullGuid, EmailMessageAttachment);
    InsertAttachment(EmailMessageAttachment, AttachmentInStream, '');
    exit(EmailMessageAttachment.Length);
end;

(or refactor the implementation and avoid code duplication just because of the InLine Parameter).
Thanks!

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 10591.

Availability update: We will publish a fix for this issue in the next update for release 22.
Build ID to track: 56284.


Add Existing Cluster fails with blank page

When adding an existing cluster, this allows you to select cluster type, and then subscription, however the following page is blank:

We've been unable to add any clusters to this plugin for some time now. What causes this?

Hi @JackSinclairT, thanks for opening this issue. I tried and it's working fine for me. Could you give us more infos about your environment? Extension version installed? Vscode version? Os?
Then, when you see this blank page, if you execute Developer: Open Webview Developer Tools in the command palette, do you see any error/log in the console tab?
Thank you and sorry for the trouble.

I see the following on click of the final 'next' button before getting the blank screen

Thank you @JackSinclairT we'll look into it.
@itowlson @bacongobbler could you please try to replicate it?
I found an error but it is different from the one reported here Uncaught Error: Could not resolve webview id. Webview will not work. This is usually caused by incorrectly trying to navigate in a webview. Investigating on it.

When adding an existing cluster, this allows you to select cluster type, and then subscription, however the following page is blank:
We've been unable to add any clusters to this plugin for some time now. What causes this?

I'm having the same experience. Any tips to mitigate this issue? @itowlson

Maybe you are lack of this extension? https://marketplace.visualstudio.com/items?itemName=ms-kubernetes-tools.vscode-aks-tools. Install it and do the login, then right click on the cluster to merge the config.

Hope this helps.

Sa

This seems to be a long running issue and I've definitely had this plugin working after Nov 2021 when it was first reported, however I've gone to add a new cluster from Azure and I'm experiencing this blank page.
@lstocchi Here's my web view console error:

I've tried restarting VSCode and my machine but to no avail.

same issue on my end with the exact same error

I'm seeing this same issue. I was able to follow the instructions suggested by @gsxmax and add the Azure Kubernetes Service extension, click the second AKS cluster, and merge into my config. Once that was done the new cluster appeared in the Kubernetes extension cluster list.


How to always keep sidebar opened, and hide with a key press?

I've set everything up, and works fine. Now, I want to Hide the sidebar (f1 key right now). If I press to hide it, it will hide, then the top navbar will appear. If I press again f1, it will hide the top navbar, and the sidebar now has to be hovered to be shown...
https://github.com/KiKaraage/ArcWTF/assets/62475718/fbb4ea2e-de7c-483f-b3a5-6dab51aa6cf2

I'm curious why did you implement userchrome toggle instead of leaving the native toggle of the navbar..

Solution: Set keyboard shortcut for Userchrome Toggle instead of Sidebery.
If you want to use F1 for toggling the sidebar, you have to assign another shortcut first for Sidebery (Go to about:addons, click the gear icon in top right corner, choose Manage Extensions Shortcuts, scroll to Sidebery, assign other key. I use F3)
And then, you can assign F1 for Userchrome Toggle
So, when toggling the Userchrome Toggle button, you can switch between hidden sidebar (that can be hovered to show sidebar fully, temporary) and static sidebar

Why did you implement userchrome toggle instead of leaving the native toggle of the navbar?

I use Userchrome Toggle because by using it I can make the sidebar autohidden (and shown when hovered), like how it works on Arc.
Otherwise if I only use native sidebar button, the sidebar state would only be "hidden permanently" or "shown permanently"

I see. Thanks for the help, I might work for a workaround to only have the sidebar, without Userchrome Toggle, because personally, i don't use that show on hover feature.

I see. Thanks for the help, I might work for a workaround to only have the sidebar, without Userchrome Toggle, because personally, i don't use that show on hover feature.

I'd also be interested in this, since I prefer to work with a keyboard.

I see. Thanks for the help, I might work for a workaround to only have the sidebar, without Userchrome Toggle, because personally, i don't use that show on hover feature.

I'd also be interested in this, since I prefer to work with a keyboard.

Check this out:
https://github.com/LupuC/FlowUI_firefox

Check this out: https://github.com/LupuC/FlowUI_firefox

Would love to see some screenshots!

Check this out: https://github.com/LupuC/FlowUI_firefox

Would love to see some screenshots!

Check the repo again ;)


remove cache options

mypy is already called with --no-incremental which disables the cache. I simply added the corresponding flag for pytest, to remove this flag.

mypy is already called with --no-incremental which disables the cache. I simply added the corresponding flag for pytest, to remove this flag.

I don't think it is called with --no-incremental when you run locally.  So I think this option should be kept.

mypy --help says:

--no-incremental          Disable module cache (inverse: --incremental)

So I assume that is effectively the same as deleting the cache (but it it less code on our side to achieve it)

mypy --help says:

--no-incremental          Disable module cache (inverse: --incremental)

So I assume that is effectively the same as deleting the cache (but it it less code on our side to achieve it)

Yes, but I don't see that we are running with --no-incremental by default??

That seems to be the case on main:
https://github.com/pandas-dev/pandas-stubs/blob/9072b1596e5364268648899a7adaf021a8d7e8c2/scripts/test/run.py#L7

Ah, good.  So you're right that we don't need the option!


Add process subcommand to CLI

Add commands to start/stop individual processes, ex. bin/cli.sh process start --master
Define process interface and registry

process specific java opts are defined with the process and are dynamically added to env

Add journal format command as part of starting master process
Mount options for worker are not ported because they will be deprecated in the near future

there's an interesting situation with process and flags. by following the convention of bin/cli.sh <service> <operation> <flags and/or args>, a start command must follow the format bin/cli.sh process start --master (as a flag) or bin/cil.sh process start master (as an argument). process operations could also have their own specific flags. for example, adding a -i flag to the master start command specifies it to restore the journal from the backup file.
in the code, flags must be defined as part of the command (ie. start operation is the command) and arguments are parsed after the flags are read. this means it is not possible to define the the -i flag only for the master process and it must be set as part of the start command with all the other process name flags and any process specific flags. this is the current state of the command:
$ bin/cli.sh process start -h
Start the process

Usage:
   process start [flags]

Flags:
  -h, --help                         help for start
      --job_master                   Master process
      --job_worker                   Worker process
      --journal-backup-file string   Path to journal backup file to restore the master from
      --master                       Master process
      --proxy                        Proxy process
  -N, --skipKillOnStart              Avoid killing previous running processes when starting
  -a, --startAsync                   Asynchronously start processes without monitoring for start completion
      --worker                       Worker process

Global Flags:
      --debugLog   True to enable debug logging

to add to the confusion of flags, if there is a similar flag for two distinct processes, (ie. format for worker and format for master), the flag names and abbreviations must always be unambiguous, so if -f is used for format master, it cannot be used for format worker. the code can get very messed up if there are overlapping flags registered for multiple purposes.
this is the best option given the current guidelines. here are some alternative options/examples:

current: bin/cli.sh process start --master -i /path/to/backup
bin/cli.sh process start master -i /path/to/backup: break the convention of bin/cli.sh <service> <operation> and add a third tier such that the processName is a command so process specific flags can be added cleanly
bin/cli.sh process master --start -i /path/to/backup: switch the order of operation and process name. however, this mixes operation specific flags (ie. if there are both stop and start flags) and has the same flag overlap problem as the current approach.

thoughts/opinions? @jenoudet @jingwenouyang

@Xenorith I like option 3. the best semantically. To manage the conflicting / differing flags, it's best to load the options into a custom struct and use https://github.com/go-playground/validator to define rules to validate the input we're given. Options 3. works well with the tool I have outlined above. It is also the most user friendly as only the relevant flags are offered up to the user when selecting a specific process.

@Xenorith I like option 3. the best semantically. To manage the conflicting / differing flags, it's best to load the options into a custom struct and use https://github.com/go-playground/validator to define rules to validate the input we're given. Options 3. works well with the tool I have outlined above. It is also the most user friendly as only the relevant flags are offered up to the user when selecting a specific process.

taking your earlier comment into account, it would look cleaner to add a --type style flag for the operation type for option 3, to end up looking like bin/cli.sh process master --op start <additional flags>, but the flags for different operations will still show up together. for example, async flag for start and soft kill flag for stop will both appear under bin/cli.sh process master; one could mistaken the async flag to be applicable to stop, especially if it's labeled as only --async without the stop/start descriptor.

but the flags for different operations will still show up together.

Given the above correct observation and taking inspiration from the docker container cli, I think it is best to go with option 2.. This, in fact, does not break the convention as we have bin/cli.sh <command> <subcommand> [value].  where [value] is one of {master | worker | job_worker | job_master | proxy}.
This allows simpler commands like bin/cli process start master --async and bin/cli process stop worker --soft while retaining the convention. We can then validate the input using the validator library I linked above (for example, bin/cli process start master -i /path/to/backup works, but bin/cli process start worker -i /path/to/backup does not. in this specific example it -i flag can be safely ignored but in cases where there are conflicts we can return at error to the user).

but the flags for different operations will still show up together.

Given the above correct observation and taking inspiration from the docker container cli, I think it is best to go with option 2.. This, in fact, does not break the convention as we have bin/cli.sh <command> <subcommand> [value]. where [value] is one of {master | worker | job_worker | job_master | proxy}. This allows simpler commands like bin/cli process start master --async and bin/cli process stop worker --soft while retaining the convention. We can then validate the input using the validator library I linked above (for example, bin/cli process start master -i /path/to/backup works, but bin/cli process start worker -i /path/to/backup does not. in this specific example it -i flag can be safely ignored but in cases where there are conflicts we can return at error to the user).

this looks good for me, and not too cumbersome. #3 with too many flags, it can get tedious / confusing i feel.

alluxio-bot, merge this please


[ENG-6693] Add new tests for preprint moderation states

Purpose
Add new tests for preprint moderation states
Changes
QA Notes
Documentation
Side Effects
Ticket
https://openscience.atlassian.net/browse/ENG-6693?atlOrigin=eyJpIjoiOTBhN2U1MTg5M2U0NGI1YjgxNGRkZTYwYTUzYTMxOWYiLCJwIjoiaiJ9

Overall looks good, the only suggestion is to add more checks for the “submit” and “accept” tests
An example of a test flow:

Create a preprint
submit/accept
Check guid.referent, is_published, etc.
Create a second version
submit/accept
Check guid.referent, is_published, etc. for the second version


Support share JSON

Add a function or adapt convertCatalog to accept and convert share JSON. We will need to embed this in Terria for any app we re-release on TerriaJS version 8 to support current share links.

I will be posting progression updates in Model architecture: Share & story migration

almost done
Action: @nf-s need to write tests on catalogue converter side
done with stories as well


[EM] Python wrapper for the ExtMemQuantileDMatrix.

Not exposed to the document yet.

Add C API.
Add Python API.
Basic CPU tests.

The initial implementation of GPU-based batch training is getting close to being finished now. ;-)

cc @rongou .


notebook: Add notebook estimate V100 GPU-days for cyclic adversary

Add notebook that parsers the cyclic adversary's victimplay logs to estimate that the cyclic adversary used 2,220 V100 GPU-days of training for victimplay (training GPU not included)

Remember to rename from iclr2022 before merging!

Rerequesting review because I made several large changes:

Previously I was only looking at the victimplay GPU usage. I've added the train worker's GPU usage (not counting the time where the train worker is idling and waiting for more rows). The new V100 GPU-days estimate for the cyclic adversary is 2,223 days
Refactored things into functions so that we can get the passing adversary's training compute (3.07 V100 GPU-days)
Added a plot of GPU-days vs. win rate for the cyclic-adversary.

The last few points of the plot are:
            adv_win     gpu_days
adv_steps
434127104  0.000000   634.901149
445174528  0.000000   656.277141
455012352  0.000000   674.590325
464995584  0.120000   693.807642
474976512  0.145833   712.869404
484961536  0.400000   731.345387
494657792  0.645833   749.644650
504708864  0.750000   781.309203
515616512  0.833333   832.093124
525883904  0.875000   931.111608
535865088  0.940000  1206.192888
545065216  0.957224  2223.228956
545993728  0.960000  2883.143384

Added plots of GPU-days vs. adversary training steps now (to replace the plots of FLOPs vs. adversary training steps in our paper draft)

Will take some time to read through the code closer later today. But I was wondering if we could also add the checkpoint switching lines to the win-rate vs compute plot? I'm thinking the lines will spread out towards the end which would be a nice effect to show off clearly.

good suggestion, added

Oops, I underestimated the pass adversary GPU-days by a factor of 7 (20.4 V100 GPU-days vs. 3.06 V100 GPU-days) because I forgot that the pass-adversary was run with a single victimplay worker with 7 GPUs rather than 7 victimplay workers with 1 GPU.
Updating paper draft now

@tomtseng are you still waiting on a review for this, or is it blocked for some other reason?


Subscription is triggering even after the delete function throws error.

Hello!
I have a collection named vendors. Whenever I delete a specific vendor it shows me an error.
⛔ Vendor deletion: ClientException: {url: http://<IP_ADDRESS>:8090/api/collections/vendors/records/jc62n0vfhxe3kfq, isAbort: false, statusCode: 400, response: {code: 400, message: Failed to delete record. Make sure that the record is not part of a required relation reference., data: {}}, originalError: null}
I've no problem with this error. But as my delete function throws an error means.... the record isn't deleted. So why should my subscription of the vendor trigger an event?
💡 Stream {"action":"delete","record":{"id":"jc62n0vfhxe3kfq","created":"2023-06-14 13:36:31.682Z","updated":"2023-06-14 13:36:31.682Z","collectionId":"t3si1vfrp0ooi0f","collectionName":"vendors","expand":{},"address":"Lorem Ipsu ","creator":"hcgrqqn1zdsm3wf","description":"Lorem Ipsum","email":"a@vendor.com","name":"A Vendor","phone":"01234567890","updator":""}}
Here is the screenshot of my terminal

If anyone knows how to stop this unusual trigger or possible mistakes I've done. please let me know. Thank you.

This is already fixed in the develop branch.
The reason for the above error is because in the current version we do "optimistic delete" and don't await the actual record delete operation to complete successfully to send the realtime message. In the develop branch there is a check that prepares the record delete event but sends it only if the OnModelAfterDelete get triggered.

@ganigeorgiev I think this issue hasn't been solved in version 0.16.7. I have just updated it from 0.16.6 to 0.16.7. But still facing the issue. Can you please check it out?
Thank you.

@sabikrahat Yes, the above mentioned changes are not part of v0.16.7 as they are currently only in the develop branch. The issue will  be resolved with the PocketBase v0.17.0 (there are no fixed ETAs yet).

Oh okay... Thank you for your quick response.


InertionSort

Please grant your approval if you are satisfied with the modifications and include the "hacktoberfest-accepted" label.

https://user-images.githubusercontent.com/43691873/135965000-a3019b12-c089-4a61-bae3-81f915ec39a5.png
Pls read the readme file again. Your PR will be excluded by system. Pls submit genuine PR.


Cannot read property 'HTML_STRING' of undefined

I am currently trying to use html-keyboard-response plugin, and I get an error: Uncaught TypeError: Cannot read property 'HTML_STRING' of undefined on line 21.
Any ideas about a solution?

Are you loading the jspsych.js library before loading the plugin? Are you using the latest version of jspsych.js with the plugin?


question: where is the src for android app?

oh, i have found the answer https://protonmail.com/blog/ios-open-source/


Revert "feat(apps/prod/tekton/configs/pvcs): add global crate index mirror"

Reverts PingCAP-QE/ee-ops#1140
Caused by:
  File exists (os error 17)
+ r=101
+ set +x
make[2]: *** [Makefile:459: x-build-dist] Error 101
make[2]: Leaving directory '/workspace/source/tikv'
make[1]: *** [Makefile:270: build_dist_release] Error 2
make[1]: Leaving directory '/workspace/source/tikv'
make: *** [Makefile:259: dist_release] Error 2

/approve


Add improvements on import errors and update library version

There are 2 PRs that can easily improve library usability: #12 and #13
Also, the package on pypi doesn't contain fixes from master.
@apmorton Please take a look.

Hello,
Thanks for your interest in this library, and sorry for the lack of maintenance on my end with regards to PRs and updates to pypi.
In any case, which PR would you like me to merge? #12 would conflict with the changes you make in #13
IMO, #13 is not strictly an improvement if the proper ImportError is thrown, which was fixed by @NZSmartie some time ago, but as you mentioned never got published to pypi.
Unless you want to send in another PR I will merge #12, close #13, and bump the version on pypi.
I will wait till I hear back from you in any case.
Thanks,
Austin

I have updated #13 so that it combines both.
Thank you for quick response!
Hope you can merge this now.

@apmorton Is it better now?


Google cast stops front end loading

Home Assistant release with the issue:

0.75.2
Last working Home Assistant release (if known):
Fresh installation
Operating environment (Hass.io/Docker/Windows/etc.):

hass.io
Component/platform:

https://www.home-assistant.io/components/cast/
Description of problem:
Fresh install using the integration page to configure google cast then restarting. Then all I get is connecting
Front end fails to load
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:

I am also running into this.
I don't know if it has to do w/ Chromecast specifically, but since upgrading to 75.2 I can no longer access the front end. I did also use the integration (on .72 I think) to set it up.

Any error log?

In the logs it looks like it's loaded correctly
I could access samba, ssh just not the frontend

Same problem here.
I installed 0.73.1 and got the same error.

A 'Same problem here' or 'I am also running to this' cannot help. We need more detail error log and/or configuration to isolate the issue. We specific asked those information in issue template.
Even you cannot find anything from home-assistant log, anything in browser console log?

I fully understand this isnt helpful.
Here my the steps I went through (I’ve now wiped my card and reinstalled resin and version 69.1)
I refreshed installed hass.io
Waiting for it to fully load up.
Linked the discovery button
Clicked google config
All my google cast devices showed up.
I restarted the service, then all I get is “connecting”
I checked the log file via samba and see no issues related to casting.
I went into the storage folder and deleted core.config.entities and rebooted via ssh, which allows me back in.
It has something to do with the google cast configure, before on lower versions it auto discovered and showed GG devices.

all I get is “connecting”
Did you saw google cast device show connecting, or the whole web page is blank, only show one line of text "connecting" ?
How did you "delete core.config.entities"? Are you delete just this file, or the whole .storage folder?

All my google device show up after hitting the config button, after hitting the restart button I refresh the web page and it sits there with the HA logo saying connecting.
I deleted the file only, via samba

Same problem for me using self-built Docker Image on Raspberry Pi 3 Raspbian Stretch host.
This does not help:
# Discover some devices automatically
discovery:
  ignore:
    - google_cast

Completely disabling "discovery" component allows HA to load but of course nothing is auto-discovered.

Also, when it fails to load, it really fails to load -- no HTTP server.  "connection refused" so the Browser console log is useless.

The plot thickens... I went back to my original configuration with the discovery component turned on and the Chromecast explicit config removed, and now it seems to be working fine!
I even restored the original .storage/core.config_entries and it still is now starting correctly.
Something else must've changed but heckifiknow
I can't seem to break it now.
So the provisional workaround is this:

Disable discovery component
restart
Force an explicit cast device
restart and verify that HA is loading
return configuration to the same as it was
restart
everything working again

Sorry what's 3: force an explicit cast device?

After disabling discovery (by removing discovery from the config) then add this:
cast:
  media_player:
    - host: <IP_ADDRESS>

My problem is I have a few groups that don't have ip addresss

Yeah, I had the same issue -- my point is that after going through the goat-rodeo I listed above, then the autodiscovery started working again and my groups are showing up.

hi i'm having the same issue again
fresh install of hassio updated to .076
added google cast from the discovery link
restart service
HA fails to load
here is the log
2018-08-18 14:18:21 WARNING (MainThread) [homeassistant.components.http] You have been advised to set http.api_password.
2018-08-18 14:18:39 ERROR (SyncWorker_5) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-08-18 14:18:46 WARNING (MainThread) [homeassistant.setup] Setup of config is taking over 10 seconds.

I solved for me,
I was blocking google dns (<IP_ADDRESS>, <IP_ADDRESS>) on my chromecast and using <IP_ADDRESS>
After changing that everything worked again

I had this fail for me too on 0.76.1 -- I did a simplified version of my prior workaround and it allowed HA to launch:

Remove "discovery" component
Restarted... Working
Add "discovery" component back
Restarted... Working

Maybe HA will fail to restart the next time... unclear at this point.
Sadly these last months I am afraid to upgrade or restart HA since there has been a show-stopper almost every release for one thing or another.


feat(engine): consume and support delay, waitForDuration, and waitForResume commands from JSONv6

Overview
As a JSONv6 protocol user author, I want to instruct the protocol to wait...

for a period of time, or
until I click resume

...before proceeding.
In the JSONv6 schema, these behaviors are accomplished by the following commands:

delay
waitForResume (see #10835)
waitForDuration (see #10835)

Acceptance criteria

[ ] ProtocolEngine has waitForResume command that matches JSONv6 schema

Implementation pauses execution until a resume action is received

[ ] ProtocolEngine has a waitForTime command that matches JSONv6 schema

Implementation pauses execution the given time elapses

[ ] Both waitForResume and waitForTime are overridden by a stop action
[ ] pause / resume actions from the client do not affect the time delay

In other words, a waitForTime always waits at least the given time
If a pause action is issued while a time delay is in progress, the protocol should remain paused once the time elapses

[ ] JSONv6 > ProtocolEngine translation layer translates delay commands into waitForResume and waitForTime

Implementation notes

waitForResume can be implemented as a rename of the ProtocolEngine's existing pause command
The waitForDuration spec above seems complicated, but it's not! Details below

waitForDuration implementation notes
The goal with waitForDuration is to preserve the existing v5.x.x behavior. Some examples of that behavior - given a waitForDuration of 30 seconds:

If, while the delay is ongoing, a user sends a pause, the delay’s internal timer still proceeds. Once the delay’s 30 seconds have passed, the protocol stays paused by the user-initiated pause; sending a resume will then resume the protocol.
If, while the delay is in progress you send a pause 10 seconds in, wait for 5 seconds and then send a resume, the protocol will delay for another 15 seconds and then proceed to the next step. So the 30 second delay always completes.

This may seem daunting, but the ProtocolEngine's existing architecture is already geared exactly towards this! If we implement waitForDuration as a simple call to await anyio.sleep() (or asyncio, whatever), I believe we'll get the spec'd behavior "for free".
If a waitForDuration is ongoing in a call to await sleep(...):

If a engine.pause() is called, the status will change to paused and the queue worker will be prevented from picking up new commands, but the currently running command will not be affected

In other words, the sleep timer will keep ticking
When the sleep timer elapses, the engine will not proceed to the next command, because the queue worker is still paused from the engine.pause()
A call to engine.resume() will unblock the queue worker, allowing the protocol to proceed

If a call to engine.resume() happens while the sleep timer is still ticking, the queue worker will also not move on, because it will still be waiting for the waitForTime command to complete

PAPIv3 concerns removed from ticket. Dropped estimate to 3, accordingly

Smoke tested a JSONv6 protocol with both waitForResume, waitForDuration, and delay (both the deprecated until resume and for duration formats):

[x] Run analyzed without actually waiting
[x] Run paused at waitForResume until another play action was issued
[x] Run waiting at waitForDuration for specified duration
[x] Both could be cancelled via a stop action


Consider using ghc-lib

Today this was announced: https://neilmitchell.blogspot.com/2019/02/announcing-ghc-lib.html
It looks like it could solve the problem of having to compile hie for each different version of GHC.

Perhaps, a bit, or it might make it a bit easier. But the lack of an installed package database with ghc-lib might mean it doesn't help as much as it could.

@ndmitchell  Would it still help if having a targeted version of GHC installed is still required?
This way we'd have package database, but the benefit would be in that we'd need only one HIE binary instead of one per compiler, and wouldn't need hie-wrapper?

If you demand a targeted install of GHC, wouldn't that solve all the HIE issues anyway? I don't see how ghc-lib helps.
ghc-lib is certainly useful, and it could well help HIE, but it's not immediately clear where just yet.

@ndmitchell may of our dependencies use haskell-src-exts, maybe we could start there

@lorenzo that's not a bad idea. HLint intends to switch. However, ghc-lib takes a really long time to compile, which might end up causing problems...

I raised a ticket to see if the parse-only use case (e.g. haskell-src-exts) can be sped up https://github.com/digital-asset/ghc-lib/issues/39

@ndmitchell I guess what I meant is:
Currently, we compile different HIE executables, one for each version of GHC.
So each HIE user has hie-8.2, hie-8.4, hie-8.4.4, hie-8.6.2, hie-8.0, hie-8.2.1, hie-8.4.2, hie-8.6, hie-8.6.3 installed on their machine, plus hie-wrapper "to rule them all".
Could ghc-lib could help us having just one executable since ghc-lib, from my understanding, is able to work with code that targets any GHC? Or it doesn't target this problem?

Some of the code in HIE needs access to the package database. The package database for each compiler version relies on different GHC versions to access it. So while ghc-lib can give you the 8.6 API on GHC 8.4, it can't access the GHC 8.4 package database, which I imagine is required for some of the stuff HIE does.

Fundamentally hie needs to be able to load a module in the context of a specific project, including all the dependencies for that project. So if ghc-lib does not allow access to the existing package database, I think it may prevent it's use here.

I’ve managed to get ghc-mod and HIE compiling under ghc-lib, but it looks like it’s running into the issues above with the lack of the package database. (Trying to load a project with .hi files of different versions causes an error)
https://github.com/bubba/haskell-ide-engine/tree/ghc-lib

Ok. I suspect this tool is not going to help us in terms of being a useful general BIOS.

@alanz do you think ghc-lib would improve anything in other libs we use like HaRe?

@lorenzo I would have to investigate, but fundamentally things like HaRe are very tightly coupled to the specific AST in a GHC version, which does change from release to release.
So unless there is a generalising layer on top of it (which I understand haskell-tools does), then this will not really help there.
Also, HaRe specifically uses the hie plugin API, to be able to be easily integrated.


Activating Open Collective

Hi, I'm making updates for Open Collective. Either you or another core contributor signed this repository up for Open Collective. This pull request adds financial contributors from your Open Collective https://opencollective.com/pickr ❤
What it does:

adds a badge to show the latest number of financial contributors
adds a banner displaying contributors to the project on GitHub
adds a banner displaying all individuals contributing financially on Open Collective
adds a section displaying all organizations contributing financially on Open Collective, with their logo and a link to their website

We have also added a postinstall script to let people know after npm|yarn install that you are welcoming donations. Feel free to remove it if you don't want it. [More info]
P.S: As with any pull request, feel free to comment or suggest changes.
Thank you for your great contribution to the Open Source community. You are awesome! 🙌
And welcome to the Open Collective community! 😊
Come chat with us in the #opensource channel on https://slack.opencollective.com - great place to ask questions and share best practices with other Open Source sustainers!

Already available through npm fund.

Does that mean that you are not using Open Collective?

I'm using it, but I'll probably us it within https://github.com/npm/rfcs/blob/latest/accepted/0017-add-funding-support.md.
I really like the Idea the Idea but I'm not a friend of spamming the console with pls support me like corejs does (There was already a big discussion within the funding package repo :/)


Vulnerabilities identified in dotnet:4-slim base image

Hi, Our Snyk vulnerability scanner has detected a number of critical and high severity vulnerabilities coming from the latest version of the mcr.microsoft.com/azure-functions/dotnet:4-slim base image.
They are being picked up in the following packages and I've provided links to the issues.
glibc
gmp
openssl
zlib
https://security.snyk.io/vuln/SNYK-DEBIAN11-GLIBC-2340922
https://security.snyk.io/vuln/SNYK-DEBIAN11-GLIBC-2340908
https://security.snyk.io/vuln/SNYK-DEBIAN11-GLIBC-1296898
https://security.snyk.io/vuln/SNYK-DEBIAN11-GLIBC-1911968
https://security.snyk.io/vuln/SNYK-DEBIAN11-GMP-1920938
https://security.snyk.io/vuln/SNYK-DEBIAN11-OPENSSL-2426309
https://security.snyk.io/vuln/SNYK-DEBIAN11-ZLIB-2433933
I didn't know if these are something I should raise here and if they can be addressed in the base image?
Thanks

I'm hopeful that the new release will solve the issue now that it's moved to the latest dotnet base image: https://github.com/Azure/azure-functions-docker/releases/tag/4.5.0


where is root  dir on my hard disk ?

where is root  dir on my hard disk ?
I have install julia on win 7 on D disk. and some path of julia are on C/users/.../.Julia...
where is root  dir on my hard disk ?
Wher I must put the file index.html ?
Paul

HTTPServer.jl is not a traditional static web server. It is basically a framework to listen to  and parse HTTP request. The response needs to be coded by the programmer.
So, specifically, the root dir is where ever your implementation of the HTTPResponseHandler needs them to be.

Actually, a Handler for static files exists in Meddle.jl
https://github.com/JuliaWeb/Meddle.jl/blob/master/src/Meddle.jl#L137-L153
As you can see, the FileServer function takes the root directory as a parameter. Usage instructions are at  https://github.com/JuliaWeb/Meddle.jl/blob/master/src/Meddle.jl#L16-L27

Thx:)
Paul
W dniu 2015-03-03 o 15:32, Avik Sengupta pisze:

Actually, a Handler for static files exists in Meddle.jl
https://github.com/JuliaWeb/Meddle.jl
https://github.com/JuliaWeb/Meddle.jl/blob/master/src/Meddle.jl#L137-L153
As you can see, the |FileServer| function takes the root directory as
a parameter. Usage instructions are at
https://github.com/JuliaWeb/Meddle.jl/blob/master/src/Meddle.jl#L16-L27
—
Reply to this email directly or view it on GitHub
https://github.com/JuliaWeb/HttpServer.jl/issues/49#issuecomment-76955517.


Add plaintext as alias for text

I propose that the type plaintext is added under aliases for the Text language in https://github.com/github/linguist/blob/master/lib/linguist/languages.yml
Preliminary Steps
Please confirm you have...

[x] reviewed How Linguist Works,
[x] reviewed the Troubleshooting docs,
[x] considered implementing an override,
[x] verified an issue has not already been logged for your issue (linguist issues).

Problem Description
While writing markdown documents I often use the following to start a code block:
```text

However, this is inconsistent with some other tools, such as markdown-pdf which accept the following:
```plaintext

Predictably, I often find myself using the wrong keyword at the wrong time. To resolve this I propose that plaintext is added as an alias for text, assuming that it does not affect anything else.
I'd be happy to submit a small PR for this if it will be accepted.
Last modified on:
2021-01-10

Though I don't oppose the addition of a plain text alias (see #5109), I am curious as to why you're tagging code-blocks as "Text", rather than leaving them untagged. 🤔 On GitHub, both of these constructs are rendered identically. For example,
```text
Tagged
```

```
Untagged
```

yields
Tagged

Untagged

Is there something I'm missing?

Though I don't oppose the addition of a plain text alias (see #5109), I am curious as to why you're tagging code-blocks as "Text", rather than leaving them untagged. 🤔 On GitHub, both of these constructs are rendered identically. For example,
```text
Tagged
```

```
Untagged
```

yields
Tagged

Untagged

Is there something I'm missing?

@Alhadis you raise a good point.
I used to leave them untagged. However, after using other tools, mainly for pdf generation I found that leaving them untagged produced inconsistent results as by default it could apply a syntax highlighting to my code blocks. So now I always try to remember to tag the code block to have a uniform way of writing markdown.
In running through some quick tests, it does appear that plaintext when used on GitHub/Jekyll does not apply syntax highlighting. So this change would probably not affect anything. But still, it would be nice to have it properly supported.

@Alhadis you raise a good point.
I used to leave them untagged. However, after using other tools, mainly for pdf generation I found that leaving them untagged produced inconsistent results as by default it could apply a syntax highlighting to my code blocks. So now I always try to remember to tag the code block to have a uniform way of writing markdown.
In running through some quick tests, it does appear that plaintext when used on GitHub/Jekyll does not apply syntax highlighting. So this change would probably not affect anything. But still, it would be nice to have it properly supported.

Feel free to submit a PR then, but please add the alias as plain text (not plaintext). Doing so will implicitly add plain-text and plaintext as variant spellings, whereas the converse will only match plaintext verbatim. This is primarily relevant to code searches with a language: qualifier.

Feel free to submit a PR then, but please add the alias as plain text (not plaintext). Doing so will implicitly add plain-text and plaintext as variant spellings, whereas the converse will only match plaintext verbatim. This is primarily relevant to code searches with a language: qualifier.


Incorrect timezone and offset to Lisbon, Portugal

Get this from the API:
"latitude" : 38.729,
"longitude" : -9.153,
"offset" : -1,
"timezone" : "Etc/GMT+1"
The timezone is sort of correct (but would be better as Europe/Lisbon) but the offset is wrong. It should be +1.

Yes. Thanks. I switched to tz=precise and it works perfectly. I'm only querying once every 30 minutes so the extra 1/5s doesn't matter. Cheers. Great project.

Thanks for the quick follow-up here! I'm going to close this for now, but definitely feel free to re-open if anything else comes up


QA task: test data logging & enrollment for factorial experiment in staging env

When participants are enrolled and complete workspaces in staging for the factorial design, enrollment and metric data should be logged correctly in the new factorial Data tab

Main long-running ticket: https://carnegielearning.atlassian.net/browse/STU-2269
Currently this is what is happening: https://carnegielearning.atlassian.net/browse/DEVOPS-5774


Ability to restore the backup?

Thank you for your project.
But maybe we could implement a feature to also restore the backup file from the server?

Thanks for attention to my project, yes I will add this soon.

I add this feature to script you can check new release V.1.1.0 (2ef607178617178e3a43d291159ea1ff32766931)


Unexpected behaviour of auto complete suggestion window.

Issue: Autocomplete suggestion window not popping on line 1 when I write something on line 2.
Autocomplete suggestion window is not working as expected. I have no custom settings on my typescript settings file. I tried replicating this behavior with all settings disabled but the problem persists. As, this is not a crash issue or installation issue, I am not sure what logs I can provide. Autocomplete suggestion works fine when typescript plugin is disabled or removed.

Sublime text version 4107. Forgot to put this in the post.


滤波后在原图可视化骨骼图 贴合效果不理想？

曾爱玲 大佬您好，针对2D pose滤波，根据图像大小归一化图像序列对应的pose到【-1，1】，smoonthNet滤波后反归一化，整体的棍图看着是平滑没那么抖动了，但是在原视频中可视化，发现贴合到人的骨骼效果并不理想，可以简单分析下可能的原因吗？感谢

Hi @codylcs,
Since SmoothNet provided models are trained on existing mocap data and it does not refer to the input image, it will happen positional shift when the distribution of your data movements differs significantly from the distribution of the original training data (e.g., quite different speeds).


Nested handles inside recipes don't resolve.

If you do something like
recipe foo
  Particle
    in a
      out b

then out b never resolves. Weird, huh?

i'm confused, is this particle spec nested inside a recipe?

I think the example I saw was something more like
particle Parent
    in a
        out b
particle Child
    in c

recipe foo
    Parent
        a <- outer
            b -> shared
    Child
        c <- shared

And this wasn't resolving.
(This is here as a reminder for me to test this properly.)

Closing as no-repro (once I used the correct fate). As the user involved, I'm dismissing this as user error.


621 | Task Scheduler | C++

Title - 621. Task Scheduler
What will change - adding a new file with a solution for 621. Task Scheduler in C++
Type of Issue -

[x] Adding New Code

Programming Language

[x] C++

Self Check

Ask for issue assignment and wait to get assigned to it before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Discord server ✉ - https://discord.gg/CXksGdn
Happy Coding,

please assign me this issue


fix: Numeric Overflow for Teradata COUNT column validation

Closes #1023
This fix will allow users to CAST count at the outer level like so to avoid numeric overflow error:
- aggregates:
  - field_alias: count
    source_column: null
    target_column: null
    type: count
    cast: int64

with the SQL generated:
SELECT CAST(count(1) AS BIGINT) AS "count" FROM dataset.table

/gcbrun


Changed apt pin for nodejs to version contrail1

Currently nodejs version was apt-pinned to 0.8.* version. In 2.1 they have changed the dependency to include a contrail specific nodejs version which is now being directly built by contrail. It has contrail1 appended to its version

@vpramo please squash the commits into a single commit.


Bump stactools-usda-cdl to v0.1.2

Description
Update stactools-usda-cdl dependency to pick up https://github.com/stactools-packages/usda-cdl/commit/78c9e8ffb01685d465315c6fb5af49667ac59a59.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
I've re-tiled the data and the staging explorer looks better? I can't quite be sure b/c there's still some edge effects at far-out zoom but that should just be caching issues, many mid-level zooms look good.
Checklist:

[x] I have performed a self-review
[ ] Unit tests pass locally (./scripts/test)
[ ] Code is linted and styled (./scripts/format)

Thanks!


[BugFix] Fix bug metric not using bytes unit

Why I'm doing:
The metric units all end in bytes, but the actual display is indeed converted.
What I'm doing:
There is no need to go back and forth, just use the original bytes value, which saves memory but not calculation.
Fixes https://github.com/StarRocks/StarRocksTest/issues/5012
What type of PR is this:

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

https://github.com/Mergifyio backport branch-3.2

https://github.com/Mergifyio backport branch-2.5

https://github.com/Mergifyio backport branch-3.1

https://github.com/Mergifyio backport branch-3.0


Different train result between xgboost>=1.4.0 and xgboost<=1.3.3

I had a py-script to train a xgboost model. When I run the script (without earlystop) with different xgboost version(0.90 and 1.5.1), the AUC results show obvious difference(+0.3% val_AUC).
Therefore, I tested the script on lots of xgboost version, including 0.90, 1.0.0, 1.2.0, 1.3.1, 1.3.2, 1.3.3, 1.4.0, 1.5.1.  It show that xgboost>=1.4.0 return exactly same results  and xgboost<=1.3.3 return another same results  (ALL version are cpu-based)
I had read the release about 1.4.0, but I couldn't find out the reason.  Could you help me to understand what happened on xgboost>=1.4.0 ?
Below is the train/val result  on xgboost>=1.4.0 and xgboost<=1.3.3

Here is the Code:
params = {
    'booster':'gbtree',
    'objective':'binary:logistic',
    'tree_method':'approx',
    'eta':0.1,
    'gamma':0.1,
    'max_depth':5,
    'lambda':1,
    'subsample':1,
    'colsample_bytree':1,
    'min_child_weight':10,
    'eval_metric':'auc',
    'seed':0
}

df = pd.read_parquet('../data/my_trainset/ver=v6/dt=20220106/', columns=ALL_COLUMNS)
train_data, val_data = df[df['dt'] <= args.split_dt], df[df['dt'] > args.split_dt]
print(f'len(df) = {len(df)}, len(df.columns) = {len(df.columns)}, len(train_data) = {len(train_data)}, len(val_data) = {len(val_data)}')
del df; gc.collect()

dtrain = xgb.DMatrix(train_data[FEATURE_COLUMNS], train_data[LABEL_COLUMNS[0]]); del train_data; gc.collect()
dval = xgb.DMatrix(val_data[FEATURE_COLUMNS], val_data[LABEL_COLUMNS[0]]); del val_data; gc.collect()

evals_result = dict()
evallist = [(dtrain, 'train'), (dval, 'val')]
bst = xgb.train(
    params, dtrain, evals=evallist,
    num_boost_round=50, early_stopping_rounds=None,
    evals_result=evals_result, verbose_eval=1)

We have these changes from time to time, mostly caused by floating-point differences.

All the inputs and params are same. Before 1.4.0, the results are exactly the same. It doesn't seems like caused by floating-point differences.   So does xgboost>=1.4.0

We have rewritten the AUC from scratch in 1.4.0 https://github.com/dmlc/xgboost/pull/6747, which causes some differences.  The math is the same for binary classification, but the implementation differs from the old one.

There's also a small difference in the latest master branch where we changed the floating point in evaluation metrics from 32bit to 64bit.

I had conformed that We have rewritten the AUC from scratch in 1.4.0 #6747.  The different models predicted exactly the same scores, and the AUC of xgboost<=1.3.3  are same with sklearn.
thanks for your help !


Get the running runtimes sockets

We need to poll the list of running runtime sockets.
We need: https://github.com/platformatic/platformatic/pull/1115 to be merged in runtime first.

We can probably use the new platformatic "control package" for that. https://github.com/platformatic/platformatic/pull/2128/files


[Android] Is anyone planning to put mapview in Compose?

Hi, I'm going to start an application in Android Compose. I wanted to know if the project will put the view in Compose or if there is an example to know how to do it.
Thanks in advance.

Hi @ravenfeld I have not used compose before. What is it for? If you don't find documentation on how to do this, feel free to start a new readme or so and submit a pull request...

https://developer.android.com/jetpack/compose
This is a new way to create views on Android. It's a bit like Swift UI I think.

thanks a lot, that's what I was starting to look at. I'm just having trouble with the listeners doing leaks

which listeners? Maybe you need to observe the compose lifecycle or make some activity listeners and observe them in slide effects?

Sorry I didn't see your message. I also looked at Google Map and they did a lot of things on their side and not just put in an AndroidView. I don't know what the performance impact is.
And my code for drawing lines on the map is not very clean at the moment I think. Google map exposed the components in Composable on their side.

Hey folks, I'm using the official Mapbox SDK for Android at the moment in a Jetpack Compose app and had to adapt it to make it work. Here's what I'm doing more or less: https://gist.github.com/daniel-j-h/cd88b6cdf54e86bffed2bc440cbbb751
By now there is Google Maps for Compose, with a nice API; easy to use

https://developers.google.com/maps/documentation/android-sdk/maps-compose
https://cloud.google.com/blog/products/maps-platform/compose-maps-sdk-android-now-available
https://github.com/googlemaps/android-maps-compose

The official Mapbox SDK for Android still does not provide a similar API for Compose; there's an in-progress pull request upstream from summer 2022 but there seems to be no progress from what I can tell.
Ideally we would have a Google Maps for Compose like API and beat Mapbox to a great developing experience going forward :)

Thank you very much, I have started a work with Mapbox and we are relasioning with them. I am in the process of getting mapbox into compose but not sure if my company will allow me to do the same in opensource for maplibre.

If MapView wrapped in AndroidView is not a root, there will be problems with view annotation rendering. I just faced it and spent a lot of time in debugging
Annotations haven't been rendered at all until I removed all composable containers that hold AndroidView with map and made it as the root one

@RomanBapst and I have been working on such a library, both for MapLibre and Mapbox. It is called ramani-maps: https://github.com/ramani-maps/ramani-maps.
It does not have all the features (we added what we use first, obviously), but we intend to keep adding features steadily, and we are open to contributions :blush:.
I hope this helps!

I am using maplibre in compose and it is working flawlessly. I have checked how google made the GoogleMap composable function and mimic that solution. Underneath it is just an AndroidView composable, which is interop for classic XML. Here are some utils that I am using: https://gist.github.com/PiotrPrus/d65378c36b0a0c744e647946f344103c and here is a small sample of using it:
val map = rememberMapViewWithLifecycle()

AndroidView(
                modifier = Modifier.fillMaxSize(),
                factory = { map },
                update = { mapView ->
                    coroutineScope.launch {
                        val libreMap = mapView.awaitMap()
                        libreMap.setStyle(
                            Style.Builder().fromJson(
                                ResourceReader.readRawResource(
                                    context,
                                    R.raw.mapbox_style
                                ) ?: ""
                            )
                        )
                  }
)

I wouldn't set the style in the update maybe better in the Factory? so it's not called every time we want to update markers or camera position.  but probably this is just an example, it's very helpful, Thank you!

 Looking at google maps, that's what they do. The project above does it very well.

It seems like there is an issue with NativeConnectivityListener when trying to use MapLibre in Compose Previews.

Digging into this, it looks like it's some sort of native loader, which shouldn't be an issue inherently, but I am starting to realize that Compose Previews have several non-obvious limitations, including network and certain file APIs being unavailable.
Has anyone else gotten Compose Previews to work yet? This is clearly the modern way to do Android development, and not being able to use MapLibre here would be unfortunate.
Here is my code so far.
/**
 * Remembers a MapView and gives it the lifecycle of the current LifecycleOwner
 */
@Composable
fun rememberMapViewWithLifecycle(): MapView {
    val context = LocalContext.current
    val mapView = remember { MapView(context) }

    // Makes MapView follow the lifecycle of this composable
    val lifecycle = LocalLifecycleOwner.current.lifecycle
    DisposableEffect(lifecycle, mapView) {
        val lifecycleObserver = getMapLifecycleObserver(mapView)
        lifecycle.addObserver(lifecycleObserver)
        onDispose {
            lifecycle.removeObserver(lifecycleObserver)
        }
    }

    return mapView
}

private fun getMapLifecycleObserver(mapView: MapView): LifecycleEventObserver =
    LifecycleEventObserver { _, event ->
        when (event) {
//            Lifecycle.Event.ON_CREATE -> mapView.onCreate(Bundle())
            Lifecycle.Event.ON_START -> mapView.onStart()
            Lifecycle.Event.ON_RESUME -> mapView.onResume()
            Lifecycle.Event.ON_PAUSE -> mapView.onPause()
            Lifecycle.Event.ON_STOP -> mapView.onStop()
            Lifecycle.Event.ON_DESTROY -> mapView.onDestroy()
            else -> throw IllegalStateException()
        }
    }

@Composable
fun NavigationMapView() {
    val mapView = rememberMapViewWithLifecycle()

    AndroidView(
        modifier = Modifier.fillMaxSize(),
        factory = { mapView },
        update = { mapView ->
            mapView.getMapAsync { map ->
                map.setStyle("https://demotiles.maplibre.org/style.json")
            }
        }
    )
}

@Preview
@Composable
fun PreviewNavigationMap() {
    Mapbox.getInstance(LocalContext.current)
    NavigationMapView()
}

I've attempted to do some crimes against the JVM and use ByteBuddy to replace the class at runtime, but am like 12 layers deep into weeds and way out of my range of comfort with Java. If my hunch is correct, it seems like MapLibre should allow for a mock connectivity listener implementation to enable previews, and I was hoping to confirm quickly with hacks, but that's proving to be difficult 😅

Are there any plans to add native Jetpack Compose support?

Yeah, I really don't see any disadvantage, and I don't see how it could be done in a more "native" way than what Ramani Maps does. I could see a governance issue (i.e. if you have a problem using Ramani Maps because it is not officially owned by the MapLibre project), but technically I think it is as native as it gets (well "more native" could be by calling C++ directly instead of using MapLibre Android, but IMHO it would be a poor idea).

Ramani Maps looks promising. However being a separate project it probably won't get the latest beta or pre-release versions of Maplibre..

However being a separate project it probably won't get the latest beta or pre-release versions of Maplibre...

Can't you just tell gradle to point to a different version of the dependency when including org.ramani-maps:ramani-maplibre, e.g. like this? :thinking:

Yes. Gradle is a complex beast to understand, but this is totally possible. And doesn’t require merging higher level wrappers like Ramani or the similar SwiftUI project into the main repo.

However being a separate project it probably won't get the latest beta or pre-release versions of Maplibre...

Can't you just tell gradle to point to a different version of the dependency when including org.ramani-maps:ramani-maplibre, e.g. like this? 🤔

Thanks! Indeed, it looks like a good option.


Performance test: ~2.5s to add 10,000 objects to an array

This issue is a follow-up to the replies to this tweet. I added 10,000 objects to an array, and on my it took about ~2.50s.
I'm using:
Chrome 118.0.5993.117 (Official Build) (arm64)
16GB, M1 Macbook Pro (2020)

Here is a sample trace:
Trace-20231031T225959.json
The code I used to add 10,000 objects to an array is this:
import { types } from "mobx-state-tree";
import { nanoid } from "nanoid";

const Bus = types.model({
  name: types.string,
  id: types.string,
});

const BusLine = types
  .model({
    distance: 0,
    stops: 0,
    buses: types.array(Bus),
  })
  .actions((self) => ({
    addBus(name: string) {
      self.buses.push({ name, id: nanoid(5) });
    },
  }));

const store = BusLine.create();

export function MSTTest() {
  return (
    <>
      <div>
        <button
          onClick={() => {
            performance.mark("1");
            for (let i = 0; i < 10000; i++) {
              store.addBus("hello world");
            }
            performance.mark("2");
            performance.measure("Add 10000 items", "1", "2");
            console.log("ADDED 10000");
          }}
        >
          Add 10000
        </button>
      </div>
    </>
  );
}

Do note that I didn't write this to try and be as optimal as possible, nor to make it the most helpful test for debugging performance issues. I wrote this to get a comparison with the other state management library I'm tested on the tweet.
For example, I generate an id for every object, which in isolation is noise, but in the context on my test and application was necessary, since I do need an id, and I generate them on the test where I use the other library.
Out of curiosity I ran a version of it that doesn't generate ids and the difference is trivial.

@mrkev thank you so much! I will adapt this into the existing benchmarks. I'm sure your own state library will keep your hands full, but let me know if you ever want to talk shop about MST/state management performance.
We'll get these numbers down. Reproduction steps like this are very helpful to diagnosing issues and proving solutions!


Admissions get all remake

Codecov Report

Merging #189 (8629da2) into main (6231552) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #189   +/-   ##
=======================================
  Coverage   87.53%   87.53%
=======================================
  Files          17       17
  Lines         329      329
  Branches       33       33
=======================================
  Hits          288      288
  Misses         39       39
  Partials        2        2

Impacted Files
Coverage Δ

backend/services/admissionService.js
88.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Use a separated set to record generated typedefs.

Hi @tianxiaogu @D-D-H,
I propose the following change to resolve #26, but I'm not familar with roundEnvironment.getElementsAnnotatedWith(e) and I'm not sure the new way to check if a TypeDef has been generated has some cons.
I would like to know how you folks think about that?

Merge as all tests are ok.


Tried the example without succes

Hi,
I've found you library very useful. However, when trying to run the example, it raises an error for plot_utils not being part of entsog. Could you help me with this?
Thanks.

Hi, thanks for using the package. It is due to me not having updated it on the PyPi yet. I am a novice when it comes to releasing packages, it's also an extra dependency (the plots stuff) I am not sure I want to add. I will update and push to PyPi it later this week, and close the issue.

In the meantime, if you want you can just copy the plots_util functions in entsog/plots_util.py in your file and you'll be able to run the example (after installing plotnine).


chore(deps): update module github.com/gruntwork-io/terratest to v0.41.7

This PR contains the following updates:

Package
Type
Update
Change

github.com/gruntwork-io/terratest
require
patch
v0.41.6 -> v0.41.7

Release Notes

gruntwork-io/terratest
v0.41.7
Compare Source

Modules affected

terraform

Description

Added to terraform options parameter SetVarsAfterVarFiles which allows reordering var and var-file flags

Special thanks

Special thanks to the following users for their contribution!

@chilledornaments

Related links

https://github.com/gruntwork-io/terratest/pull/1217

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

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

GitHub release
v1.13.1

Your semantic-release bot :package::rocket:


Release rope crate on crates.io

I really like the design of your rope datastructure.  Have you considered publishing it?

See #89

Published at xi-rope on crates.io. Hope people find it useful. There is definitely documentation and cleanup still to be done, but I'll close this issue.


SPDX license identifier for reporting

SPDX license identifier should be used for license reporting. This will make it easier to automate results, especially across tools.
https://spdx.org/licenses/

Hello there,
This PR should fix the problem once it gets approved
https://github.com/pivotal/LicenseFinder/pull/876
The CI build fails for some reasons not linked to the changes made so I'm waiting for @xtreme-shane-lattanzio and the repo maintainer before proceeding. But Hope It can be merged soon !
once merged, you'll just have to use the option  --use_spdx_id to have the report with the spdx identifiers instead of random licenses names

As #876 is merged I guess you could close this. However, the new --use_spdx_licenses flag isn't documented in the README. Also, I was a bit surprised to find out I can't seem to use the SPDX name in the decision file.


Query UniProt programmatically to get info

Write simple python script (under /scripts) to:

[ ] Query UniProt API to get the FASTA sequence out of a UniProt Accession number

[ ] Get the organism NCBI Taxonomy id of the organism

[ ] Interface of library method (this method CAN BE IMPORTED FROM OTHER PYTHON CODE):

def query_uniprot(uniprot_ac: string):
...
return `namedtuple` with `fasta` and `organism_id`

[ ] Add a __main__ script subroutine that just prints the fasta (content) to standard output

Example for entry http://www.uniprot.org/uniprot/O43583,

fasta sequence: http://www.uniprot.org/uniprot/O43583.fasta (TRIVIAL!)
organism: 9606

@MadhukarSP NOT NECESSARY see #36


GMCP support

I have come across two scripts that help add support for GMCP in to YATCO. The first work's out of the box, is more simple, and respects YATCO's settings for gag and timestamp:
https://www.dropbox.com/s/31qbex4f9eyg0aj/GMCPChat.trigger.xml?dl=0
The second has nameDB support (which works) but does not respect YATCO options for gag even if gag is set to true in both YATCO and the script itself. It also does not appear with timestamps:
https://www.dropbox.com/s/76lkj7kvj6b6s29/GMCPChat.xml?dl=0
Any thoughts towards including GMCP support in YATCO natively?

I'm for it. I'll try to take a look tomorrow, get this and some anitimer
issues resolved.
On Feb 3, 2018 2:11 AM, "Brenex"<EMAIL_ADDRESS>wrote:

I have come across two scripts that help add support for GMCP in to YATCO.
The first work's out of the box, is more simple, and respects YATCO's
settings for gag and timestamp:
https://www.dropbox.com/s/31qbex4f9eyg0aj/GMCPChat.trigger.xml?dl=0
The second has nameDB support (which works) but does not respect YATCO
options for gag even if gag is set to true in both YATCO and the script
itself. It also does not appear with timestamps:
https://www.dropbox.com/s/76lkj7kvj6b6s29/GMCPChat.xml?dl=0
Any thoughts towards including GMCP support in YATCO natively?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/demonnic/YATCO/issues/8, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAOTBVU8a16rJdIMk8pA24hbRKMbnsbks5tRAaegaJpZM4R4E1q
.

Looking into this a bit today, haven't had the kind of time I'd hoped this weekend.

Here is my fix: https://github.com/Brenex/YATCO

This seems interesting, as my game as well sends chat text via GMCP

having moved to EMCO and changed it to be non-chat specific, I think gmcp drivers may need to be on a per-game/package basis. Since the name of the end tabbed object is not fixed, and I no longer assume chat is all you want to do with it, and not everyone will want to use the same tab names, it may be easier to instead provide an example on the wiki for EMCO of how you might take a gmcp chat message and redirect it.


Proxy release 2024-03-04

Proxy release 2024-03-04
Please merge this Pull Request using 'Create a merge commit' button

Reviewed for 2024-03-08 changelog


Fixed #35856 -- Added QuerySet.explain() support for MEMORY/SERIALIZE option on PostgreSQL 17+.

Add support for MEMORY/SERIALIZE option to QuerySet.explain() on PostgreSQL 17+.
Trac ticket number
ticket-35856
Branch description
Add support for MEMORY/SERIALIZE option to QuerySet.explain() on PostgreSQL 17+.
Checklist

[x] This PR targets the main branch.
[x] The commit message is written in past tense, mentions the ticket number, and ends with a period.
[x] I have checked the "Has patch" ticket flag in the Trac system.
[x] I have added or updated relevant tests.
[x] I have added or updated relevant docs, including release notes if applicable.
[x] I have attached screenshots in both light and dark modes for any UI changes.

Thanks for reviewing @felixxm : I was going to check that everything was OK before asking for your review but I appreciate your initiative!


[Sema] Minimum access for protocol requirement members to 'fileprivate'.

What's in this pull request?
CC: @jrose-apple
I'm not sure this is the right fix.
// ModA/File1.swift
private protocol P  {
  func privMethod() // This was implicitly `internal`.
}
public class C : P {
  public init() {}
  fileprivate func privMethod() {
    print("FOOBAR")
  }
}

C.privMethod() was visible from other file. (Because P.privMethod() was internal)
// ModA/File2.swift
extension C {
  public func callPrivMethod() {
    // This should be "error: use of unresolved identifier 'privMethod'",
    // but was not.
    privMethod()
  }
}

This compiles.
But, ends up with runtime error  'fatal error: call of deleted method'
// main.swift
C().callPrivMethod()

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

A smoke test on macOS does the following:

Builds the compiler incrementally.
Builds the standard library only for macOS. Simulator standard libraries and
device standard libraries are not built.
lldb is not built.
The test and validation-test targets are run only for macOS. The optimized
version of these tests are not run.

A smoke test on Linux does the following:

Builds the compiler incrementally.
Builds the standard library incrementally.
lldb is built incrementally.
The swift test and validation-test targets are run. The optimized version of these
tests are not run.
lldb is tested.

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

@swift-ci Please test

@swift-ci Please test

macOS: https://ci.swift.org/job/swift-PR-osx/3331/
Linux: https://ci.swift.org/job/swift-PR-linux/3522/

SE-0025 says we shouldn't care if the member has a higher access, but this might be a good enough patch fix anyway.
(We have a similar problem on a larger scale in SR-2315, and I expect the fix for that will take care of this as well. But I think this is a reasonable thing to do anyway.)

Both tests passed, force-merging.


Yellow color appearing in frames after saving video with the VideoWriter

Yellow color appearing in frames after saving video with the VideoWriter
I am running this on linux 18.04, Python 3.6.13 .
I will provide more info, just tell me what info is necessary

Hi, can you provide a minimal example to reproduce?

import cv2
from videoio import VideoWriter
cap=cv2.VideoCapture(0)
ret,frame=cap.read()
width=frame.shape[1]
height=frame.shape[0]
out=VideoWriter("out.mp4",resolution=(width, height))
while ret:
ret,frame=cap.read()
out.write(frame)
out.close()

Thanks! In this example, OpenCV returns frames in BGR, while video assumes RGB, so blueish objects can seem yellow. Is that what you mean by yellow frames?

Yes. Bluish objects  are appearing yellow. Actually the video was underwater, so lot of it was blue color. So everything seemed yellow. Is there a flag I can pass to VideoWriter, telling it to expect BGR frames instead of RGB ? Or should I change the frames to RGB before out.write(frame)

No such flag, but you can just do frame = cv2.cvtColor(frame, cv2.COLOR_BGR2RGB) before passing it to videoio

I suppose the problem is now resolved, let me know if not

Yes it's resolved. Thank you


Update HL7v2 to FHIR to HL7v2 DataType Mappings: FN

User Story

As a ReportStream engineer,
I want to update the ReportStream HL7v2 -> FHIR and FHIR -> HL7v2 mappings for the FN HL7v2 data type per the mapping inventory
so that I can ensure data does not get dropped during translation and enable the creation of mappings of ORU-R01 segments that reference this HL7v2 DataType.
Description/Use Case

Given the ORU-R01 context, this HL7v2 DataType can map to the following resources (the sub list shows where exactly in what mapping file the DataType mapping appears in):
- [ ] HumanName
    - [ ] HL7 Data Type - FHIR R4_ XCN[Practitioner] - Sheet1-XCN.2
    - [ ] HL7 Data Type - FHIR R4_ XCN[RelatedPerson] - Sheet1-XCN.2
    - [ ] HL7 Data Type - FHIR R4_ XCN[Patient] - Sheet1-XCN.2
- [ ] string
    - [ ] HL7 Data Type - FHIR R4_ XPN[HumanName] - Sheet1-XPN.1
    - [ ] HL7 Data Type - FHIR R4_ XPN[string] - Sheet1-XPN.1

Testing
The unit tests for the mappings of this DataType DO NOT have to cover every since segment a particular HL7v2->FHIR / FHIR->HL7v2 mapping appears in. It is sufficient to pick a representative segment and base the DataType mapping tests off of it. The unit tests should verify a segment containing a particular mapping maps correctly to HL7v2->FHIR and FHIR->HL7v2, having a test case for each condition or logic outlined in the mapping inventory for a particular mapping.
Acceptance Criteria

[ ] Mappings outlined in the Description of ticket have been created/updated per the mapping inventory
[ ] Unit Tests created per testing strategy
[ ] Any new RS extensions have FHIR examples documented

FN mapping requires extensions on the FHIR string primitive


remove timedout request ctx's from waiting_requests queue

The patch addresses a possible crash in case of non-working LDAP server.
At the moment, if request context gets into server->waiting_requests queue, it can be read in ngx_http_auth_ldap_get_connection() after context memory is freed, because it is still in the queue after request was timed out.

One can verify that there was a use-after-free by compiling nginx with nginx-auth-ldap module having NGX_DEBUG_PALLOC=1  macro definition. That will make every pool allocation to be actually a separate call to malloc, allowing use of Valgrind.
Then, configure a single LDAP backend, run Nginx (single process mode, preferably) under Valgrind. Then make a request with an authorization, wait for timeout. Then make request one more time. On the second time, you should be able to see use-after-free event from Valgrind.

Issues #143, #104, #56, and #33 all look related. There are either crashes in functions that use server->waiting_requests or very similar condition — crashing when LDAP backend is not online.


chore: release main

:robot: I have created a release beep boop
nest-utils: 3.0.0
3.0.0 (2024-11-16)
⚠ BREAKING CHANGES

testing: Migrate testing to separate package
auth: Decouple AuthModule from express-openid-connect by forcing consumers to import the auth middleware themselves and hand it over to this package

Features

auth: Decouple AuthModule from express-openid-connect by forcing consumers to import the auth middleware themselves and hand it over to this package (90ea1de)
testing: Migrate testing to separate package (f0f3c13)

Bug Fixes

auth: Mark AuthModule as global module properly (e01d870)

nest-testing: 1.0.0
1.0.0 (2024-11-16)
⚠ BREAKING CHANGES

container: TestContainer no longer implicitly includes AuthModule, but instead detects when it has been provided

Features

container: TestContainer no longer implicitly includes AuthModule, but instead detects when it has been provided (784da85)
testing: Implemented new package @spuxx/nest-testing (a9719e2)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

nest-utils-v3.0.0
nest-testing-v1.0.0
:sunflower:


[bugfix] Immediately warp into vehicle

If you spawn a car in a garage kind of location, it'll blast off. That is why we need to immediately warp them after spawn.

Could cause trouble for players with high latency as they'll be warped before the vehicle is created?

Nah, it's my bad.


Files browser for 0.4

WARNING Hacks and bad code in here!

Currently working

Create directories
Navigate directories
Preview images, markdown and raw data

Goals

[ ] Clean Code
[ ] Video previewer
[ ] Code highlighting on text files
[ ] Upload files
[ ] Move folders and files via drag and drop
[ ] Delete files and folders
[ ] Folder creation inline
[ ] Better sorting (first folders, then files, set sort order by clicking on the header)
[ ] Make it look good
[ ] Select on click, double click to open
[ ] Inline rename
[ ] Copy?

Preview

this looks amazing and i love it.
On Sun, Jan 24, 2016 at 3:31 PM Friedel Ziegelmayer <
<EMAIL_ADDRESS>wrote:

WARNING Hacks and bad code in here!
Currently working

Create directories
Navigate directories
Preview images, markdown and raw data

Goals

[ ] Clean Code
[ ] Video previewer
[ ] Upload files
[ ] Move folders and files via drag and drop
[ ] Delete files and folders

Preview
[image: ipfs-files-2]
https://cloud.githubusercontent.com/assets/790842/12539807/a4c31fc4-c2fa-11e5-9a61-c5e9be2d53eb.gif
[image: ipfs-files-first]
https://cloud.githubusercontent.com/assets/790842/12539809/a66e48bc-c2fa-11e5-88dd-27799891eaeb.gif
You can view, comment on, or merge this pull request online at:
https://github.com/ipfs/webui/pull/221
Commit Summary

Start working on the files browser for 0.4

File Changes

A app/scripts/components/files-explorer.js
https://github.com/ipfs/webui/pull/221/files#diff-0 (65)
M app/scripts/pages/files.js
https://github.com/ipfs/webui/pull/221/files#diff-1 (420)
M app/styles/app.less
https://github.com/ipfs/webui/pull/221/files#diff-2 (2)
M app/styles/base.less
https://github.com/ipfs/webui/pull/221/files#diff-3 (11)
A app/styles/components/files-explorer.less
https://github.com/ipfs/webui/pull/221/files#diff-4 (40)
M package.json
https://github.com/ipfs/webui/pull/221/files#diff-5 (5)

Patch Links:

https://github.com/ipfs/webui/pull/221.patch
https://github.com/ipfs/webui/pull/221.diff

—
Reply to this email directly or view it on GitHub
https://github.com/ipfs/webui/pull/221.

Wow this looks great!!!
Some other things I think it should have:

publish button to publish object (or the root) via IPNS (maybe with an option to folder wrap or not)
permalink button (it copies to clipboard or shows an IPFS link to an object)

As a way to copy files:

duplicate button (creates a copy in the same folder)
move (to move a file or folder) and paste (to paste it somewhere else)

Of course real file manager functionality (select multiple files, move/copy them) would be better but it would get a lot harder to make.

Agreed that this looks awesome!

@dignifiedquire could you test a markdown document that contains <script>alert(document.domain)</script> as inline html?

Are you planning to use highlight.js to highlight source files and maybe detect source files?

@Kubuxu yes sth like that

Closing in favor of #229


ModuleNotFoundError: No module named 'torch_geometric.data.storage'

Hi @lightaime , thinks for your excellent job and instant reply, I've solved OSError problem. But new problem appears, it confused me a lot when I run the gcn_graph/train_search.py
File "train_search.py", line 313, in
main()
File "train_search.py", line 177, in main
train_dataset = GeoData.PPI(os.path.join(args.data, 'ppi'), split='train')
File "/home/tie.xu/anaconda3/envs/sgas/lib/python3.6/site-packages/torch_geometric/datasets/ppi.py", line 55, in init
self.data, self.slices = torch.load(self.processed_paths[0])
File "/home/tie.xu/anaconda3/envs/sgas/lib/python3.6/site-packages/torch/serialization.py", line 529, in load
return _legacy_load(opened_file, map_location, pickle_module, **pickle_load_args)
File "/home/tie.xu/anaconda3/envs/sgas/lib/python3.6/site-packages/torch/serialization.py", line 702, in _legacy_load
result = unpickler.load()
ModuleNotFoundError: No module named 'torch_geometric.data.storage'
Best!

@Sigmafye Have you resolved your issue? I'm encountering the same problem now, and I hope you can help me solve it.


Render markdown in notes

I was hoping to submit a PR instead of an issue...
I want to have an aside with markdown in it. e.g.:
<aside class="metrics" markdown="1">
**fun** stuff
</aside>

I've tried leveraging notes (I was going to hack css for speaker notes) But I can't get it to create a node with bold in it.
``notes
**fun**
``

I've tried modifying slide_markdown.rb by adding postprocess(preprocess(code)) but it still didn't work.
Any suggestions how to create a node with div around it (and css name)?
Thanks as always for the great tool.

How does #69 look to you?

Version 3.4.0 has been published here (https://rubygems.org/gems/reveal-ck/versions/3.4.0) if you'd like to try it out.


enable outbound network from within a pod

How does one enable outbound network connections initiated from within a running pod?

Hey @dustinkirkland , I actually just put up a PR to add this to the readme, see https://github.com/ubuntu/microk8s/pull/77/files

It's merged now, see https://github.com/ubuntu/microk8s#my-pods-cant-reach-the-internet-but-my-microk8s-host-machine-can

Thanks a bunch!
@DustinKirkland
On Tue, Jul 24, 2018 at 2:59 PM, Tim Van Steenburgh <
<EMAIL_ADDRESS>wrote:

It's merged now, see https://github.com/ubuntu/
microk8s#my-pods-cant-reach-the-internet-but-my-microk8s-host-machine-can
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ubuntu/microk8s/issues/78#issuecomment-407532518, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAzMhqgGWrIFqcjfuYHJaNuWHNZzr7SKks5uJ3yMgaJpZM4VdV6c
.


Docker support with LiteDb

Hi Team,
Wanted to check whether I can install lite db in docker image alongwith asp.net core. If so, can you provide few examples or samples which I can refer. I tried finding documents around but didn't fine. This is meant for developers machine.
Thanks,
Rahul

Well...LiteDB isn't a server. It's a file, managed by your code. There shouldn't be an issue with running it in Docker.

Yeah thanks for the response. Figured out this.


[10.x] Allow easier detection of whether migrations need to be run

Diff looks simpler if https://github.com/laravel/framework/pull/47396 is merged first.
Currently, php artisan migrate:status exits with success whether or not there are pending migrations. This PR allows developers to programmatically detect whether migrations need to be run.
The common exit status 117 means Structure needs cleaning which I consider a good fit in this case, because the database must be changed to the desired structure.
No BC breaks. If you wish, I can PR a docs addition.
When this PR is merged, we will be able to do this in our deployment scripts:
#!/usr/bin/env bash

php artisan migrate:status --non-zero-when-pending

if [ $? -eq 117 ]; then

  echo "Handling pending migrations..."

  php artisan down
  php artisan migrate --force

  # ..

fi

Maybe simpler to just write your own command that calls this command and exits based on the output it sees?


fix: add res to reqCustomProp function signature

Added res object as additional function parameter to the reqCustomProps function
Non-breaking now, but function name will need to be changed in next semver major update, will add PR after this is merged to reuse the branch.
Updated README.md and test.js with new function signature.
Side effects:

had to add "bash" to beginning of benchmark command since it relies on bash, and errors out on systems where bash is not the default.
added "fix" npm script since locally installed standard has to be run inside npm script to use local version, and standard --fix must be run to get tests to run.

closes #119

5.4.0 published

5.4.0 published


visual feature extraction

"When using different splits to train a visual feature extractor (e.g., ST-GCN), do you use the entire visible feature test set as the validation set? How can we ensure that, while training solely on the visible feature training set, the accuracy on the visible feature test set reaches around 93% instead of around 82% (as reported in the ST-GCN paper)? If you can see this, please address my concerns. Thank you."

Hi,
Thanks for your question. We only use seen classes extracted from the entire validation set to test our model. As we use only the seen classes to train and test our model, this makes the problem simpler or harder depending on the selection of the unseen classes. Thus you can't directly compare these two performance numbers.
Thanks,
Oscar

Hello, first of all, thank you for your response. Perhaps due to the lack of clarity in my initial question, I’ll try to express it more thoroughly this time.
I noticed that in the visual feature files, there is a val.npy file, whose size matches the size of the test set after excluding the unseen classes. I assume you trained the skeleton feature extraction module on all seen classes in the training set and then validated it on all seen classes in the test set. However, I also noticed another file, val_out.npy, which should represent the classification scores of the validation set. Comparing this with the real labels of the validation set’s seen classes in the val_label.npy file, I found that the accuracy is close to 93%. If you trained only on all seen classes in the training set, the model should not reach such high accuracy.
Could you clarify if the skeleton extraction framework is trained solely on all seen class data from the original training set? Or does it also include some seen class data from the original test set?


Improve GitHub issue forms

Adds 3 new forms

I think we can keep icon suggestions & submissions in the same form

@tandpfun how about now?


Interactive SICP-JS: Improve readability + minor fixes

Description

Improved readability by altering max width, line-height and font size.

Fixed formatting issues on index page. Previously, title and contents  were not aligned properly. Also updated adapters names.

Remove dead code from syntax highlighting library that was previously bundled by webpack.
before:

after:

Fix figure margins and text alignment. Figures now have margins on the top and bottom. Text alignment for code snippets no longer centered (left align now).

Simplify parsing of containers, defined as elements that have a title and hold child elements. Previously, tags such as SECTION, SUBSECTION, SUBSUBSECTION etc. were all handled separately, even though they are parsed in same way. After this PR, the tags will all be parsed as section tags.

Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Code quality improvements

How to test

Checklist

1 & 2: verify page is as shown in the screenshots
3: build the project using yarn build, the build/static/js folder should look like the screenshots in the description. Syntax highlighting should still work.

[x] I have tested this code
[ ] ~I have updated the documentation~

Ready to merge after this PR is merged.


migrated AllListFragment to kotlin

Description
migrated AllListFragment to kotlin from java
Issue Resolved
Link to the issue that is resolved by this pull request goes here e.g. 'Fixes #47'.
Checklist
Please make sure to review the following before submitting your PR:

[x] I have read the contribution guidelines.
[x] I have read the code of conduct.
[x] I have reviewed my submission in detail.

Lgtm, thanks ✌


Avoid using eval

Try to fix #111.

Changes Unknown when pulling 4a1b04bb731787b804959340c4207fbb99cf4fa8 on avoid-using-eval into ** on master**.

Changes Unknown when pulling f279bcc20069ba057dfda2e0eed0d6237d5ef76a on avoid-using-eval into ** on master**.

Thanks dude, that's awesome! 👍


[Added] Pinstr app to Nostr section

Describe the changes you have made in this PR
Added  https://pinstr.app/  to Nostr section
Link this PR to an issue [optional]
Fixes #2432
Type of change

feat: New feature (non-breaking change which adds functionality)

Screenshots of the changes [optional]

Logo used -

Checklist

[x] My code follows the style guidelines of this project and performed a self-review of my own code
[x] New and existing tests pass locally with my changes
[x] I checked if I need to make corresponding changes to the documentation (and made those changes if needed)

@bitcoinuser Please review the PR at your earliest convenience.