Notify cluster admin about soon to be expired certs

https://github.com/appscode/kubed/issues/15
We want to move this as a ClusterAlert here, instead of a Kubed thing. This is already implemented in Kubed.

https://github.com/appscode/kubed/blob/master/pkg/cert/cert_watcher.go#L71


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative-sandbox/api-core-wg-leads
/assign knative-sandbox/api-core-wg-leads
Produced by: knative-sandbox/knobots/actions/update-deps
Details:
bumping knative.dev/pkg 7a61343...dec98b4:
  > dec98b4 fix a small lint warning (# 2270)
  > fbe9e7e Widen the error checker interface to allow response error checking (# 2253)

/lgtm
/approve


Add TLS support to load balancer/application

Would be a good idea to add some sort of TLS support to the application or load balancer. Right now the load balancer runs over http. Also would be good to look at the newer load balancer instead of the "classic" one.

Sigh this seems to be a bit invovled. Not sure if the generated domain can be used with the cert.

https://docs.aws.amazon.com/elasticloadbalancing/latest/network/create-tls-listener.html https://docs.aws.amazon.com/acm/latest/userguide/acm-overview.html
https://www.azavea.com/blog/2018/07/16/provisioning-acm-certificates-on-aws-with-terraform/
https://www.oss-group.co.nz/blog/automated-certificates-aws
https://github.com/terraform-aws-modules/terraform-aws-eks/issues/433
https://learnk8s.io/terraform-eks
The ACM can be provisioned with Terraform to generate/get the cert. Still unsure about the domain.  Can setup ALB for kubernetes to get certs maybe.

https://github.com/yandok/terraform-aws-eks-template
https://itnext.io/the-definitive-guide-for-setting-up-a-clean-and-working-aws-eks-kubernetes-infrastructure-for-2d4153d47e20
This might also help with the env stuff as well.

https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/set-up-end-to-end-encryption-for-applications-on-amazon-eks-using-cert-manager-and-let-s-encrypt.html

Ingress controller seems to be the way go. Also would help to get rid of the nat gateway. Might need to make another ticket for that maybe.


Bad unknown6 signature builder

I'm not really using this library but I should let you know that node-pogo-signature is deprecated in the way seeds+signature is generated and is detectable.
You should probably fork it and do the fixes.
Seeds changed for the xxhash function, the githash commit id (uk25) isn't set (And it is set since version 0.33.0).

@SpencerSharkey what do you say?

Sorry, I'm so late here...
I did update node-pogo-signature with the updated hash seed (for the xxhash utils). Since this repo relies on ^2.0.0 a simple npm update should at least fix your hash seeds.
I am unaware of the uk25 addition. I'll take a look into this when I can find some free time. Anyone is welcome to fork and submit a pr :)

A fork was made and node-pogo-signature was updated. See
5530068aabebf0442cacb3975e1242cda9438d29.


fix: DEV-2931: Fix hiding NER regions with new outliner

Hi @nicholasrq!
This PR was created in response to a PRs in upstream repo:

https://github.com/heartexlabs/label-studio-frontend/pull/764

/git merge develop


[tests-only] Bump core commit for API tests

Includes changes from test-related PRs:
https://github.com/owncloud/core/pull/38066 [tests-only] Use PHP 7.4 for behat acceptance test dependencies
https://github.com/owncloud/core/pull/38069 [Tests-Only] Refactor GET request to a pending remote share
https://github.com/owncloud/core/pull/38068 [Tests-Only] Adjust then steps for the unsuccessful sharing scenarios
https://github.com/owncloud/core/pull/38071 [Tests-Only] add api tests for checking etag propagation on copy operations
And some feature files had minor (= annoying) line number changes.
Similar PR in owncloud/ocis is https://github.com/owncloud/ocis/pull/792

@ishank011 ready for review


DISCUSSION: Digital Ocean V2 API

Hey guys, particularly maintainers, as you've likely heard DO moved their V2 API out to beta. It's RESTful, more secure, and does pagination well.
Part of the magic of this repo was that it was heavily metaprogrammed. It allowed someone to easily add new endpoints with very little knowledge of the library.
In large part that was thanks to DO's V1 API - which I actually ended up loving despite not following generally accepted RESTful practices.
So, let's discuss moving this to V2. I think we'd all like to take a similar metaprogrammed approach if possible. Is it possible with the new V2 API?

This has been almost a year since I cared for this. I'm opting to just leave it at V1 and point people to the official V2 gem.
https://github.com/digitalocean/droplet_kit

https://github.com/motdotla/digitalocean/pull/51


Reading the body of a request

I want to be able to read the body of a (multipart) request I have built, for tests, but I cannot because there does not seem to be a public API for converting a Body (async nor blocking) into bytes. It has an as_bytes() method, but for Inner::Streaming it returns None (same for blocking's Kind::Reader) so there seems to be no way to publicly access that data when it needs to be streamed to turn into bytes. Am I missing something to do this? Or is this a missing feature?
To be clear, I see the tests: https://github.com/seanmonstar/reqwest/blob/master/tests/multipart.rs that compare against what was received by an actual http server. And the unit tests access private methods.
Thanks.

Am I missing something to do this? Or is this a missing feature?

You're not missing anything. It so far was not publicly exposed. In #2059, there's a possibility of keeping the public impl HttpBody for Body, in which case you could use that.

the unit tests access private methods.

The integration tests (in the tests directory) all use public methods, they are compiled as separate from the library, they don't have any internal access.

possibility of keeping the public impl HttpBody for Body,

Sounds good, I would appreciate that, thanks :)

The integration tests (in the tests directory) all use public methods, they are compiled as separate from the library, they don't have any internal access.

Yes, that's why I mentioned the unit tests as separate, e.g. https://github.com/seanmonstar/reqwest/blob/4f54ba732f80ccb89e50954a369d6e8bb46375f2/src/async_impl/multipart.rs#L591 which does exactly what I want -- but relies on private methods.


Implement std Error for decode and encode errors

This PR implements the std::error::Error trait for decode::Error and encode::Error. This makes these error types more versatile for some uses. E.g. it permits them to work with an std Error trait object (Box<dyn Error>).
Since the current Debug impl for decode::Error seemed to be more of a Display impl (require by std Errror) I changed it as such and added a derived Debug impl.

@wezm Looks good!  Thanks again.


Certificate domain vaildation fails with CN=*.com

Sourcehut's Gemini hosting service (gemini://srht.site/) uses certificates with wildcards and just the TLD in the common name (to be as generic as possible), for example CN=.com and CN=.site.
The domain validation in Lagrange fails and an error message is displayed: "UNTRUSTED CERTIFICATE".
I found the comment at https://github.com/skyjake/lagrange/blob/1e5dfdc840824723dfa142707aca1f0fca4c0056/src/gmcerts.c#L396 and I'm wondering (sorry, not much time to read the code further) if this is expecting common names to have at least two non wildcard labels.

The wildcard check is done by OpenSSL and I’m pretty sure it has no concept of a certificate that covers an entire TLD.
I think in the context of Gemini it’s fine to use more lenient wildcard checking, although it needs to be done manually.
The referenced line is related to implicit wildcards where a “site.tld” certificate is automatically allowed for “subdomain.site.tld”.

TlsRequest in the_Foundation now supports this kind of wildcards.

Fixed in v1.3.4.


feat: create shopcart api and testing

Now able to pass all 26 testing

Looks good, but missing test case for the success scenario of making a shopcart.

Added the missing test case


Support away_mode as permanent hold and hold_mode as temporary hold.

Description:
We had discussed deprecating away_mode as it is overlapping with hold_mode.
After some discussions with users on the forum I found an interpretation of both modes which justifies both but which makes them different enough so they don't interfere or overlap:

away_mode is a permanent change of the target temperature to some determined temperature
hold_mode is a temporary change of the target temperature

Users have been using the away_mode as a way of emulating vacation hold, as provided by some, but not all climate devices. Hold mode, on the other hand, is to support the smart hold and away (and other) functions provided by some, but not all, climate devices.
This interpretation provides a consistent and meaningful requirement for climate devices with respect to these modes.
I have changed the implementation of the hold_mode and away_mode features on the ecobee platform to match above definition.

away_mode is just on/off as before; it permanently switches the target temperature to the temperature defined in the away climate.
home_mode provides away, home, temperature, and vacation hold and temporarily (until the next climate transition) switches the target temperature to the indicated temperature.

Please note that nordlead2005 has proposed a further enhancement of hold_mode building on the current hold mode which is consistent with above and also useful.
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#1944

@MartinHjelmare As we discused, this pull request omits the changes to be made by nordlead2005 which are now meant to be checked in on top of these changes. After he or she checks those changes in, I have some more updates to ecobee waiting.

Is this a breaking change?
I.e. if someone is using hold_mode / away_mode will their climate behaviour change?

Actually, this tries to resolve something that was a "breaking change". We had discussed deprecating away_mode for climate because it was not scalable. hold_mode was implemented to subsume away_mode and be scalable to many different hold_types.
This change found a way of keeping away_mode working while allowing hold_mode to provide a larger solution.
There is in general the issue that every hold (or away) is a mode where the target temperature differs from the target temperature dictated by the currently active climate and involves potentially some decisions:

what temperature should the desired target temperature be set to?
for how long should this deviation last?
what properties other than temperature (e.g., fan, humidity,...) are affected?

Every climate device may handle this differently, so the climate component has to be reasonably generic.
This change proposes to:

At the climate component level, maintain away_mode and hold_mode both, thus is compatible with all running code out there.
Individual climate devices need to decide how to handle the questions above. The ecobee component has a proposed implementation which is consistent with the current code also.

The code seems fine to me, but I never had a climate/ecobee device, so lets wait for another reviewer.
Meanwhile, is it possible to add tests for the new code?

Tests already exist for both away_mode and hold_mode for the demo climate.

That seems like a good solution. We should make sure to describe this in the docs for climate so it also won't get lost 😉
Merging this as tests in place for the demo component.

@balloob I have extensively documented the ecobee component, including an explanation of the various concepts of a climate device as interpreted by the ecobee component. I would like to to the same for the climate component itself, but it is more tricky as one has to infer what was meant from the code of the implementing climate devices (as there is precious little explanation in the climate component itself).


Fix inline comment in example config

The config as written doesn't parse:
FATA[0000] error loading configuration file - Near line 7 (last key parsed 'Server'): Expected a top-level item to end with a new line, comment or EOF, but got '/' instead.

@cceckman thanks


Performance issue with table

Package
filament/filament
Package Version
v3.2.94
Laravel Version
v10.48.16
Livewire Version
v3.5.4
PHP Version
PHP 8.2
Problem description
Hey! Yesterday we managed to bump versions in our application (v3.2.73 -> v.3.2.94) and we encountered strange performance drop with table component.  After version bump in some cases our table load time jumped from couple of seconds to 20-30 seconds. To be fair, our table is huge (100 records, 12 columns, 20+ filters), and it already had some issues with performance but we solved some of them and were happy. I run some performance tests to find out what is going on and this is the result.
Before version bump

After version bump

It looks like watchForCheckboxClicks method takes enormous amount of time to do the work. There was a discussion about possible performance but as far as I understand there were no changes made.
LINKED PR https://github.com/filamentphp/filament/pull/13074
Expected behavior
We would like the table to load in the same amount of time it did before or at least in bearable time. In the linked PR there was an idea to let user manage this feature on/off and it would be superb for us.
Steps to reproduce
In provided repository:

run seeder (2000 users)
go to http://<IP_ADDRESS>:8000/examples/list
apply email filter with any value
disable filter by pressing X in active filters section (yellow box)

application lags for a while (if you downgrade version under 3.2.87 - version with watchForCheckboxClicks then application run smoothly)
performance check for provided example

Reproduction repository (issue will be closed if this is not valid)
https://github.com/Tryfciu/filament-issue
Relevant log output
No response

Donate 💰 to fund this issue

You can donate funding to this issue. We receive the money once the issue is completed & confirmed by you.
100% of the funding will be distributed between the Filament core team to run all aspects of the project.
Thank you in advance for helping us make maintenance sustainable!

I have the same problem. The table freezes every time:

when any of the filters are applied or removed
when the user presses the back/forward button in the browser.

My table contains 1800 records, paginated by 100 records.

We are facing the same issue with watchForCheckboxClicks


UI Issues: Dark Mode Icon Misalignment, Missing Footer, and Small Text in "About Us" and "Feature Post"

The dark mode icons and the circle are slightly out of the small container, causing misalignment.

The webpage is missing a footer section.

The text in the "About Us" and "Feature Post" sections is too small, reducing readability. The font size should be increased to enhance the user experience.

With my strong background in HTML, CSS, and JavaScript, and considering the nature of the work required, I believe this task should be assigned as Level 2 or Level 3. Please assign this under GSoC '24 and Hacktoberfest.

there are separate issues for every point you have mentioned in this issue !

dark mode icons already fixed

I'm closing this issue because all points you've raised already exist as separate issues. This is unacceptable—you were clearly supposed to check for existing issues before creating a new one. Please follow the guidelines and make sure you do a proper check next time to avoid wasting time and cluttering the repository


spdlog: 1.8.5 -> 1.9.2

Motivation for this change
Supersedes #134609
i need 1.9.2 to package ananicy-cpp
Things done
built normal and pkgsStatic

Built on platform(s)

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

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

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

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

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

1 package marked as broken and skipped:

lizardfs

5 packages failed to build:

nrfutil
python38Packages.qiskit
python38Packages.qiskit-aqua
python39Packages.qiskit
python39Packages.qiskit-aqua

39 packages built:

bear
cherrytree
far2l
gerbera
hal-hardware-analyzer
kodi (kodiPackages.kodi)
kodi-gbm
kodi-wayland
kodiPackages.a4ksubtitles
kodiPackages.inputstream-adaptive
kodiPackages.inputstream-ffmpegdirect
kodiPackages.inputstream-rtmp
kodiPackages.joystick
kodiPackages.kodi-platform
kodiPackages.libretro
kodiPackages.libretro-genplus
kodiPackages.libretro-snes9x
kodiPackages.netflix
kodiPackages.pvr-hdhomerun
kodiPackages.pvr-hts
kodiPackages.pvr-iptvsimple
kodiPackages.steam-controller
kodiPackages.vfs-libarchive
kodiPackages.vfs-sftp
mtxclient
nheko
openroad
pc-ble-driver
python38Packages.pc-ble-driver-py
python38Packages.qiskit-aer
python38Packages.qiskit-ibmq-provider
python38Packages.qiskit-ignis
python39Packages.pc-ble-driver-py
python39Packages.qiskit-aer
python39Packages.qiskit-ibmq-provider
python39Packages.qiskit-ignis
spdlog (spdlog_1)
vowpal-wabbit
waybar

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 145006 run on x86_64-linux 1

1 package marked as broken and skipped:

lizardfs

4 packages failed to build and already failed to build on hydra master:

python38Packages.qiskit: log was empty
python38Packages.qiskit-aqua: log was empty
python39Packages.qiskit: log was empty
python39Packages.qiskit-aqua: log was empty

1 package failed to build and are new build failure:

nrfutil: log was empty

39 packages built:

bear
cherrytree
far2l
gerbera
hal-hardware-analyzer
kodi (kodiPackages.kodi)
kodi-gbm
kodi-wayland
kodiPackages.a4ksubtitles
kodiPackages.inputstream-adaptive
kodiPackages.inputstream-ffmpegdirect
kodiPackages.inputstream-rtmp
kodiPackages.joystick
kodiPackages.kodi-platform
kodiPackages.libretro
kodiPackages.libretro-genplus
kodiPackages.libretro-snes9x
kodiPackages.netflix
kodiPackages.pvr-hdhomerun
kodiPackages.pvr-hts
kodiPackages.pvr-iptvsimple
kodiPackages.steam-controller
kodiPackages.vfs-libarchive
kodiPackages.vfs-sftp
mtxclient
nheko
openroad
pc-ble-driver
python38Packages.pc-ble-driver-py
python38Packages.qiskit-aer
python38Packages.qiskit-ibmq-provider
python38Packages.qiskit-ignis
python39Packages.pc-ble-driver-py
python39Packages.qiskit-aer
python39Packages.qiskit-ibmq-provider
python39Packages.qiskit-ignis
spdlog (spdlog_1)
vowpal-wabbit
waybar

I would have liked to see the patch borrowed from vcpkg that I described in the linked issue. It seems like a usability win.

I would have liked to see the patch borrowed from vcpkg that I described in the linked issue. It seems like a usability win.

Is this line in the apkgbuild related? https://git.alpinelinux.org/aports/tree/community/spdlog/APKBUILD#n34

Yes, I think it is addressing the same issue.


Edit Stage Workflow

Try editing a stage from the see more panel. Let me know if you have any concerns.

should we add an alert showing what got updated?

Updated form titles for edit trip and edit stage:

Adjust Course changed to Adjust Trip and Adjust Plan

Added minor fixes to:

generateStage prompt to enforce preferences, and to get places identified by google maps
passing newStageResponse.newStage.stageLocation in StageController to improve response sent to google api for fetching coordinates (was having undefined issues with stageLocation previously with some edit stage)


[5.3] XFAIL test/Interpreter/metadata_access.swift on arm64e

The test manipulates raw pointers some of which might be signed and therefore it fails on arm64e

@swift-ci Please test


Create multiple entries through yaml

Signed-off-by: Mohammed Abdi<EMAIL_ADDRESS>

Moved to another PR https://github.com/spiffe/tornjak/pull/60


Update Campaign Household Mailing List report button to work in both Lightning and Classic

Critical Changes
Changes
The old "NPSP Campaign Household Mailing List" report included with the NPSP Households package is being replaced with a new version of the report that works properly in both the Salesforce Classic and Lightning user interfaces. The old report will still exist in custom orgs, but will not be used with the Household Mailing List custom button. If a custom organization has modified the older report, those changes will need to be applied to the new report.
Issues Closed
Fixes #2324
New Metadata
Reports/Nonprofit Edition Reports/NPSP Campaign Household Mailing List V2
Deleted Metadata

I'm wondering if it's worth holding off merge on this feature until next sprint when we do the underlying package update, which will then allow deleting the old deprecated report. I hate having to tell admins "Update this new report with stuff from the old report, then wait a few weeks before you can delete the old one." Thoughts @force2b @judisohn @smarovich ?

@njjc Guess what? There is nothing I can see that prevents the user from deleting the report right now. I fired up a scratch org with the managed release, went to a managed report, hit Delete and it's gone.

So I think we should do it in the underlying only to prevent it in new orgs, but it doesn't seem to matter for existing customers.

@force2b @smarovich

Yeah. That makes sense based on this doc. Reports are subscriber deletable even if the report isn't removed from the original package. https://developer.salesforce.com/docs/atlas.en-us.packagingGuide.meta/packagingGuide/packaging_packageable_components.htm#packaging_packageable_components

Wonderful, maybe let's add to the release notes that users can safely delete the old one once the new one has been updated, if applicable?

@smarovich See comments above. Maybe 'Note that If a customer organization has modified the old report, those changes will need to be applied to the new report. Once the changes are applied to the new report and NPSP Settings updated in People > Households to reference the new v2 report, the old "NPSP Campaign Household Mailing List" can be safely deleted.' What do you think?

@judisohn and @smarovich The settings won't need to be updated by the User. I added code to the post install script to do that for them.


Add swift_versions for CocoaPods 1.7.0 & Swift 5.0

CocoaPods 1.7.0 adds swift_versions for libraries to support multiple Swift versions.
Since this library supports both Swift 4.2 and 5.0, I suggest adding this property in podspec.

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


Gantt backgroundColor type definition is set to string instead of object

From the original documentation, setting the backgroundColor should be something like backgroundColor: {fill: "#ccc"}

However, inside the ChartWrapperOptions, the backgroundColor is defined as a string, not as object. Hence, setting the property as described in the documentation yelds
TS2769: No overload matches this call.   Overload 1 of 2, '(props: Readonly<ReactGoogleChartProps>): Chart', gave the following error.     Type '{ fill: string; }' is not assignable to type 'string'.   Overload 2 of 2, '(props: ReactGoogleChartProps, context?: any): Chart', gave the following error.     Type '{ fill: string; }' is not assignable to type 'string'.

For what is worth, ignoring any errors, setting backgroundColor: "#ccc won't work. However, backgroundColor: {fill: "#ccc"} does work.
My temporary workaround: backgroundColor: ({fill: "#ccc"} as unknown) as string

Is this still the only viable workaround? This is the only syntax I have found that seems to work.


Adding Graph Traversal Algorithms

🚀 Feature
I would love to work on Breadth-First Search (BFS) and Depth-First Search (DFS) Graph traversal algorithms in C as a part of DWOC
(A clear and concise description of what the feature is.)
Have you read the Contributing Guidelines on Pull Requests?
(Write your answer here.)
Yes
Motivation
Graphs are a powerful and versatile data structure that easily allows you to represent real-life relationships between different types of data (nodes). Graphs are one of the most difficult topics of data structure and can be asked in interviews. I will be working on-
1.DFS
2.BFS
(Please outline the motivation for the proposal.)
Pitch
(Please explain why this feature should be implemented and how it would be used.)
Graph traversal is a technique used for searching a vertex in a graph. It is also used to decide the order of vertices is visited in the search process. It is also used to find the edges to be used in the search process without creating loops. In these ways they can be used

Hi, I would like to work on this . Also let me know if this in included in DWOC2020. Thank you

I would like to work on this issue under DWOC

I would like to work on this issue in java under DWOC

Hi, I would like to work on this issue in C++, please assign this issue to me and add C++ label to it

I would like to work on this issue under DWOC

in C

I would like to work on this issue under DWOC

in C


[ZEPPELIN-6007] Enhance release scripts for tar shasum commands detection

What is this PR for?
When untar the 0.11.1 RC1 tgz on Linux, I found the following warnings. It's actually caused by macOS tar's default behavior, see more details at SPARK-43395
➜  zeppelin-0.11.1-rc1 tar -xzf zeppelin-0.11.1-bin-all.tgz
tar: Ignoring unknown extended header keyword 'LIBARCHIVE.xattr.com.apple.provenance'
tar: Ignoring unknown extended header keyword 'LIBARCHIVE.xattr.com.apple.provenance'
tar: Ignoring unknown extended header keyword 'LIBARCHIVE.xattr.com.apple.provenance'
tar: Ignoring unknown extended header keyword 'LIBARCHIVE.xattr.com.apple.provenance'
tar: Ignoring unknown extended header keyword 'LIBARCHIVE.xattr.com.apple.provenance'
tar: Ignoring unknown extended header keyword 'LIBARCHIVE.xattr.com.apple.provenance'

Similarly, shasum is also different on macOS and Linux.
What type of PR is it?
Improvement
Todos

[ ] - Task

What is the Jira issue?
ZEPPELIN-6007
How should this be tested?
Manually test.
Screenshots (if appropriate)
Questions:

Does the license files need to update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

cc @jongyoul, this is minor issue and I don't think it's a release blocker

Thank you for checking it. BTW, how can we handle it permanently?

I checked the comment on the spark's issue. :-) Thank you!

@jongyoul this should be a permanent solution, and the failed test should be irrelevant.

@jongyoul this should be a permanent solution, and the failed test should be irrelevant.

Yes, I know it. I just wonder why some test fails :-)

@jongyoul the Python 3.8 test failed consistently, maybe caused by deps dynamic version


merge package from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Shift Gradebook-related to GradebookModel

removed gradebook related codes in StorageController
moved them to Gradebook Model
linked commands to Gradebook Model
working codes for add, delete and list Gradebook commands

Coverage increased (+0.6%) to 78.568% when pulling 346a2b930067c02db63ee3a9b512c5fc3c449067 on tristyxxnana:master into 027da75a7ca17f8cfc7ea682ba2208c403df7bbf on CS2113-AY1819S1-T16-1:master.


webapp: Hostname does not exist error on ssl bind

Describe the bug
Starting in 2.20.0, this started throwing errors. (was working in <=2.19). Note that this is for a situation where the app service & app service plan are in different resource groups.
What is happening is that we are trying to bind an ssl cert to app service with cname of ABC, but instead we get an error that an unrelated hostname (XYZ) does not exist (It actually does exist, making this a doubly-fun error).
It looks like something in az webapp config ssl bind is using the last ssl cert in the list rather than the one that corresponds to the given app service / cert thumprint. (If I run az webapp config ssl list, the hostname XYZ that appears in the error is the last in the list.)
Command Name
az webapp config ssl bind
Errors:
Hostname 'XYZ.domain.com' does not exist.

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
Here is how the certificate thumprint is selected:
APP_FQDN=ABC.domain.com
THUMBPRINT=$(az webapp config ssl list -g $PLAN_RESOURCE_GROUP --query "[?name=='$APP_FQDN'].thumbprint | [0]")
and here is the command that errors:
az webapp config ssl bind --resource-group $RESOURCE_GROUP --name $APP_SERVICE --certificate-thumbprint $THUMBPRINT --ssl-type SNI
Same results if the --ids arg is used instead.
Expected Behavior
Was working in 2.19
Environment Summary
Note, this is also occurring in multiple Azure DevOps pipelines (just started recently)
macOS-10.13.6-x86_64-i386-64bit
Python 3.8.8
Installer: HOMEBREW

azure-cli 2.20.0

Extensions:
front-door 1.0.11
aks-preview 0.5.4
webapp 0.3.1
application-insights 0.1.13

Additional Context

webapp

2.20.0 return success but it doesn't bind the certificate on the webapp.
I have downgraded to 2.19.1 and it's working properly.

This issue also happens if both the app service plan & app service are in the same resource group. This seems to be happening due to a recent change in 2.20.0 version.
Tried with version 2.19.0 and it worked perfectly fine.

Please escalate this issue accordingly as there is no workaround to bypass this error, using --name or --ids doesn't work.
If working locally, one can downgrade to 2.19.1 and resolve it but there is no workaround for Azure DevOps as we can't specify a version for the AzureCLI task.

@panchagnula
We got some cases related to this

@calvinsID can you take a look at this especially since this states that this is a regression from this change https://github.com/Azure/azure-cli/pull/16778

@calvinsID can you take a look at this especially since this states that this is a regression from this change #16778

I got this same error with az cli version 2.21, suggesting that the issue is not fixed.

@mpowrie the fix should be in the next version, which will be on cloud shell 04/09 and officially released 04/13. Can you please try again with the updated version once its out? sorry for the inconvenience

Thanks @calvinsID will do.


Because files are mounted, mounting from a filesystem using CRLF will cause failures

root@e0f6acee0d14:/go/src/github.com/telemetry-reference-tools# cmd/idrac-telemetry-receiver.sh
cmd/idrac-telemetry-receiver.sh: line 1: $'\r': command not found
cmd/idrac-telemetry-receiver.sh: line 2: $'\r': command not found
cmd/idrac-telemetry-receiver.sh: line 3: $'\r': command not found

In my case I was deving from Windows sync'd to a remote Linux system. Because the code is mounted instead of being container-native, if the saved format converts line endings to CRLF the code fails.
We should ensure that git saves all files with Unix-style line endings.
If we choose to include a startup script it should check that all required files use only LF instead of CRLF

I'll start taking a look.

Eh I'm going to close this one. Now that I look back at it - it is a problem, but it's more of a problem with my dev environment. not worth burning time on

Thanks Grant


car docs: use experimental long limits

On some platforms (namely GM), we are able to allow lower enable speeds when using openpilot longitudinal. This passes experimental_long to the car interfaces which currently does not change any limits (until https://github.com/commaai/openpilot/pull/28708 is merged).

@adeebshihadeh are you fine with showing the best limits possible/when using openpilot longitudinal? When using stock ACC, the camera still restricts to min 5 kph or stopped here


File counter

Explain the bug
Write a clear description of what the bug is.
To reproduce

Go to '....'
Click on '....'
Scroll down to '....'
See the error

Expected behavior
Write a clear description of what you expected.
Logfile
Upload the log file here for us to understand your issue better.

You can access it from Settings->About->Open log location.
or
Copy the debug.txt and debug_fulltrust.txt from the following directory, and upload the files here.
%localappdata%\Packages\49306atecsolution.FilesUWP_et10x9a9vyk8t\LocalState

Screenshots
Add screenshots to help explain your problem if needed.
System Information

OS Version: [e.g. Windows 10 20H2 19042.804] (Press WIN + PAUSE/BREAK, use the copy button at the bottom)
App version: [e.g. v1.0] (In the app, go to Settings -> About, the version is shown at the top)

Additional comment
Add any other comment about the problem here. Does this problem happen again after restarting the app?
I sometimes experience that the counter of elements in a folder (bottom left corner) doesn't show the real number. Oftentimes it stays on one number (today it is 29) every time I open a folder. When I refresh by clicking F5, the correct number gets displayed.

Same as #4281?

Similar, my counter shows the true number in Detail View, but not in all the other ones, it only corrects itself when I press F5.

Is this still an issue in v1.5?


WIP: Multibox Support

Early draft of multibox support.

Need to find a way for the ArcDps to either handle multiple instances or have it gracefully not start if there is already an instance listening.

Just curious, what is still missing here?

https://discordapp.com/channels/531175899588984842/536970543736291346/715928883400147065

Eh, just one or two to clean up the method used to resnap (it'll show on the first proc at launch until you click into the GW2 window it'll end up being assigned to - doesn't cause any problems, but I can at least make it slightly cleaner).

Working on this now.

Closed in favor of #247


PHP version updated in travis.yml

The latest php version update into travis.yml and chacked with travis.
it build pass upto php 7.0 and hhvm

ping  @weierophinney

I've already done this on the develop branch, from which I'll be taking a 2.0 release in the coming days.


[WIP] Global Default Address Pool feature support

This feature allows user to specify list of subnets for global
default address pool. User can configure subnet list using
'swarm init' command. Daemon passes the information to swarmkit.
We validate the information in swarmkit, then store it in cluster
object. when IPAM init is called, we pass subnet list to IPAM driver.
Signed-off-by: selansen<EMAIL_ADDRESS>
- What I did
- How I did it
- How to test it
- Description for the changelog

@thaJeztah , Modified API params as per our discussion.

@thaJeztah , could you pls approve it ? "Request change" still not revoked.

CI failed at the same place randomly many times. so  I didnt update it

re-ran and CI passed now.

Thanks a lot @thaJeztah @anshulpundir for helping me to close it.


Add link to cdk-sqlserver-seeder project

Issue #, if available:
Description of changes:
Add link to cdk-sqlserver-seeder project
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Ah, I didn't meant doing that as part of this PR, thought it was merged already :-\ Please let me know if you want to separate this things from each other.
@eladb I made a number of changes to prepare awesome-cdk list to submission to the central awesome repo:

made the changes to pass awesome-lint warnings (mostly dots and dashes)
added CC0 license to the repo (so it is shown on GitHub project page)
added GitHub Actions flow to run awesome-lint for each PR/push into the repo

To successfully submit awesome-cdk to the main list we also need to do the following (according to the guidelines):

make default branch main, not master as it is now
add topics to the repository (awesome and awesome-list are mandatory, the rest is optional but desired). Example from my fork:

@kolomied merged, but I am still seeing an error: https://github.com/eladb/awesome-cdk/runs/888975212?check_suite_focus=true

@eladb just raised #55 to address this


Guided Missile description fix/change

There was a slight error in the description of the Guided Missile on the home page.

Thanks for the fix!

No problem!


Noise produced in region of negative infinity, doesn't happen with orca

I've recently realised that plotly no longer supports orca and seen I should be using kaleido. I'm using Surface and Mesh3d and in both I'm doing something similar, but I only get this problem with Mesh3d. Essentially, I create some field on the surface/mesh, and then I set the value outside some region to a large negative number so that the region can be seen easily. In both cases I export as png as well as pdf and the problem is the same for both, and I do not get it in the browser.
This is an example of what I mean with the Surface example. Here I have the topography of the Earth and then the region outside South America is set to a large negative value, and it appears white as desired.

Now if I do the same for some mesh, instead of the white I'm expecting I get noise. Here is a field on a Mesh3d of Homer, then I isolate the head as the region and I get the noise. If I use the orca engine, I do not get this issue.

Is there a way to fix this, or is it a bug? I'll have to revert to orca in the meantime.

Hi @paddyroddy, thanks for the report. Would you be able to provide full code for a simple example that reproduces this behavior?

Here's some code which reads a mesh of homer from this repo. The library I'm using to read the mesh is igl which can be installed via: conda install -c conda-forge igl.
import numpy as np
import plotly.offline as py
from igl import read_triangle_mesh
from plotly.graph_objs import Figure, Mesh3d

def kaledio_bug(
    engine: str,
    mesh: str = "homer.off",
    large_negative_value: float = -1.56e30,
    region_ymin: float = 0.15,
) -> None:
    """
    minimal working example to reproduce the Kaleido bug
    """
    # read in mesh
    vertices, faces = read_triangle_mesh(mesh)

    # create some region
    region = vertices[:, 1] >= region_ymin

    # create dummy field
    function_on_mesh = np.ones(vertices.shape[0])

    # set value outside region to negative infinity
    masked_region = np.where(region, function_on_mesh, large_negative_value)

    # create plot
    data = [
        Mesh3d(
            x=vertices[:, 0],
            y=vertices[:, 2],
            z=vertices[:, 1],
            i=faces[:, 0],
            j=faces[:, 1],
            k=faces[:, 2],
            intensity=masked_region,
            cmin=-1,
            cmax=1,
        )
    ]
    fig = Figure(data=data)
    py.plot(fig)

    # bug happens kaledio but not orca
    for file_type in {"png", "pdf"}:
        fig.write_image(f"homer_{engine}.{file_type}", engine=engine)

if __name__ == "__main__":
    for engine in {"kaledio", "orca"}:
        kaledio_bug(engine)

The resulting plots look like:
Kaleido

Orca

I've found if I set large_negative_value to some less small number, i.e. -1e5 then it's okay. However, when I don't normalise the dataset sometimes this wouldn't be a small enough value, so not ideal.


aws-c-common: 0.3.11 -> 0.3.15

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/aws-c-common/versions.
meta.description for aws-c-common is: '"AWS SDK for C common core"'.
meta.homepage for aws-c-common is: '"https://github.com/awslabs/aws-c-common"
Release on GitHub
Compare changes on GitHub

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
/bin/sh passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 0.3.15 with grep in /nix/store/iwz6ff4zrmw9wwz68wk7jaxfmd1475x9-aws-c-common-0.3.15
directory tree listing: https://gist.github.com/6e5fbb7f0f1f2cff3144108dd3865c30
du listing: https://gist.github.com/e445234db8af105d9f0f6d41dc389b1b

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

183 total rebuild path(s)
51 package rebuild(s)
51 x86_64-linux rebuild(s)
47 i686-linux rebuild(s)
38 x86_64-darwin rebuild(s)
47 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
aws-c-common
aws-c-event-stream
aws-sdk-cpp
bundix
cabal2nix
common-updater-scripts
dep2nix
discover
disnix
disnixos
fusionInventory
gnome3.gnome-packagekit
gnome3.gnome-software
gnome3.simple-scan
go2nix
haskellPackages.nix-paths
hydra
lispPackages.quicklisp-to-nix
lispPackages.quicklisp-to-nix-system-info
nix
nix-bundle
nix-du
nix-exec
nix-index
nix-pin
nix-plugins
nix-prefetch
nix-prefetch-bzr
nix-prefetch-cvs
nix-prefetch-docker
nix-prefetch-git
nix-prefetch-hg
nix-prefetch-scripts
nix-prefetch-svn
nix-review
nix-serve
nix-update-source
nixFlakes
nixStable
nixUnstable
nixui
osquery
packagekit
packagekit-qt
plasma5.discover
pypi2nix
python37Packages.nixpkgs
python37Packages.pythonix
simple-scan
vgo2nix

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/iwz6ff4zrmw9wwz68wk7jaxfmd1475x9-aws-c-common-0.3.15 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A aws-c-common https://github.com/r-ryantm/nixpkgs/archive/0c67ea6eead23cd18d6093d06b860c543796a205.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/iwz6ff4zrmw9wwz68wk7jaxfmd1475x9-aws-c-common-0.3.15
ls -la /nix/store/iwz6ff4zrmw9wwz68wk7jaxfmd1475x9-aws-c-common-0.3.15/bin

cc @orivej @edolstra for testing.

@GrahamcOfBorg build aws-sdk-cpp

Obsolete (current version is 0.4.12)


Consider cleaning npm cache in docker build

Acceptance criteria

[ ] reduced docker image size

Unnecessary. We do not pay for the storage, so simply ignore.


Simplify async logic

Await the gather instead of accessing the event loop directly.
We should probably avoid accessing the event_loop directly.

Actionable comments posted: 0
Actionable comments outside the diff hunks (2)

validator/validator/validator.py (2)> Line range hint 24-24: The sys module is imported but not used. Consider removing this unused import to clean up the code.

- import sys

Line range hint 436-436: The logging statement uses an f-string without placeholders. Consider simplifying this to a regular string for clarity.
- bt.logging.warning(f"Scores contain NaN values. This may be due to a lack of responses from miners, or a bug in your reward functions.")
+ bt.logging.warning("Scores contain NaN values. This may be due to a lack of responses from miners, or a bug in your reward functions.")

Will get this in another PR


Allow search outside of viewport

The JSON is highlighted just in the viewport area to allow larger files to be loaded and highlighted without delay, but I miss the fact that the search was impacted occurring just in the highlighted area. This must be fixed asap.

The previous version was working just fine. The Search capability is by far the feature I used the most.

I will fix this today


Deploy and test CSV and JSON aggregate endpoints

This has been deployed in production, but still some testing needs to be done.

Rolled back on ooni-sysadmin e9c6eee8b712f3e11ff8ac7f0352c9868ab50f16

Deployed on yesterday


Suggestion: Icon selection

Suggestion:
With each recipe, there is a pizza icon. This is fine, but looks a little silly next to my dessert recipe. Perhaps if we could choose from a selection(?)
Also, for 'Mass Create,' I now realize the icon is supposed to be the back of a truck being loaded, but it took me a while. Maybe consider an alternative.

Hi @GreyMoth and thanks for your proposal.
For the icons I'm dependent on FontAwesome which is a pretty huge collection (10K in the free version) but stays generalist.
I'm open to suggestions though if you can make a list of the icons from this collection that would fit the needs we have in reciphpes. Then I'll see what I can do about them.


[Feature Request] Selected and disabled checkbox-button

Existing Component
Yes
Component Name
Checkbox-button
Description
A checkbox-button doesn't have a style for selected and disabled.
When we use a normal checkbox component, we can distinguish a disable one of selected from not selected.
I hope checkbox-button has a style for the state like checkbox.

A checkbox-button doesn't have a style for selected and disabled.

The styles of these two buttons are different. You can also use your style to overwrite default style.


Determine deployment environment within VA

DSVA vs VAEC (we can't use Cloud.gov)
Are we allowed to just define our own lower environments?

@anushyaprasad to follow up with Alex

We've agreed to use the TW AWS account to build until we're a couple weeks from going to prod; we'll also start applying for a VAEC account.
In a month, we'll revisit this and see if it's worth going into DSVA to get the benefit of whatever we have to deploy.


Add info about llama.cpp support to readme

Thanks for the great work here.
I implemented LLaVA support in llama.cpp and this pr simply adds a notice to the readme.
See it in action here.

Thank you so much for the great contribution! It is definitely an exciting news!
Would like to discuss with you about a few things regarding the output quality to see if there are room for improvements, as I believe people would be more excited if the output quality are as good as the one we see in the web demo! We can discuss that in your PR: https://github.com/ggerganov/llama.cpp/pull/3436#issuecomment-1758925801

Just merged this. Cheers! Also let's continue to see if we can figure out the quality issue with the 13b model in llama.cpp repo :) Thanks for the great work again!

Thanks for merging! Yes I'll continue to work on this --it's just amazing and it would be great if we could achieve a level of performance comparable to the one in the demo :)


DEPENDENCIES

I am using it for a school project but when i try to simply install it, i have a whole bunch of dependencies issues, with the version of three and other errors.

Hi @dairo95
We have officially released the new library components on September 20 2023. This library substitutes web-ifc-three and web-ifc-viewer. Both WIV and WIT will remain up, but they will be deprecated and won't be maintained any longer. You can find the new docs here.
All our efforts are going towards components now. The API is very similar, so I strongly suggest you make the leap and start using it. If you still face this issue with it, you can open an issue there and we'll take a look.


Swap Gradle language from Groovy to Kotlin

Fix usage of Java 17 API in the build
Swap the build language from Groovy to Kotlin

I also noticed that when I run this, I get a warning that I'm not seeing on the master branch:

Task :model:compileJava
/Users/cmoesel/git/cql/pr1413/Src/java/model/build/generated/sources/model/main/java/org/hl7/fhir/Identifier.java:108: warning: [unchecked] Possible heap pollution from parameterized vararg type JAXBElement<? extends Element>
public Identifier withRest(JAXBElement<? extends Element> ... values) {

It's probably not a big deal, but I'm mentioning it since it does appear to be new.

Huh. My guess is that we were previously excluding the generated sources from compiler warnings. I don't know what change would have caused this though. I will investigate.

@cmoesel - The heap pollution was a real issue. The xjc generation was running for all the classes in the schema in the model project, not just those relevant to model.


Made use of null-coalescing assignment operator where appropriate

Looks good, but some warnings were introduced from the sealed changes. Could you fix those warnings please?

Sure. I hadn't noticed so thanks for pointing it out

thanks! It looks like there are still a few more warnings in the text tool


Logperf7

@OliveGerste : Tobias, can you help?
We have a smartcharging test failing ... I think I didn't merge properly some changes, but I do not find which one.
Can you please have a look to the failing test?
Any hint would be helpful!

@OliveGerste : Tobias, can you help? We have a smartcharging test failing ... I think I didn't merge properly some changes, but I do not find which one. Can you please have a look to the failing test? Any hint would be helpful!

Hi @ClaudeROSSI,
Not an easy one to be honest. The fault is not on your side:
Short answer: Performance is too good now.
Long answer: The test assumes that the first transaction starts shortly before the second one. Normally this worked because the code execution took more time, so that we had 1 second difference between the transaction starts.
Due to the performance increase they start at the exact same time and the parameters are exactly the same which leads to a other order how the the transactions are prioritised.
I provided a PR to fix this https://github.com/sap-labs-france/ev-server/pull/4173
Let me know if this is sufficient.


fix #2914

Codecov Report

Merging #2936 into master will decrease coverage by 0.04%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master    #2936      +/-   ##
============================================
- Coverage     80.52%   80.48%   -0.05%
+ Complexity     7230     7222       -8
============================================
  Files           145      145
  Lines         27133    27122      -11
  Branches       6492     6492
============================================
- Hits          21849    21829      -20
- Misses         3403     3408       +5
- Partials       1881     1885       +4

Impacted Files
Coverage Δ
Complexity Δ

.../java/com/alibaba/fastjson/parser/JSONScanner.java
75.98% <ø> (-0.29%)
503 <0> (-5)

...ava/com/alibaba/fastjson/parser/JSONLexerBase.java
71.38% <100%> (-0.01%)
829 <0> (+1)

...ava/com/alibaba/fastjson/serializer/DateCodec.java
87.05% <0%> (-1.77%)
40% <0%> (-1%)

...com/alibaba/fastjson/parser/JSONReaderScanner.java
72.61% <0%> (-1.28%)
44% <0%> (-1%)

...main/java/com/alibaba/fastjson/util/FieldInfo.java
86.2% <0%> (-0.35%)
90% <0%> (-1%)

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 370c718...97daf58. Read the comment docs.


Tfrecords to parquet

Example + function to convert tfrecords to parquet

@benfred updated to write each tfrecord to one parquet file by using cuDF
Issues with reading the parquet file with cuDF: https://github.com/rapidsai/cudf/issues/9216

rerun tests


Support default arguments in function blocks

Describe the desired feature
Allow components and extensions to define default values for any/all/none of the parameters.
Give an example of how this feature would be used
This will ease the use of functions with many parameters. Users won't have to fill every parameter by themselves. This will also allow extensions to define a default argument for functions.
Why doesn't the current App Inventor system address this use case?
It does with the Notifier.ShowChooseDialog block but that is hardcoded https://github.com/mit-cml/appinventor-sources/blob/cc121a481d7edd75878f24c3ccac70fa8584daa8/appinventor/blocklyeditor/src/drawer.js#L603

Why is this feature beneficial to App Inventor's educational mission?
Make blocks easy to use and save users time.

It might also be worth looking into using shadow blocks for these default parameters

It might also be worth looking into using shadow blocks for these default parameters

@Vishwas-Adiga
What are shadow blocks?

@Vishwas-Adiga
What are shadow blocks?

We have previously discussed using shadow blocks among the team and the power users. At the time we decided against it. At the very least, there are a number of changes here that need to be made to support annotating this information in the parameters and storing that information in simple_components.json. Drawer.js will also need to be modified to accommodate this. We'll also want to change the existing components to use this new approach rather than the special code paths currently used. All these things can be done before a decision on whether shadow blocks are used or not.

We have previously discussed using shadow blocks among the team and the power users. At the time we decided against it. At the very least, there are a number of changes here that need to be made to support annotating this information in the parameters and storing that information in simple_components.json. Drawer.js will also need to be modified to accommodate this. We'll also want to change the existing components to use this new approach rather than the special code paths currently used. All these things can be done before a decision on whether shadow blocks are used or not.

Before anyone takes on this task I'd prefer that we discuss the design first w.r.t. the annotations and changes to simple_components.json.

Before anyone takes on this task I'd prefer that we discuss the design first w.r.t. the annotations and changes to simple_components.json.

Should we be asking people to create design docs?
== Hal
Hal Abelson
<EMAIL_ADDRESS>Prof. of Comp. Sci. and Eng.
MIT Dept. of Elec. Eng. and Comp. Sci.
On Thu, Jan 21, 2021 at 10:36 AM Evan W. Patton<EMAIL_ADDRESS>wrote:

Before anyone takes on this task I'd prefer that we discuss the design
first w.r.t. the annotations and changes to simple_components.json.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mit-cml/appinventor-sources/issues/2384#issuecomment-764727237,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGAXN522WDD5IXRVAVTDGLS3BCVVANCNFSM4WMSSPQQ
.

Should we be asking people to create design docs?
== Hal
Hal Abelson
<EMAIL_ADDRESS>Prof. of Comp. Sci. and Eng.
MIT Dept. of Elec. Eng. and Comp. Sci.
On Thu, Jan 21, 2021 at 10:36 AM Evan W. Patton<EMAIL_ADDRESS>wrote:

Before anyone takes on this task I'd prefer that we discuss the design
first w.r.t. the annotations and changes to simple_components.json.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mit-cml/appinventor-sources/issues/2384#issuecomment-764727237,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGAXN522WDD5IXRVAVTDGLS3BCVVANCNFSM4WMSSPQQ
.

@halatmit Yes, I'd like to see a more formal document of what this will look like prior to investing a lot of time implementing it.
@pavi2410 Do you have concrete thoughts on this? I have my own and can start drawing something up.

@halatmit Yes, I'd like to see a more formal document of what this will look like prior to investing a lot of time implementing it.
@pavi2410 Do you have concrete thoughts on this? I have my own and can start drawing something up.

I do not have any concrete thought on this except a few ideas on the components side.
Here's how Thunkable X implements this using shadow blocks

I do not have any concrete thought on this except a few ideas on the components side.
Here's how Thunkable X implements this using shadow blocks

I've started a design doc here: https://docs.google.com/document/d/1is90WHxQxX3g6wiq46Vnzb6QkDeX1e4tw7X1bBk2-pk/edit#

I've started a design doc here: https://docs.google.com/document/d/1is90WHxQxX3g6wiq46Vnzb6QkDeX1e4tw7X1bBk2-pk/edit#

Could this be extended to support block properties as well? Or is it beyond the scope for now?

Could this be extended to support block properties as well? Or is it beyond the scope for now?

I'm not sure much if anything needs to be done for properties. We should be able to infer this information from the designer property default value and the type information for the property. I did a prototype of this back in 2017 in fact.

I'm not sure much if anything needs to be done for properties. We should be able to infer this information from the designer property default value and the type information for the property. I did a prototype of this back in 2017 in fact.

Actually I think I did most of the work to support this last summer =) When I created the system to support dropdown blocks I tried to make it extensible enough so that new annotations could be defined and associated with new types of helper blocks (eg booleans, text inputs, etc). See my documentation on Adding New Types of Helper Blocks to the Blocks Editor. You should be able to create a parameterized annotation (representing a helper block) that takes in information about the default value and displays it on the helper block.
But I could also be missing the point of this issue hehe.
If I'm not missing the point, I recommend closing this issue in favor of creating issues for specific types of helper blocks & their associated annotations.
Also with regard to shadow blocks, during the summer I was told that the main issue with them was that they enlarged the save file size, because each shadow block needs to have at least two xml nodes associated with it (the block node and the field value node). There was a bit of talk about implementing some custom behavior so that shadow blocks wouldn't save their values (eg if you replaced a shadow with a real block, the shadow would forget the value input into its field) but we decided it was outside the scope of my summer project.

Actually I think I did most of the work to support this last summer =) When I created the system to support dropdown blocks I tried to make it extensible enough so that new annotations could be defined and associated with new types of helper blocks (eg booleans, text inputs, etc). See my documentation on Adding New Types of Helper Blocks to the Blocks Editor. You should be able to create a parameterized annotation (representing a helper block) that takes in information about the default value and displays it on the helper block.
But I could also be missing the point of this issue hehe.
If I'm not missing the point, I recommend closing this issue in favor of creating issues for specific types of helper blocks & their associated annotations.
Also with regard to shadow blocks, during the summer I was told that the main issue with them was that they enlarged the save file size, because each shadow block needs to have at least two xml nodes associated with it (the block node and the field value node). There was a bit of talk about implementing some custom behavior so that shadow blocks wouldn't save their values (eg if you replaced a shadow with a real block, the shadow would forget the value input into its field) but we decided it was outside the scope of my summer project.

@BeksOmega Your documentation I do think is helpful for the annotations piece, but I am imagining that these would not be new blocks but that the engine would construct the constructor block for the given type (logic_boolean, text, math_number, etc.) rather than defining a brand new block.

@BeksOmega Your documentation I do think is helpful for the annotations piece, but I am imagining that these would not be new blocks but that the engine would construct the constructor block for the given type (logic_boolean, text, math_number, etc.) rather than defining a brand new block.

@BeksOmega Your documentation I do think is helpful for the annotations piece, but I am imagining that these would not be new blocks but that the engine would construct the constructor block for the given type (logic_boolean, text, math_number, etc.) rather than defining a brand new block.

Coolio, if I understand what you're saying, that should work fine! You'd just skip section 5 of the doc and move straight to section 6. For example:
Blockly.Util.xml.helperKeyToXML= function(helperKey) {
  switch(helperKey.type) {
    case 'OPTION_LIST':
      return this.blockTypeToXML('helpers_dropdown', {key: helperKey.key});
    case 'BOOLEAN':
      // You could either pass the default value as a mutation (like above),
      // and add a mutator to the logic_boolean block.
      // Or you could add a function to utils_xml.js to create field XML.
      return this.blockTypeToXML('logic_boolean');
  }
}

@BeksOmega Your documentation I do think is helpful for the annotations piece, but I am imagining that these would not be new blocks but that the engine would construct the constructor block for the given type (logic_boolean, text, math_number, etc.) rather than defining a brand new block.

Coolio, if I understand what you're saying, that should work fine! You'd just skip section 5 of the doc and move straight to section 6. For example:
Blockly.Util.xml.helperKeyToXML= function(helperKey) {
  switch(helperKey.type) {
    case 'OPTION_LIST':
      return this.blockTypeToXML('helpers_dropdown', {key: helperKey.key});
    case 'BOOLEAN':
      // You could either pass the default value as a mutation (like above),
      // and add a mutator to the logic_boolean block.
      // Or you could add a function to utils_xml.js to create field XML.
      return this.blockTypeToXML('logic_boolean');
  }
}

Question: Should we allow default values that are not primitive or complex?
IMO, we shouldn't. What is your take on this?

Question: Should we allow default values that are not primitive or complex?
IMO, we shouldn't. What is your take on this?

Question: Should we allow default values that are not primitive or complex?
IMO, we shouldn't.

Hmm I don't really have an opinion. But I am curious, why don't you think they should be allowed? Is it just for XML size reasons, or is it something else? Also, just to be clear, by not primitive/complex do you mean things like lists/dictionaries?

Question: Should we allow default values that are not primitive or complex?
IMO, we shouldn't.

Hmm I don't really have an opinion. But I am curious, why don't you think they should be allowed? Is it just for XML size reasons, or is it something else? Also, just to be clear, by not primitive/complex do you mean things like lists/dictionaries?

I want to give a proposal to the developers, It is very useful feature in Extension making, Set a default value of Property Blocks in @DesignerProperty.


Implement Messages

On branch messages-without-styling.
Todos:

[x] Select a room
[x] Send messages
[x] Send images
[ ] Delete messages
[ ] Create new room
[ ] Invite a user to the room
[ ] Leave room
[ ] Display name of the user instead of IDs
[ ] Add special message for 'user joined', 'user left'
[ ] Style

When styling, please do not change the given ids of HTML elements.

Also, for the ease of debugging, I have made the page automatically log in to a test account(khs1778@skku.edu).


Fix the double border around code snippets

When we add a code snippet to a post, there's a strange double border around it.
We need to remove one of the borders.
Acceptance Criteria:

The double border is removed from blog code snipppets
A single border is preserved

We'll likely need to change some CSS in _sass/_highlights.scss to target just a single element with the border.

Offending page: https://engineering.himaxwell.com/checking-for-third-party-cookies-in-2021/

Screenshot:

Closing in favor of https://github.com/himaxwell/maxwell/issues/16504


Possible to import redundant interface connections

Assume you have a connection between server1 eth0 and server2 eth0. The validation logic currently in place will allow a user to import a connection in the reverse direction:
server2,eth0,server1,eth0,connected

It should not be possible to create a redundant InterfaceConnection.

Disregard. I had disabled a portion of the validation for testing.


[FIX] explicitly use bash instead of sh

Description
Explicitly use bash instead of relying on sh symlinking to it and therefore causing an error for shells where the [[ keyword is not supported
closes #3832
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[x] Attached issue to pull request
[x] Changelog entry
- [ ] Type annotations are present
[x] Code is clear and sufficiently documented
- [ ] No (preventable) type errors (check using make mypy or make mypy-diff)
- [ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
- [ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

Reviewer Checklist:

[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Code is clear and sufficiently documented
[ ] Correct, in line with design

Processing this pull request

Merged into branches master in 189b94435949213a56004b3864f7f0fc2dd2fb25

Processing #4174.

Processing #4174.

Processing #4173.


QA-12760: use context.id to differentiate upload actions

JIRA

https://jira.jahia.org/browse/QA-12760
Description
use context.id to differentiate upload actions, define useEffect dependencies
Tests
The following are included in this PR

[ ] Unit Tests (Most changes should have unit tests)
[ ] Integration Tests

Checklist

I have considered the following implications of my change:

[ ] Security (in particular for changes to authentication, authorization, data fetching, ...)
[ ] Performance
[ ] Migration
[ ] Code maintainability

Documentation

[ ] Inline documentation
[ ] Internal Documentation (wiki)
[ ] User-facing Documentation

I remember now why we did not destroy the upload component, and so did not use the id - if you destroy the input after the click (so when the upload dialog appear), you cannot upload anything (the input is already destroyed when the user click effectively upload the file)


firefox-bin: 89.0.1 -> 90.0,  firefox-esr: 78.11.0esr -> 78.12.0esr

Motivation for this change
The release notes are not updated yet.
https://www.mozilla.org/en-US/firefox/90.0/releasenotes/
https://www.mozilla.org/en-US/firefox/78.12.0/releasenotes/
See also  #130019.
I have noticed that fonts in UI are changed. I'm not sure this is an intended change or not.
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

There's apparently some fontconfig regression on current NixPkgs master, reportedly fixed by https://github.com/NixOS/nixpkgs/pull/129675 so I suspect that might've caused it.


HTML5: "Could not open" blank tscn, "indirect call to null"

Godot version
3.4.stable.mono.official
System information
Windows 10, GLES2, Vulkan
Issue description
For some reason, when I change the Main Scene to anything else but my old title screen, the HTML5 export refuses to run the game at all.

Here is the console output on Firefox:
Godot Engine v3.4.stable.mono.official.206ba70f4 - https://godotengine.org tmp_js_export.js:347:16
OpenGL ES 2.0 Renderer: ANGLE (Intel(R) HD Graphics 400 Direct3D11 vs_5_0 ps_5_0, D3D11-<IP_ADDRESS>64) tmp_js_export.js:347:16
OpenGL ES Batching: ON tmp_js_export.js:347:16
 tmp_js_export.js:347:16
ERROR: Mono: Core API hash mismatch. tmp_js_export.js:362:18
   at: _init_godot_api_hashes (modules/mono/mono_gd/gd_mono.cpp:490) - Mono: Core API hash mismatch. tmp_js_export.js:362:18
Mono: Config attempting to parse: '/root/mono-installs/wasm-runtime-release/etc/mono/config'. tmp_js_export.js:347:16
Mono: Config attempting to parse: '/home/web_user/.mono/config'. tmp_js_export.js:347:16
ERROR: Cannot open file 'res://SplashScreen.tscn'. tmp_js_export.js:362:18
   at: load_interactive (scene/resources/resource_format_text.cpp:1183) - Condition "err != OK" is true. Returned: Ref<ResourceInteractiveLoader>() tmp_js_export.js:362:18
ERROR: Failed loading resource: res://SplashScreen.tscn. Make sure resources have been imported by opening the project in the editor at least once. tmp_js_export.js:362:18
   at: _load (core/io/resource_loader.cpp:271) - Condition "found" is true. Returned: RES() tmp_js_export.js:362:18
ERROR: Failed loading scene: res://SplashScreen.tscn tmp_js_export.js:362:18
   at: start (main/main.cpp:1998) - Condition "!scene" is true. Returned: false tmp_js_export.js:362:18
exception thrown: RuntimeError: indirect call to null,godot_js_main(int, char**)@:wasm-function[15324]:0x2ca1c5
main@:wasm-function[31565]:0x73169e
Godot/Module._main@http://localhost:8060/tmp_js_export.js:9:403120
callMain@http://localhost:8060/tmp_js_export.js:9:415259
SafeEngine/start/Engine</</<@http://localhost:8060/tmp_js_export.js:694:17
SafeEngine/start/Engine</<@http://localhost:8060/tmp_js_export.js:689:14
tmp_js_export.js:362:18
indirect call to null tmp_js_export.html:213:13

Here is the console output on Chromium, with a slightly different ending:
ERROR: Cannot open file 'res://SplashScreen.tscn'.
onPrintError @ tmp_js_export.js:362
tmp_js_export.js:362    at: load_interactive (scene/resources/resource_format_text.cpp:1183) - Condition "err != OK" is true. Returned: Ref<ResourceInteractiveLoader>()
onPrintError @ tmp_js_export.js:362
tmp_js_export.js:362 ERROR: Failed loading resource: res://SplashScreen.tscn. Make sure resources have been imported by opening the project in the editor at least once.
onPrintError @ tmp_js_export.js:362
tmp_js_export.js:362    at: _load (core/io/resource_loader.cpp:271) - Condition "found" is true. Returned: RES()
onPrintError @ tmp_js_export.js:362
tmp_js_export.js:362 ERROR: Failed loading scene: res://SplashScreen.tscn
onPrintError @ tmp_js_export.js:362
tmp_js_export.js:362    at: start (main/main.cpp:1998) - Condition "!scene" is true. Returned: false
onPrintError @ tmp_js_export.js:362
tmp_js_export.js:362 exception thrown: RuntimeError: function signature mismatch,RuntimeError: function signature mismatch
    at godot_js_main(int, char**) (<anonymous>:wasm-function[15324]:0x2ca1c5)
    at main (<anonymous>:wasm-function[31565]:0x73169e)
    at Module._main (http://localhost:8060/tmp_js_export.js:9:403120)
    at Object.callMain (http://localhost:8060/tmp_js_export.js:9:415246)
    at http://localhost:8060/tmp_js_export.js:694:28
    at new Promise (<anonymous>)
    at http://localhost:8060/tmp_js_export.js:689:14
onPrintError @ tmp_js_export.js:362
tmp_js_export.html:213 function signature mismatch

Steps to reproduce
I can't reproduce this bug on any other project that I have.
Minimal reproduction project
Only happens on here.

I'm not able to reproduce the issue, this salty project exports and runs fine for me with:

3.4.stable.mono
3.4.2.stable (there's no C# script so no need to use the Mono build which adds unnecessary libraries)

I'm not able to reproduce the issue, this salty project exports and runs fine for me with:
* 3.4.stable.mono

* 3.4.2.stable (there's no C# script so no need to use the Mono build which adds unnecessary libraries)

Out of options, I've tried deleting my local repo and re-cloning the online repo, and for some reason, the bug is gone on 3.4.stable.mono. Maybe it was some aggressive caching had gone awry?
I'll try an export with 3.4.2.stable as well. Thanks for the tip.


Add Paymaster feature

Can you provide any more context to it?

Give gas fees options using ETH, USDC or FUEL
Reference: VISA Paymaster ERC-4337
https://usa.visa.com/solutions/crypto/rethink-digital-transactions-with-account-abstraction.html


Uncaught ReferenceError: __extends is not defined

Hello,
For some reason I get this error mentioned in the title. it has something to with my LocalDataSource but I don't know how en why. I am enthusiastic about this data-table and I would like to use it.
Kind regards,
Meindert

Hey @MeindertRomkes, would you mind sharing a code example or plunkr to take a look at?

I have the same problem! I just used code from Minimal Setup Example and bundled it by webpack.

ng2-smart-table: 0.2.2
angular2: rc.5
webpack: { test: /\.ts$/, loader: 'awesome-typescript!angular2-template' }

me and @MeindertRomkes are using the angular-cli version of our project, mainly everything is managed by that + webpack.

guys, thanks for reporting, I would need a bit more information about the environment, webpack, typescript etc version, webpack configurations to investigate the issue. Also version of the module you use.
Generally you could take a look at our demo webpack/package configurations to compare:
https://github.com/akveo/ng2-smart-table/blob/master/config/webpack.common.js#L138
https://github.com/akveo/ng2-smart-table/blob/master/package.json

webpack version: webpack 2.1.0-beta.18 (Angular CLI)
webpack configuration is handled by angular cli, (more information)[https://github.com/angular/angular-cli]
typescript version 2.0.0
module version: latest of npm.
Environment: Ubuntu docker container.

ng2-smart-table: 0.2.2
angular2: rc.5
webpack: 1.13.2 - { test: /.ts$/, loader: 'awesome-typescript!angular2-template' }
typescript: 1.8.10
windows 10 pro 64-bit

all right, could you also provide a complete error output including stack trace?

 I'm struggling to reproduce the issue with no luck.

We are facing the same issue trying to get ng2-smart-table to work within our project.
ng2-smart-table: 0.2.3
angular2: rc.6
webpack: 1.13.2
typescript: 2.1.0-dev.20160823
stack trace:
local.data-source.js:8Uncaught ReferenceError: __extends is not defined(anonymous function)
@ local.data-source.js:8(anonymous function)
@ local.data-source.js:232n
@ bootstrap fe736e7…:50(anonymous function)
@ ng2-smart-table.component.js:6n
@ bootstrap fe736e7…:50(anonymous function)
@ ng2-smart-table.directives.js:2n
@ bootstrap fe736e7…:50(anonymous function)
@ ng2-smart-table.js:5n
@ bootstrap fe736e7…:50(anonymous function)
@ pages.module.ts:19n
@ bootstrap fe736e7…:50(anonymous function)
@ app.module.ts:13n
@ bootstrap fe736e7…:50(anonymous function)
@ main.ts:3n
@ bootstrap fe736e7…:50(anonymous function)
@ app.fe736e7….js:6n
@ bootstrap fe736e7…:50window.webpackJsonp
@ bootstrap fe736e7…:21(anonymous function)
@ app.fe736e7….js:1
Happens as soon as I try adding Ng2SmartTableModule into the "imports" of my NgModule. Unfortunately at this time I cannot provide a repo to reproduce the issue.

related to #26 , the fix is to add the typescript helpers globally for now , or to compile it with noEmitHelpers:false

Issue is also reported under issue #16

Thanks, the fix worked for me.

where i need to add noEmitHelpers:false in node module ng2-smart-table or in my project root tsconfig please help us

fixed in 0.4.0-3


[FEATURE] Loop route back to start

New to the project but loved onthegomap when I used it to plot my run today. Not sure if this idea is in development, I looked through some feature requests and didn't see anything, but being able to reverse your route, looping back to where you started, was something I was looking for today.

Thanks! This repo is just for the planetiler project for making vector tile basemaps from openstreetmap data, not onthegomap itself.
I have feedback.onthegomap.com and info at onthegomap dot com set up for people to submit sugestions like that, but not a great way to share progress or for others to comment on suggestions. I wonder if a separate onthegomap repo just for issues would work? Or maybe another service for collecting user feedback since most onthegomap users won't have a github account?


depoying in ECS

Hi Sir,
I have seen your code and its really awesome.
Since I am just a beginner and am learning devops recently , I would like to know how to deploy the same in an amazon ECS
I have pushed the image to amazon ECR and I need to provision docker containers now using ECS , Would you please show me a way for the same.

have tried to run the compose file locally, it was running fine, and now trying to deploy it to ECS

have tried to run the compose file locally, it was running fine, and now trying to deploy it to ECS

Hi @ThejusAP,
I think it's best to start with a tutorial on ECS first, like this: https://medium.com/boltops/gentle-introduction-to-how-aws-ecs-works-with-example-tutorial-cea3d27ce63d
Then you should be able to get this container up&running on ECS.
If you have specific issues with this container on ECS, let me know!


ReferenceError: util is not defined

Hello, first of all thanks for your great library :)
I am encountering an issue while trying your example.
const client = require('shodan-client');

const searchOpts = {
  facets: 'port:100,country:100',
  // minify: false,
};
client
  .search('asterisk port:5061', 'myapikey', searchOpts)
  .then(res => {
    console.log('Result:');
    console.log(util.inspect(res, { depth: 6 }));
  })
  .catch(err => {
    console.log('Error:');
    console.log(err);
  });

Return :

Result:
Error:
ReferenceError: util is not defined
at client.host.then.res (/home/picoloop/workspace/shodan.js:11:17)
at process._tickCallback (internal/process/next_tick.js:68:7)

Am I missing something ?
Thanks in advance for your help.
Environment :

OS: Arch Linux
Node.js version: v10.5.0

Ei, thanks for the feedback 😄. You´re right, there was an error in the example. I´ve added this first lost line.
https://github.com/jesusprubio/shodan-client.js/blob/master/README.md#use
Moreover I have also changed the query, because now Shodan returns an empty results looking for Asterisk in port 5061.

I can believe I didn't try that..
I was thinking util was an internal library of your project :disappointed_relieved:
Thanks for your help!


HTML5 Video support on IE

The Element is not supported under IE11 under Win7 and maybe as well IE10 under win 7.
On IE 9 under Win 7 everything is fine.

IE11 introduces support for MPEG-DASH media streaming through HTML5 Media Source Extensions (MSE). MSE extends the video and audio elements that you can dynamically change for a media stream without using plug-ins. This gives you such things as adaptive media streaming, live streaming, splicing videos, and video editing.

Important  This feature is not supported in IE11 on Windows 7.

Source: https://msdn.microsoft.com/en-us/library/ie/bg182646(v=vs.85).aspx#mse
It is marked as Full supported and leads lots of users wrong: http://caniuse.com/#feat=video

I don’t understand this bug report. You’re saying the video element is not supported by IE11? That is patently false.
The quote included is about MPEG-DASH and MSE. Very different to the video element itself.

@dstorey I never said that it is not supported under IE11. It is not Supported under Windows 7 and IE 11. I have tested this also with a demo site for the HTML5 Video Player.
So IE11 has only a partial HTML5 Video Element Support. -> http://www.html5rocks.com/de/tutorials/video/basics/
Just check it out under Windows 7 and IE 11. It does not work. I have used browserstack to try this.
The Quote is only a further detailed Explanation why it doesn't work.

@Zeromax The video element is supported in IE11 on Windows 7. It was added in IE9 https://msdn.microsoft.com/en-us/library/ie/hh772959(v=vs.85).aspx

@dstorey Please go to Browserstack. Start a Session with IE11 and Windows 7 use this link: http://www.html5rocks.com/de/tutorials/video/basics/ Check it out.
If everythig works. Close it.

@Zeromax It seems the only reason it doesn't work on that page is due to the addition of the codecs being specified (  codecs="avc1.42E01E, mp4a.40.2") if you remove that it works fine. So at worst that's a minor bug.

@Fyrd Thanks for that explanation.


The libxc subsections of &XC_FUNCTIONAL are not recognized

Hi
I'm trying to parse an input file using the new libxc subsections of &XC_FUNCTIONAL. But these sections are not recognized and I get the following error:
cp2k_input_tools.parser_errors.InvalidSectionError: ("invalid section 'MGGA_C_R2SCAN'", defaultdict(<function Context.. at 0x2b26fa545790>, {'filename': 'phonon.inp', 'linenr': 358, 'colnrs': [8], 'line': '&R2MGGA_C_SCAN', 'section': Section(name='XC_FUNCTIONAL', node=<Element 'SECTION' at 0x2b26f7505bd0>, subsections=[], keywords=[], param=None, repeats=False)}))
Can I somehow add these sections?
Thanks in advance,
Fabian

Can you please try with version 0.6.3?
We are using a bundled cp2k_input.xml as generated by CP2K with cp2k.psmp --xml.
When using the API you can specify an alternative file as the first argument to CP2KInputPraser: cp2k_parser = CP2KInputParser("path/to/an/updated.xml"). For the command line tools there is no option yet to specify an alternative file.

Works like a charm. Thanks for the update and the explanation!


Question consultation

Dear authors:
Recently I  have looking your this project and feel interested in it !could have a dataset of this project?   Thanks a lot! I am looking forward to your reply Sincerely!
Best regards.

Hello! Thank you for your interest in our work!
I do not own the dataset, but I used BRATS 2017's data. The webpage is here. I can recommend checking it out to see if it is still available, or reaching out the organizers.
Once you acquire the data, you can get the (training, validation, test) splits using the IDs share here.
Hope this helps!

I am pleased to hear from your letter. Thank you very much.


Custom String Formats

Low-priority refactor needed for all our string APIs to support an extensible string system where users can register custom string recognizers and printers. This would also allow for better built-in support for a wider variety of codepages and standards.

Dupe of #1334


Go to Definition behaves inconsistently when importing a module in a package

Go to Definition behaves inconsistently when importing a module in a package, in the following ways:

On a line of the form import package.module, Go to Definition on the module reports "No definition found," while hovering over the module name gives a summary of the module. Whereas Go to Definition does work on the module name when using the form from package import module [as name]
After the import line itself, in different cases, Go to Definition may jump to the import line, an intermediate import line the parent package of the module, or the source code of the module itself (all for the same parent package and child module).

The above behavior also applies to Peek Definition.
Note: In principle, I would be open to contributing a fix for this bug, but I don't know where to start, as I've only just started evaluating vscode-python.
Environment data

VS Code version: 1.37.1
Extension version (available under the Extensions sidebar): 2019.8.30787
OS and version: macOS 10.14.5
Python version (& distribution if applicable, e.g. Anaconda): 2.7.10
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
Relevant/affected Python packages and their versions: Any Python module or package that's nested within another package.
Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info microsoft/vscode-python#3977): Language Server

Expected behaviour
Example code:
1  import os.path
2  from os import path as os_path
3  print(os.path.basename('a/b/c')
4  print(os_path.basename('a/b/c'))

Expected behavior of right click → Go to Definition on...

line 1, cursor right after the "s" in os: open os.py (i.e., the same behavior as when the cursor is right before the "o" or the "s" or when the cursor is right after "from os" on line 2)
line 1, path in import os.path:

jump to the line import posixpath as path in os.py (the current behavior of right click → Go to Definition on path and os_path` on lines 3 and 4, respectively)
alternatively, directly open posixpath.py (i.e., the same behavior as on path or os_path on line 2) if an import is not considered a definition. This is a tradeoff between precision (being able to trace the steps involved in importing a symbol into an environment) and expediency (being able to jump to the actual definition of a symbol in fewer steps).

line 3, path and line 4, os_path: jump to the corresponding line (to be consistent with right click → Go to Definition on os on line 3)

Actual behaviour
Actual behavior of right click → Go to Definition on...

line 1, cursor right after the "s" in os: moves the cursor just before os (similarly, Peek Definition shows the same file with os highlighted rather than showing os.py)
line 1, path in import os.path: reports "No definition found for 'path'"
line 3, path and line 4, os_path: jumps to the line import posixpath as path in os.py. This is an odd middleground that neither stops at the nearest import nor skips over all levels of imports to the actual definition.

Steps to reproduce:

Create an empty directory, add a file named example.py with the following contents:

import os.path
from os import path as os_path
print(os.path.basename('a/b/c')
print(os_path.basename('a/b/c'))

Open the directory in VS Code

Inspect the code in example.py as described under expected/actual behavior above.

Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
View→Output is grayed out
Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)
I don't see an option to enable Developer Tools under Help.

In symbol is imported, depending on the import form first navigation may go to the import statement effectively showing where variable is first declared in the file. Navigation from import statement then gets to the module source - if available. If module is compiled or a built-in, you may get "no definition is available" because effectively, there is no Python source.

Related https://github.com/microsoft/python-language-server/issues/1162

Here is how it may work:
import os.path

caret on os => goes to os.py
caret on path => goes to import ntpath as path in os.py - that's where path is defined.

from os import path as os_path

caret on os => goes to os.py
caret on path => goes to import ntpath as path in os.py.
caret on os_path => goes to ntpath.py on Windows.

print(os.path.basename('a/b/c'))

caret on os => goes to os.py
caret on path => goes to import ntpath as path in os.py.
caret on os_path => goes to ntpath.py on Windows (per #1162).

print(os_path.basename('a/b/c'))

caret on os_path => goes to ntpath.py on Windows (per #1162).

Pending #1482

Part of https://github.com/microsoft/python-language-server/pull/1482. 0.4.16+.


Suggestion for nlxheader.py in init for missing date-time information

I had some issues loading in neuralynx data that were missing date-time information in the headers. This isn't the most elegant solution, but I simply generated a date-time value for header files missing that information. I don't know if missing date-time information should raise an error, but it should definitely be a warning to users.
lines 241:260 in neo.rawio.neuralynxrawio.nlxheader

# opening time
sr = re.search(hpd['datetime1_regex'], txt_header)
if not sr:
    raise IOError("No matching header open date/time for application {} " +
                  "version {}. Please contact developers.".format(an, av))
else:
    dt1 = sr.groupdict()
    self['recording_opened'] = datetime.datetime.strptime(
        dt1['date'] + ' ' + dt1['time'], hpd['datetimeformat'])

# close time, if available
if 'datetime2_regex' in hpd:
    sr = re.search(hpd['datetime2_regex'], txt_header)
    if not sr:
        raise IOError("No matching header close date/time for application {} " +
                      "version {}. Please contact developers.".format(an, av))
    else:
        dt2 = sr.groupdict()
        self['recording_closed'] = datetime.datetime.strptime(
            dt2['date'] + ' ' + dt2['time'], hpd['datetimeformat'])

Code that I changed to ignore missing date-time information

# opening time
sr = re.search(hpd['datetime1_regex'], txt_header)
if not sr:
    self['recording_opened'] = datetime.datetime.now().replace(microsecond=0)
else:
    dt1 = sr.groupdict()
    self['recording_opened'] = datetime.datetime.strptime(
        dt1['date'] + ' ' + dt1['time'], hpd['datetimeformat'])

# close time, if available
if 'datetime2_regex' in hpd:
    sr = re.search(hpd['datetime2_regex'], txt_header)
    if not sr:
        self['recording_closed'] = datetime.datetime.now().replace(microsecond=0)
    else:
        dt2 = sr.groupdict()
        self['recording_closed'] = datetime.datetime.strptime(
            dt2['date'] + ' ' + dt2['time'], hpd['datetimeformat'])

We have updated neuralynx so please give it a go and if you still run into troubles just open a new issue.

Thanks Zach, I won’t have a chance to check this out anytime soon, but I
definitely will
On Fri, May 3, 2024 at 10:03 AM Zach McKenzie @.***>
wrote:

We have updated neuralynx so please give it a go and if you still run into
troubles just open a new issue.
—
Reply to this email directly, view it on GitHub
https://github.com/NeuralEnsemble/python-neo/issues/1346#issuecomment-2093087320,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK7U57VMWDEVFJVPYUMICU3ZAOKKBAVCNFSM6AAAAAA7GMF34GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJTGA4DOMZSGA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Updating the example with New Vschema format

This Pull Request corrects the Vschema Definition with the new version

@ashudeep-sharma A similar change needs to be made in the sharding-kubernetes doc.

@demmer Thanks for the information, added the changes in sharding-kubernetes.html

Head's up: The changed files are generated and must not be edited manually.
Instead, you need to edit the files under the doc/ directory. See also the README.md file in the docs/ directory: https://github.com/youtube/vitess/tree/master/docs
There's unfortunately no easy way to avoid this confusion because "docs" is the hardcoded directory used for serving the website. You cannot change it in GitHub.
I'll port back the changes of this PR later.

@michael-berlin Now I remember sometime back you had made the changes to markdown files and then generate these files. I have updated the changes in Markdown files here https://github.com/youtube/vitess/pull/2615


Add scripts for generating ASCII animations

Sill very rough but worth a review or adoption.
https://asciinema.org/a/Z4HxV5IXOanYi8r2oWCCB2VhT

@prescod did these end up in a different repository?

@davisagli Yes, the latest code is in:
https://github.com/SFDO-Tooling/cci-demo-animations


add text underline utility & correct relative comment

Adds a utility class for .text-underline and adjusts the corresponding comment
Fixes: #540
/cc @primer/ds-core

On it @shawnbot

All done, first time I've built the primer storybook on my machine. My primer contributions are evolving.


[P2] Having a simple tutorial on how to use intervenable model inside another torch module, or pipeline (e.g., HF pipeline)

Descriptions:
The IntervenableModel is a torch.nn.Module.  So, this can be used inside another torch model, or even pipeline object (e.g., Huggingface pipeline). Here is a quick code snippet,
import pyvene
from pyvene import IntervenableRepresentationConfig, IntervenableConfig, IntervenableModel

# provided wrapper for huggingface gpt2 model
_, tokenizer, gpt2 = pyvene.create_gpt2()

# turn gpt2 into intervenable_gpt2
intervenable_gpt2 = IntervenableModel(
    intervenable_config = IntervenableConfig(
        intervenable_representations=[
            IntervenableRepresentationConfig(
                0,            # intervening layer 0
                "mlp_output", # intervening mlp output
                "pos",        # intervening based on positional indices of tokens
                1             # maximally intervening one token
            ),
        ],
    ),
    model = gpt2
)

import torch
import torch.nn as nn
from typing import List, Optional, Tuple, Union, Dict

class ModelWithIntervenables(nn.Module):
    def __init__(self):
        super(ModelWithIntervenables, self).__init__()
        self.intervenable_gpt2 = intervenable_gpt2
        self.relu = nn.ReLU()
        self.fc = nn.Linear(768, 1)
        # Your other downstream components go here

    def forward(
        self,
        base,
        sources: Optional[List] = None,
        unit_locations: Optional[Dict] = None,
        activations_sources: Optional[Dict] = None,
        subspaces: Optional[List] = None,
    ):
        _, counterfactual_x = self.intervenable_gpt2(
            base,
            sources,
            unit_locations,
            activations_sources,
            subspaces
        )
        counterfactual_x = counterfactual_x.last_hidden_state

        counterfactual_x = self.relu(counterfactual_x)
        counterfactual_x = self.fc(counterfactual_x)
        return counterfactual_x

and then you can run forward as usual,
model = ModelWithIntervenables()

base = tokenizer("The capital of Spain is", return_tensors="pt")
sources = [
    tokenizer("The capital of Italy is", return_tensors="pt"),
]

model(
    base, sources, {"sources->base": ([[[4]]], [[[4]]])}
)

which returns,
tensor([[[2.7027],
         [6.3036],
         [6.1785],
         [6.4302],
         [8.0921]]], grad_fn=<ViewBackward0>)

the readme has this right? closing


Addition of the remaining methods which are in the Wallet Api

Description
There's a few methods that are in the Wallet Api but not in this library.
I'm currently writing Dapp codes with React and on my way to refactor Wallet connection logic with this library, replacing Wallet Api with this library.
For now everything seems to be fine except above point. e.g. addCIS2Tokens

Hi @aiinkiestism, thanks for filing this issue.
The addCIS2Tokens and addCIS2Tokens methods are not yet supported in the mobile wallets.
I think we should definitely add the methods to BrowserWalletConnector. If added to the WalletConector interface, the methods would have to throw "not implement" exceptions in WalletConnect. I think that's also reasonable, but will check with the team. We probably need a way for the dapp to probe whether a connector supports a given method.
For now, you can still access the browser wallet API directly via the client field in BrowserWalletConnector.

Internal task: https://concordium.atlassian.net/browse/CBW-961


Track upstream PR

Pull the merged changes from upstream once it's merged: https://github.com/Homebrew/formulae.brew.sh/pull/266

Closed by 0f4c55eacf58a9fcfc2611d52a1b228f7846c723


Create bot-ビットフライヤー

Install-Package BitflyerApi

what? any mistake?

I'm sorry. I made a mistake.
From: kobake
Sent: Tuesday, February 14, 2017 8:31 AM
To: kobake/BitflyerApi
Cc: miyagon ; Author
Subject: Re: [kobake/BitflyerApi] Create bot-ビットフライヤー (#6)
what? any mistake?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Had you tried to make PR in your repository? If so, you need to select not original repository but yours in combobox when creating PR.

I close This PR. Feel free to ask more.