Replace instances of dbt Core with a product variable

Contributions

[ ] I have read the contribution docs, and understand what's expected of me.

Link to the page on docs.getdbt.com requiring updates
You will need to search the repo for mentions of dbt core or dbt Core or core.
What part(s) of the page would you like to see updated?
For more information on how to use product variables, see Using global variables.
Let's use this product variable instead of the product name:

<Var name="dbtCore" />

Additional information
No response

Closing this for now. We might address this at a later time.


[feature request] Allow paginators / dots animation

Like https://github.com/f111fei/react-native-banner-carousel

I believe this requires the renderPagination() function to return the scrollValue

Is there a way to animate the dots in react-native-swiper without the feature?


Fix #65.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
http://guh.guru:8080/job/guh-webinterface-pull-request/48/
Test PASSed.


Pouring (Core Filling Functionality)

Summary of changes
This PR adds the "pour" functionality to ghastly, i.e., the ability to fill a core with pebbles.  It uses a combination of OpenMC to pack cylindrical regions, and LAMMPS to both allow the pebbles to fall under gravity, and add any remaining pebbles needed to fill the core to the desired packing fraction.
It does this using a series of jinja2 templates, which automatically create a LAMMPS input file based on the parameters in the input file, which is a JSON file.  There are example input files for ghastly both in the tests and examples directories.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] I have read the CONTRIBUTING document.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Associated Issues and PRs

closes #2
closes #4
closes #10

Checklist for Reviewers
Reviewers should use this link to get to the
Review Checklist before they begin their review.

I think I saved it - sorry folks!

I believe I have either made issues for or fixed issues in new comments!  (Thanks all)

Oops - I missed a few comments because I missed some hidden comments when I when through.  Let me make a commit for splitting up functions into smaller sections, and THEN I think I actually covered everything.

@katyhuff do you have any insight on why Pep8speaks might not have checked this PR?


Reserve space for additional instances in binary deserializer

This PR adds a new method WeakDom::reserve that can preallocate additional space for instances, and makes the binary deserializer use it before adding instances.
On my machine, this improves rbx_binary's "Deserialize 10,000 Parts" benchmark by ~4%, reduces the number of heap allocations by a negligible amount, but allocates ~2.4MB less memory.
I'm not sure if this should also call reserve on WeakDom.unique_ids, because UniqueIds won't always be present in inputs, and it could take a possibly significant amount of space for no reason.

It doesn't seem to make much a difference for a 6MB rbxl file on my machine, but I guess it won't hurt, since massive rbxm files aren't very common anyway

Hilariously for Adopt Me (65MB), it seems to actually make it take longer to deserialize with the UniqueId reservation. If I went through the trouble of checking our full Rojo project it might be more dramatic, since we have around 6000 models with UniqueId written in them, but that's work I don't feel like doing right now.
The difference for Adopt Me is like 11%, so we may want to just not bother with UniqueId reservation.

Well, that's a bit weird! 🤔


support redirects for renamed docs

This PR exists in anticipation of a rename in electron/electron:
web-view-tag.md 👉 webview-tag.md

This will need to be revamped, given all the change that happened in #630.

Replaced by #641


Backup Options

Hi Team,
I'm a little confused with all the backup options and want to know what's necessary / easy / useful with my current configuration.
I use 1.6.2 with BTRFS (64GB USB Stick) and have RTL, RPC Explorer and Lightning Loop enabled right now.
Somewhere it's mentioned that you shouldn't use sticks with more than 32GB since this could cause power issues - so I wonder if it's save to use another stick for backup because you can't use the one used for BTRFS.
On the other hand you can create a backup file to download and also use a function to backup within RTL...
I simply want to ensure that I can restore everything properly after an update or an hardware error and would appreciate advice.
Thanks

The bigger and older the thumb drive is the higher the chance that it consumes more power. 64GB should be OK but switching down to a 32GB is best practice.
To change BTRFS RAID Thumbdrive .. you should be able to just turn that "off" and replace the thumb drive and switch it "on" again and your fine - use commands:
sudo /home/admin/config.scripts/blitz.datadrive.sh raid off &
sudo /home/admin/config.scripts/blitz.datadrive.sh raid on
the name of the raid device you should get from
sudo /home/admin/config.scripts/blitz.datadrive.sh status
Regarding backup files for download:
There is the migration file that makes a archive of all your relevant data .. so no blockchain data or indexes but all wallets and data from installed apps. You can use that to move to a complete new hardware - like a new HDD/SSD.
And there is the smaller brother the lnd-rescue file that just backups all the relevant data from your LND - but not the other apps.

Sorry to ask for clarification, but I'quite new to Linux / CLI...
So when I simply stop raid, change the stick & start raid again - why do I need this status command?
It seems lnd rescue is the preferred solution when I do normal updates just in case something goes wrong - but for my understanding I don't have to use the rescue file and when I update to a new version everything should work fine normally, right?
Thanks again

So when I simply stop raid, change the stick & start raid again - why do I need this status command?

When turning the raid on you have to give the name of the device (could be 'sdcfor example) .. thestatus` command gives you a list of possible names.

It seems lnd rescue is the preferred solution when I do normal updates just in case something goes wrong - but for my understanding I don't have to use the rescue file and when I update to a new version everything should work fine normally, right?

Yes normally you dont need the rescue file on an update ... its just for the case something goes worng. Once your node is up and running after upadte I would even recommend to delete the reschue-file.

Ok, thank you for clarification.


[WORKAROUND]: New Config UI (2.0.0 and above) causes Push Notification to not work properly

What happened?
Push notifications was working well but now don't work after upgrading to version 2.0. I can't see any settings to change to fix this.  Any ideas?
Device Type
Doorbell (Supported)
Plugin Version
v2.0.x (Supported)
HomeBridge Version
v1.4.x (Supported)
NodeJS Version
v16 (Supported)
Operating System
Raspbian 10+ (Supported)
Relevant log output
[6/1/2022, 8:00:20 AM] [EufySecurity-2.0.0] WARN:  Push Closed!
[6/1/2022, 8:00:20 AM] [EufySecurity-2.0.0] INFO:  Finished shutdown!
[01/06/2022, 08:00:25] [homebridge-eufy-security] Child bridge process ended
[01/06/2022, 08:00:25] [homebridge-eufy-security] Process Ended. Code: 143, Signal: null
[01/06/2022, 08:00:31] [Apple TV 4K] State of Apple TV 4K is: true
[01/06/2022, 08:00:32] [homebridge-eufy-security] Restarting Process...
[01/06/2022, 08:00:34] [homebridge-eufy-security] Launched child bridge with PID 11720
[01/06/2022, 08:00:36] Registering platform 'homebridge-eufy-security.EufySecurity'
[01/06/2022, 08:00:36] [homebridge-eufy-security] Loaded homebridge-eufy-security v2.0.0 child bridge successfully
[01/06/2022, 08:00:36] Loaded 1 cached accessories from cachedAccessories.0E35953ECB1A.
[6/1/2022, 8:00:36 AM] [EufySecurity-2.0.0] WARN:  warning: planned changes, see https://github.com/homebridge-eufy-security/plugin/issues/1
[6/1/2022, 8:00:36 AM] [EufySecurity-2.0.0] INFO:  Country set: GB
[6/1/2022, 8:00:36 AM] [EufySecurity-2.0.0] INFO:  Finished initializing!
[01/06/2022, 08:00:36] Homebridge v1.4.1 (HAP v0.10.2) (homebridge-eufy-security) is running on port 59551.
[6/1/2022, 8:00:42 AM] [EufySecurity-2.0.0] INFO:  You're using guest admin account with this plugin! This is recommanded way!
[6/1/2022, 8:00:42 AM] [EufySecurity-2.0.0] INFO:  Updating accessory: Eufy Homebase
[6/1/2022, 8:00:43 AM] [EufySecurity-2.0.0] INFO:  Adding new bridged accessory: Front Door
[01/06/2022, 08:00:43] Front Door 27CE is running on port 43139.
[01/06/2022, 08:00:43] Please add [Front Door 27CE] manually in Home app. Setup Code: 397-53-293

yes nothing in Common Issues

Hi @andypburke
You mean push notifications from Homekit, right?
I have experienced a similar behavior from time to time. But could not find where it is caused.
Have you tried to restart homebridge altogether? For me this resolves this issue in general.
From your log I cannot see where a event is detected (motion, doorbell ring, ...) but my findings suggest that the plugin is doing it's job as planned but the informations seems to get lost somewhere on the way to homebridge or HomeKit.
Please let me know, if restarting helps.

Hi again
the problem seems to lie with the new config ui. This can interfere with the connection to the eufy cloud and in the end be the cause of failing push notifications.
I have added a section to the common issues to inform about this. The general workaround as of now would be to restart the plugin every time you entered the config ui - regardless of any setting being changed or not.
Way to reproduce:

Open config ui a few times over the course of a day and close it after the device list was loaded.
After a while (for some users after the very first time already) no push notifications will reach the plugin (no motion, ring events, ...)
After a restart everything works again

@lenoxys For the time being I don't see if there could anything be done about this. Since we need the extra connection to setup the config wizard accordingly.
But even if the plugin-ui-utils do provide the necessary interfaces I believe a large part of the config ui would have to be rewritten.

Thanks @thieren - I did this and it seemed to work, although it took about 10 seconds before the notification appeared and without a thumbnail.  Anything I can do to resolve that?

thanks. I got it working again. just changed the config (didn't seem to matter what setting) and that seems to have fixed it. All a bit weird though.

Yeah. Just found the bug. But that's a completely other issue. Will fix this in the next beta.

hey @thieren, maybe it's related here see beta.9

Hey @lenoxys

hey @thieren, maybe it's related here see beta.9

Unfortunately this didn't fix the issue. Push notifications will still stop working if you open the config ui and list devices.
Furthermore there is now an error toast message when clicking on 'List Devices':

And in the log following errors appear:
[7.6.2022, 14:33:59] [Homebridge UI] [homebridge-eufy-security] Incoming Request: /init
[7.6.2022, 14:33:59] [Homebridge UI] [homebridge-eufy-security] Incoming Request: /getStations
[7.6.2022, 14:33:59] [Homebridge UI] [homebridge-eufy-security] [2.0.1-beta.10] INFO:  Need to refresh the devices list
[7.6.2022, 14:33:59] [Homebridge UI] [homebridge-eufy-security] TypeError: Cannot read properties of undefined (reading 'isConnected')
    at UiServer.getStations (./dev/homebridge-eufy-security/homebridge-ui/server.js:303:17)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async UiServer.processRequest (./dev/homebridge-eufy-security/node_modules/@homebridge/plugin-ui-utils/dist/server.js:75:30)
[7.6.2022, 14:34:00] [Homebridge UI] [homebridge-eufy-security] [2.0.1-beta.10] INFO:  connected!
[7.6.2022, 14:34:00] [Homebridge UI] [homebridge-eufy-security] Incoming Request: /getStations
[7.6.2022, 14:34:00] [Homebridge UI] [homebridge-eufy-security] [2.0.1-beta.10] INFO:  Need to refresh the devices list
[7.6.2022, 14:34:04] [Homebridge UI] [homebridge-eufy-security] [2.0.1-beta.10] INFO:  Connected to station T8010******** on host **.**.**.** and port 15180
[7.6.2022, 14:34:04] [Homebridge UI] [homebridge-eufy-security] [2.0.1-beta.10] ERROR: Error DuplicateDeviceError: Device with this serial T8210********** exists already and couldn't be added again!
    at EufySecurity.addDevice (./dev/homebridge-eufy-security/node_modules/eufy-security-client/build/eufysecurity.js:252:19)
    at ./dev/homebridge-eufy-security/node_modules/eufy-security-client/build/eufysecurity.js:461:26
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Promise.all (index 0)
[7.6.2022, 14:34:04] [Homebridge UI] [homebridge-eufy-security] [2.0.1-beta.10] INFO:  You're using guest admin account with this plugin! This is recommanded way!

Hum shame, though it was.
I do init early on this stage to avoid such error but when doing this you might generate new token but if the plugin isn't restarted it will play with the old one. UI and Plugin are working in //.
We need to find a way to force the plugin to use the new ones.

Or maybe list devices should reflect the cached ones and if user want to refresh it will need to redo the whole process that way it won't challenge anything from Eufy cloud API until user force it.

Or maybe list devices should reflect the cached ones and if user want to refresh it will need to redo the whole process that way it won't challenge anything from Eufy cloud API until user force it.

That was exactly what I was thinking right now. But don't know how much work this is (therefore the estimation that this could mean a larger change).
At least we have a workaround until we get to it.

whats the workaround? im on beta 2 and still get this warning.
[6/12/2022, 8:00:30 AM] [EufySecurity-2.0.1-beta.12] WARN:  Push Closed!

Hey @JonoHaysom
your issue seems to be of another origin.
For me the "Push Closed!" Warning is normal but actually will only print one time before a few seconds later the "Push Connect" message appears.
These messages are passed through from the eufy-security-client library which is used by the plugin to communicate with the eufy cloud. As far as I know the plugin does nothing to force these messages and so the problem seems to lie in the connection to the cloud for you. Where exactly is impossible to know for now.
To be sure you can test with a little tool from me: https://github.com/thieren/eufy-test-client
Follow the instructions to set it up and just connect. You should see the same Push Closed event in the log after a few seconds. If there is also no following 'Push Connect` then it proofs that this has nothing to do with the plugin but with the underlying connection to the cloud. Maybe the author of the eufy-security-client could help in this case.
Regarding your actual question: The Workaround is now described in the common issue section https://github.com/homebridge-eufy-security/plugin/wiki/Common-Issues#push-notification-issues
But as said I don't believe that this will help you since your problem seems to persist even after a plugin restart.

I don't know if this is the same problem, but... Every time I try to change the alarm setting I have to open the eufy app on my phone for the changes to take effect. If I don't do this the process with keep timing out..

Hey @jhaleit
No this sounds like #38 and is most likely not in the scope of this plugin.
There is an issue at eufy-security-client (https://github.com/bropat/eufy-security-client/issues/161) that's hopefully dealing with this.

This issue should be resolved with the latest beta and redesign of the config ui.
There still will be issues if you login via the config ui, but now it will not happen automatically and the user will be warned beforehand that a restart is needed afterwards.


Better handling of dead players

Sometimes trails are incorrectly shown
Support for multiple players killing the player in case one undoes their kill, and only giving the kill to the earliest one when the player permanently dies
Restricting movement while dead

I think clients receive incorrect trail visibility when a player enters their viewport while dead.
Do you have a way to reproduce incorrect visibility using multiple kills?

Do you have a way to reproduce incorrect visibility using multiple kills?
Sorry I meant these as separate items

Could you create separate tickets for these?


Implement the origin_tls_client_auth endpoint

Current Terraform and Cloudflare provider version
Terraform v1.0.11
on linux_amd64
+ provider registry.terraform.io/cloudflare/cloudflare v3.9.1
+ provider registry.terraform.io/hashicorp/external v2.2.0
+ provider registry.terraform.io/hashicorp/google v3.90.1
+ provider registry.terraform.io/hashicorp/google-beta v3.90.1
+ provider registry.terraform.io/hashicorp/tls v3.1.0
+ provider registry.terraform.io/outfoxx/jks-trust-store v0.2.1

Description
For Authenticated Origin Pulls, with Zone-Level — customer certificates, the PUT zones/:zone_identifier/origin_tls_client_auth/settings API endpoint [1] needs to have enabled toggled to true.
[1] https://api.cloudflare.com/#zone-level-authenticated-origin-pulls-set-enablement-for-zone
Use cases
CloudFlare negotiating with Origin over TLS and Origin validating CloudFlare's identity with a custom Client Certificate. Custom Client Certificate so that the shared CloudFlare Certificate is not used.
Use of the shared certificate [1] could lead to potentially trusting other 'clients' not quite controlled by us but initiating from CloudFlare.
[1] https://api.cloudflare.com/#zone-level-authenticated-origin-pulls-set-enablement-for-zone
Potential Terraform configuration
...

References
No response

I am looking for this functionality as well. I assumed it was the enabled flag on the cloudflare_authenticated_origin_pulls but that does not appear to be the case.

This issue has been closed as we are now tracking this internally with service teams directly. If you would like an update or to be notified when/if the product ships with this change, please reach out to Cloudflare Support or your account team who can watch the internal feature request for you.


Creator: Duplicate arbitrary programs

In addition to #161, I think there is a strong place for duplicating complex programs without manually creating each. I think this is less important than Templates since you COULD theoretically use Templates for the same purpose, but it is a few more steps and less amenable to quick iteration.
Separate from the new template database, let's see about locally (in a given Space) duplicating a paper and adding it to the left area.

Add a new random Program number.
Add suffix to new components: "Copy", "Copy1", "Copy2", etc. Whatever is next available. We'll want to try to keep associations between components which might be the tricky bit.
Add a Copy (that two paper icon) icon to the top right of a paper. Or Add a "Duplicate Paper" to the meta form. Whichever is less messy looking I think?

Found issues when TS worked on TacTiles project, but they have been cleared up. Looking good!


Add Danish translation

@mhtorp Hey, I've just updated the application with a bunch of new strings.
I know that it has been a long time between this and the last release but if you are still interested I'd like to support your translation.
Pull the last changes in the master branch and update the PR.
Thanks!


Manedit don't detect projects although the directory exists

Hey, it's me again, sorry for opening so many issues in such a shot period of time!
I'm still working on the same project, but this time I updated to manedit 0.3.4.
Unlike v0.3.3, it doesn't find created projects in the main "Project Selection" page, but detects that a project already exists when we want to create a project with the same name.
Steps to reproduce:

Code a project,
manim --save_sections hsf.py,
In manedit v0.3.4: create a project named for example HSF,
Once the project is populated, you end up in the Project Selection page. On v0.3.3 you see HSF, but v0.3.4 says No project was found in the CWD; you can change the CWD or create a new project., (the directory HSF exists in the CWD),
Go to create new project, name it HSF, you get: The project name 'HSF' points to a filled directory. If this is a project, you can open it instead.

I'll look at it, but I might not finish it today.

I failed to replicate the problem, I ran manim --save_sections hsf.py Segmentation and then manim_editor in the same directory. In the Manim Editor I selected create a  new project, called it HSF, selected the Segmentation scene and confirmed.
Then I get to see this:

Did you do anything differently?

Hmm that's strange.
Here is my full folder after running manim --save_sections hsf.py, as you can see, nothing is found by manedit
HSF.tar.gz

By exporting only Segmentation (like you did), manedit works as expected, showing the project. I personnaly exported all but BaseHsf, and tried to create a project on manedit with either all sections, or only one (in the case I uploaded in previous post, only preprocessing)

Hmm that's strange.
Here is my full folder after running manim --save_sections hsf.py, as you can see, nothing is found by manedit
HSF.tar.gz

After rendering with Manim, there shouldn't be any project folders. So this is the expected behaviour.
Or am I misunderstanding something?
PS: I currently can't take a look at the tar.gz I'll do that later today.

Oops sorry, I should have been unclear. Yes, I know that manim doesn't create the project, it's created by manedit.
But, when I export only one section using manim (like you did), I can create a project and see it on manedit. So I can replicate what you did.
However, when I export everything with manim (actually all but not the BaseHsf), manedit creates the project but I can't see it in the project selection page

Copy that.
I'll look into it later today.

I managed to reproduce it and fixed it. Could you check v0.3.5 and see if it's still there?
And don't sorry for opening many issues; this kind of feedback is exactly what I need.
Thanks a lot again!
PS: If you're interested in knowing what caused this: I'm using JSON Schema files to check if a project.json really belongs to a Manim Editor project. These schemas contain information on how the different fields in the JSON should look like. You can create these schema files from an example JSON, which I've done. The problem was that the duration of all sections in that example were integers. So the Schema set that as the type for the duration parameter. Your example has a float somewhere though so it should refused to load.

Amazing! :D
I tried and it works as expected.
Thanks for your reactivity and the explanation!


angular-pdf.js directive remove "read-only"

Hello
I was hoping may be you can give me a hand...
My issue is that looks like the directive canvas (viewer) is "read-only" I'm trying to mark some text to copy but is not possible, it looks like there is a top layer blocking, or like if the pdf is an image or svg, I was thinking if there is a way I can change this page mode?
and my second issue is I have some links inside the pdf pages, that render to another page, but we are not able to click them... we found some info about enable externalLinkTarget property but didn't work I think because the read-only mode but is just hunch we are not sure...
We'll appreciate any  info you could give us please...
thanks you.
Jose Rojas

Hi @joserojasv , now this directive doesn't render the TextLayer or links but only the page.
This is a useful feature, any help will be welcome! 😄


Update docs

Update the following docs: README AboutUs User Guide Developer Guide

(Sending this to remind me to review the linked PR)


Big latency between non-local network

I tried with 2 machine and my local machine, i can run the library good enough but when i run it on non local machine it really has latency i'm sure its about library because i tested WatsonWebsocket it was much better than this.

Can you isolate where in the library you're encountering the latency?  Ie something like .NET Reflector?

I couldn't find the code where the delay happening.

Ok, moving this to a discussion.  If you can pinpoint the issue, please let me know.  I haven't experienced this.


fix: renovate should create only one PR for CSI tools

Previously we were creating a PR for minor and patch version and a different PR for major, this will lead to a temporary failure even in the PR because the major versions will not match, this will create only one PR for update major, minor and patch versions.

/ok-to-merge fixing renovate


e2e_test: fix goroutine leak

If the goroutine running the descheduler strategies times out, it will still write to the channel without a reader thus causing a goroutine leak. To fix this, use a buffered channel (c).

/assign @damemi


Safari 9: Specifying % for flex-basis when flex-direction=column causes parent to lose height

Bumped into this issue tonight, took a very long time to debug, will circle back with replication bin tomorrow once I sleep.

This problem appears in webkit in some old versions of ios(Chrome for ios is repeat this behavior too).

Seams the same for chrome

Can you please provide an example?

@philipwalton sure, only didn't cause I noticed the other related issue.

Hi,
Had this bug too. Here is an example: https://jsfiddle.net/b85Lh1q2/1/
Fixed it by adding an extra flex-basis: auto: https://jsfiddle.net/b85Lh1q2/2/

I had this bug pop up in Safari only. flex-basis: auto on my flex items solved it but I do not know why.

I believe this is just yet another example of Flexbug 1. Since you're setting the flex direction to column, the flex-basis value goes in the vertical direction, but the height of the container is determined by its children, so you have a circular reference and a percentage value is meaningless.
However, the items should, by default, not shrink below their minimum content size (Flexbug 1), but in Safari they're not honoring that. When you say 100%, since the height isn't fixed, that computes to 0, which is why you're seeing them all squished.

removing min-height fixed this bug for me in safari.

Thanks, supremely helpful !

Thank you @philipwalton ! You've really helped me!

flex-shrink: 0 did the trick for me :)


Existential Capabilities

The design has changed quite a bit relative to https://github.com/scala/scala3/pull/20470. It is written up as a doc comment on object cc.Existentials.

scalac is crashing on opaque types subtyping a capability
import language.experimental.captureChecking

trait A extends caps.Capability

object O:
  opaque type B <: A = A

Stack trace

Exception in thread "main" java.lang.AssertionError: assertion failed: RefinedType(TermRef(ThisType(TypeRef(NoPrefix,module class <empty>)),object O),B,AnnotatedType(TypeAlias(LazyRef(TypeRef(ThisType(TypeRef(NoPrefix,module class <empty>)),trait A))),CaptureAnnotation({TermRef(ThisType(TypeRef(ThisType(TypeRef(NoPrefix,module class scala)),module class caps$)),val cap)},false)))
	at scala.runtime.Scala3RunTime$.assertFailed(Scala3RunTime.scala:8)
	at dotty.tools.dotc.core.Types$RefinedType.<init>(Types.scala:3312)
	at dotty.tools.dotc.core.Types$CachedRefinedType.<init>(Types.scala:3356)

  unhandled exception while running cc on Test.scala

  An unhandled exception was thrown in the compiler.
  Please file a crash report here:
  https://github.com/scala/scala3/issues/new/choose
  For non-enriched exceptions, compile with -Xno-enrich-error-messages.

     while compiling: Test.scala
        during phase: cc
                mode: Mode(ImplicitsEnabled)
     library version: version 2.13.12
    compiler version: version 3.5.1-RC1-bin-SNAPSHOT-git-5454526
            settings: -classpath /home/nki/.cache/coursier/v1/https/repo1.maven.org/maven2/org/scala-lang/scala-library/2.13.12/scala-library-2.13.12.jar:/home/nki/Projects/dotty/library/../out/bootstrap/scala3-library-bootstrapped/scala-3.5.1-RC1-bin-SNAPSHOT-nonbootstrapped/scala3-library_3-3.5.1-RC1-bin-SNAPSHOT.jar -d /
	at dotty.tools.dotc.core.Types$RefinedType$.apply(Types.scala:3365)
	at dotty.tools.dotc.core.Types$RefinedType.derivedRefinedType(Types.scala:3326)
	at dotty.tools.dotc.core.Types$TypeMap.derivedRefinedType(Types.scala:6200)
	at dotty.tools.dotc.core.Types$TypeMap.mapOver(Types.scala:6322)
	at dotty.tools.dotc.cc.Setup$$anon$4.recur(Setup.scala:304)
	at dotty.tools.dotc.cc.Setup$$anon$4.apply(Setup.scala:329)
	at dotty.tools.dotc.core.Types$DeepTypeMap.mapClassInfo(Types.scala:6411)
	at dotty.tools.dotc.core.Types$DeepTypeMap.mapClassInfo(Types.scala:6406)
	at dotty.tools.dotc.core.Types$TypeMap.mapOver(Types.scala:6351)
	at dotty.tools.dotc.cc.Setup$$anon$4.recur(Setup.scala:304)
	at dotty.tools.dotc.cc.Setup$$anon$4.apply(Setup.scala:329)
	at dotty.tools.dotc.cc.Setup.dotty$tools$dotc$cc$Setup$$transformExplicitType(Setup.scala:332)
	at dotty.tools.dotc.cc.Setup.mappedInfo$1(Setup.scala:114)
	at dotty.tools.dotc.cc.Setup.transformSym(Setup.scala:121)
	at dotty.tools.dotc.core.DenotTransformers$SymTransformer.transform(DenotTransformers.scala:72)
	at dotty.tools.dotc.core.DenotTransformers$SymTransformer.transform$(DenotTransformers.scala:67)
	at dotty.tools.dotc.cc.Setup.transform(Setup.scala:53)
	at dotty.tools.dotc.core.Denotations$SingleDenotation.goForward$1(Denotations.scala:833)
	at dotty.tools.dotc.core.Denotations$SingleDenotation.current(Denotations.scala:879)
	at dotty.tools.dotc.core.Types$NamedType.computeDenot(Types.scala:2551)
	at dotty.tools.dotc.core.Types$NamedType.denot(Types.scala:2514)
	at dotty.tools.dotc.ast.Trees$DenotingTree.denot(Trees.scala:258)
	at dotty.tools.dotc.ast.Trees$Tree.symbol(Trees.scala:147)
	at dotty.tools.dotc.ast.tpd$.localOwner(tpd.scala:597)
	at dotty.tools.dotc.ast.tpd$.localCtx(tpd.scala:601)
	at dotty.tools.dotc.ast.Trees$Instance$TreeAccumulator.foldOver(Trees.scala:1753)
	at dotty.tools.dotc.ast.Trees$Instance$TreeTraverser.traverseChildren(Trees.scala:1799)
	at dotty.tools.dotc.cc.CheckCaptures$$anon$2.traverse(CheckCaptures.scala:673)
	at dotty.tools.dotc.ast.Trees$Instance$TreeTraverser.apply(Trees.scala:1798)
	at dotty.tools.dotc.ast.Trees$Instance$TreeTraverser.apply(Trees.scala:1798)
	at dotty.tools.dotc.ast.Trees$Instance$TreeAccumulator.fold$1(Trees.scala:1662)
	at dotty.tools.dotc.ast.Trees$Instance$TreeAccumulator.apply(Trees.scala:1664)
	at dotty.tools.dotc.ast.Trees$Instance$TreeAccumulator.foldOver(Trees.scala:1763)
	at dotty.tools.dotc.ast.Trees$Instance$TreeTraverser.traverseChildren(Trees.scala:1799)
	at dotty.tools.dotc.cc.CheckCaptures$$anon$2.traverse(CheckCaptures.scala:673)
	at dotty.tools.dotc.cc.CheckCaptures$CaptureChecker.checkUnit(CheckCaptures.scala:1251)
	at dotty.tools.dotc.transform.Recheck.run(Recheck.scala:158)
	at dotty.tools.dotc.cc.CheckCaptures.run(CheckCaptures.scala:193)
	at dotty.tools.dotc.core.Phases$Phase.runOn$$anonfun$1(Phases.scala:380)
	at scala.runtime.function.JProcedure1.apply(JProcedure1.java:15)
	at scala.runtime.function.JProcedure1.apply(JProcedure1.java:10)
	at scala.collection.immutable.List.foreach(List.scala:333)
	at dotty.tools.dotc.core.Phases$Phase.runOn(Phases.scala:373)
	at dotty.tools.dotc.transform.Recheck.runOn(Recheck.scala:162)
	at dotty.tools.dotc.Run.runPhases$1$$anonfun$1(Run.scala:343)
	at scala.runtime.function.JProcedure1.apply(JProcedure1.java:15)
	at scala.runtime.function.JProcedure1.apply(JProcedure1.java:10)
	at scala.collection.ArrayOps$.foreach$extension(ArrayOps.scala:1323)
	at dotty.tools.dotc.Run.runPhases$1(Run.scala:336)
	at dotty.tools.dotc.Run.compileUnits$$anonfun$1(Run.scala:384)
	at dotty.tools.dotc.Run.compileUnits$$anonfun$adapted$1(Run.scala:396)
	at dotty.tools.dotc.util.Stats$.maybeMonitored(Stats.scala:69)
	at dotty.tools.dotc.Run.compileUnits(Run.scala:396)
	at dotty.tools.dotc.Run.compileSources(Run.scala:282)
	at dotty.tools.dotc.Run.compile(Run.scala:267)
	at dotty.tools.dotc.Driver.doCompile(Driver.scala:37)
	at dotty.tools.dotc.Driver.process(Driver.scala:201)
	at dotty.tools.dotc.Driver.process(Driver.scala:169)
	at dotty.tools.dotc.Driver.process(Driver.scala:181)
	at dotty.tools.dotc.Driver.main(Driver.scala:211)
	at dotty.tools.dotc.Main.main(Main.scala)

Strange compiler error on this code
import language.experimental.captureChecking

trait Suspend:
  type Suspension

  def resume(s: Suspension): Unit

trait Async(val support: Suspend) extends caps.Capability

class CancelSuspension(ac: Async, suspension: ac.support.Suspension):
  ac.support.resume(suspension)

gives
-- [E007] Type Mismatch Error: Test.scala:11:20 --------------------------------
11 |  ac.support.resume(suspension)
   |                    ^^^^^^^^^^
   |Found:    ((CancelSuspension.this.ac : Async^)^{CancelSuspension.this.suspension*})#
   |  support.Suspension
   |Required: CancelSuspension.this.ac.support.Suspension
   |
   | longer explanation available when compiling with `-explain`
1 error found

The error doesn't come up if Async does not extend Capability and CancelSuspension takes Async^ instead.

Reach capabilities being widened into cap:
//> using scala 3.5.1-RC1-bin-SNAPSHOT
import language.experimental.captureChecking

class Box[T](items: Seq[T^]):
  def getOne: T^{items*} = ???

object Box:
  def getOne[T](items: Seq[T^]): T^{items*} =
    Box(items).getOne

gives
-- Error: /tmp/tmp.yIHCJZJOce/test.scala:9:15 ----------------------------------
9 |    Box(items).getOne
  |    ^^^^^^^^^^^^^^^^^
  |The expression's type (box T^?)^ is not allowed to capture the root capability `cap`.
  |This usually means that a capability persists longer than its allowed lifetime.
1 error found

@natsukagami Last problem should be fixed now.

@natsukagami  I noted that the last example typechecks if the type of collector is given explicitly:
val collector: Collector[T]{val futures: Seq[Future[T]^{fs*}]}
       = Collector(fs)

An unsound snippet that should have compiled:
import language.experimental.captureChecking

// Some capabilities that should be used locally
trait Async:
  //  some method
  def read(): Unit
def usingAsync[X](op: Async^ => X): X = ???

case class Box[+T](get: T)

def useBoxedAsync(x: Box[Async^]): Unit = x.get.read()

def test(): Unit =
  val f: Box[Async^] => Unit = useBoxedAsync

  def boom(x: Async^): () ->{f} Unit =
    () => f(Box(x))

  val leaked = usingAsync[() ->{f} Unit](boom)

  leaked()  // scope violation

Functions like usingBoxedAsync should not type-check, as x.get.read() is charging {x*} to the closure of usingBoxedAsync, which should be rejected.

@Linyxus I need some more explanations why this is unsound. The typeckecked example is here:
  @SourceFile("leak-problem.scala") final module class leak-problem$package()
     extends Object() {
    private[this] type $this = leak-problem$package.type
    private def writeReplace(): AnyRef =
      new scala.runtime.ModuleSerializationProxy(
        classOf[leak-problem$package.type])
    def usingAsync[X](op: Async^ => X): X = ???
    def useBoxedAsync(x: Box[box Async^]): Unit = x.Async.read()
    def test(): Unit =
      {
        val f: Box[box Async^] => Unit =
          {
            def $anonfun(x: Box[box Async^]^?): Unit = useBoxedAsync(x)
            closure($anonfun)
          }
        def boom(x: Async^): () ->{f} Unit =
          {
            def $anonfun(): Unit =
              {
                f.apply(Box.apply[box Async^{x}](x))
              }
            closure($anonfun)
          }
        val leaked: () ->{f} Unit =
          usingAsync[box () ->{f} Unit](
            {
              def $anonfun(x: Async^): () ->{f} Unit = boom(x)
              closure($anonfun)
            }
          )
        leaked.apply()
      }
  }

There's not a single reach capability in that program.

The reach capability appears in the expression x.get.read(), since x's type is Box[Async^] and the type parameter of Box is covariant, it gets reach-refined to Box[Async^{x*}].
I have a modified version of this snippet which better shows the problem:
import language.experimental.captureChecking

// Some capabilities that should be used locally
trait Async:
  //  some method
  def read(): Unit
def usingAsync[X](op: Async^ => X): X = ???

case class Box[+T](get: T)

def useBoxedAsync(x: Box[Async^]): Unit =
  val t0 = x
  val t1 = x.get
  t1.read()

def test(): Unit =
  val f: Box[Async^] => Unit = useBoxedAsync

  def boom(x: Async^): () ->{f} Unit =
    () => f(Box(x))

  val leaked = usingAsync[() ->{f} Unit](boom)

  leaked()  // scope violation

The tree after cc:
    def useBoxedAsync(x: Box[box Async^]): Unit =
      {
        val t0: Box[box Async^{x*}]^? = x
        val t1: Async^{x*} = x.Async
        t1.read()
      }

Some weird interaction between caps, opaque types and inlines...
//> using scala 3.6.0-RC1-bin-SNAPSHOT

import language.experimental.captureChecking

trait Async extends caps.Capability:
  def group: Int

object Async:
  inline def current(using async: Async): async.type = async
  opaque type Spawn <: Async = Async
  def blocking[T](f: Spawn ?=> T): T = ???

def main() =
  Async.blocking:
    val a = Async.current.group

gives
-- Error: test.scala:15:25 -----------------------------------------------------
15 |    val a = Async.current.group
   |                         ^
   |The expression's type box ((contextual$1 : Async.Spawn^) & $proxy1.Spawn)^ is not allowed to capture the root capability `cap`.
   |This usually means that a capability persists longer than its allowed lifetime.

Making Spawn not opaque or making current not-inline would make the code compile.

@natsukagami Should be fixed by latest commit

//> using scala 3.6.0-RC1-bin-SNAPSHOT

import language.experimental.captureChecking

trait Source[+T]

def<EMAIL_ADDRESS>sources: Seq[Source[T]^]): Source[T]^{sources*} = ???

def raceTwo[T](src1: Source[T]^, src2: Source[T]^): Source[T]^{} = race(Seq(src1, src2))

this compiles and returns a Source that does not capture src1 and src2.

@natsukagami Should be fixed by latest commit

Seems to not work with spread parameters
//> using scala 3.6.0-RC1-bin-SNAPSHOT

import language.experimental.captureChecking

trait Source[+T]

def<EMAIL_ADDRESS>sources: (Source[T]^)*): Source[T]^{sources*} = ???

def raceTwo[T](src1: Source[T]^, src2: Source[T]^): Source[T]^{} =
  // race(Seq(src1, src2)*) // this fails
  race(src1, src2) // this compiles

Inline functions capturing a parameter on the result will fail if passed a pure argument:
//> using scala 3.6.0-RC1-bin-SNAPSHOT

import language.experimental.captureChecking

trait Listener[+T]

inline def consume[T](f: T => Unit): Listener[T]^{f} = ???

val consumePure = consume(_ => ())

errors with
-- Error: test.scala:7:50 ------------------------------------------------------
7 |inline def consume[T](f: T => Unit): Listener[T]^{f} = ???
  |                                                  ^
  |(f$proxy1 : (x$0: Any) ->? Unit) cannot be tracked since its capture set is empty

@natsukagami Latest problems should be fixed now. Let's see what you come up with next!

Not sure if this is a bug, but how should programmers deal with the following:
import language.experimental.captureChecking // compiles just fine *without* this import

trait DSL:
    type Now[+A]

    def lam[A,B](fun: Now[A] => Now[B]): Now[A => B]
    def app[A,B](fun: Now[A => B], arg: Now[A]): Now[B]

    def prog[A](e: Now[A]): Now[A]

    def test =
        prog[Int => Int]:
            lam(x => x)

With capture checking enabled, the meaning of => is changed to be a tracked type and we get the following error:
-- [E007] Type Mismatch Error: local/dsl.scala:14:12 ---------------------------
13 |        prog[Int => Int]:
14 |            lam(x => x)
   |        ^
   |        Found:    DSL.this.Now[box Int => Int]
   |        Required: DSL.this.Now[Int => Int]
   |
   |        Note that the expected type DSL.this.Now[Int => Int]
   |        is the previously inferred result type of method test
   |        which is also the type seen in separately compiled sources.
   |        The new inferred type DSL.this.Now[box Int => Int]
   |        must conform to this type.

The problem is the explicit type annotation Int => Int, and there is no way to express in the surface syntax (that I'm aware of) we want prog[box Int => Int]. A rather drastic way to get it to compile under capture checking is making all the arrows in the file pure ->.

Simply importing language.experimental.captureChecking appears to break conformance checks:
import language.experimental.captureChecking

trait Dsl:

    sealed trait Nat
    case object Zero extends Nat
    case class Succ[N <: Nat](n: N) extends Nat

    type Stable[+l <: Nat, +b <: Nat, +A]
    type Now[+l <: Nat, +b <: Nat, +A]
    type Box[+A]
    def stable[l <: Nat, b <: Nat, A](e: Stable[l, b, A]): Now[l, b, Box[A]]

    def program[A](prog: Now[Zero.type, Zero.type, A]): Now[Zero.type, Zero.type, A]

    //val conforms: Zero.type <:< Nat = summon
    // ^ need to uncomment this line to compile with captureChecking enabled

    def test =
        program:
            val v  : Stable[Zero.type, Zero.type, Int] = ???
            stable(v)
//          ^
// Type argument Dsl.this.Zero.type does not conform to upper bound Dsl.this.Nat

@bracevac
-- [E007] Type Mismatch Error: local/dsl.scala:14:12 ---------------------------
13 |        prog[Int => Int]:
14 |            lam(x => x)
   |        ^
   |        Found:    DSL.this.Now[box Int => Int]
   |        Required: DSL.this.Now[Int => Int]
   |
   |        Note that the expected type DSL.this.Now[Int => Int]
   |        is the previously inferred result type of method test
   |        which is also the type seen in separately compiled sources.
   |        The new inferred type DSL.this.Now[box Int => Int]
   |        must conform to this type.

Here it simply requires that you need to give an explicit type to test. It could be Any or it could be Now[Int => Int]. Both work.

@natsukagami The latest example you have is not supposed to compile. What I could do is add some way to give a hint why it failed:
15 |  col.add(Future(() => 25)) // error
   |          ^^^^^^^^^^^^^^^^
   |Found:    Future[Int]{val a: (async : Async^)}^{async}
   |Required: Future[Int]^{}
   |
   |Note that a capability Collector.this.futs* in a capture set appearing in contravariant position
   |was mapped to col.futs* which is not a capability. Therefore, it was under-approximated to the empty set.

@bracevac Your latest problem should be fixed with last commit.

Simply importing language.experimental.captureChecking appears to break conformance checks

The conformance check was done by the capture checker. And that is run only if the language import is present. So that explains it. But it was still a bug since no error should have been issued.

@natsukagami For the latest example, maybe you could try explicit capture set polymorphism?

@bracevac I think it would be good to get this merged soon. We are getter further and further away from the main branch, in a good way.


[3.x & 4.x] Can't backspace pre-existing text after grab_focus TextEdit & LineEdit on Mobile

Godot version
3.5.2 rc2
4.0 rc2
System information
Android 12 and IOS 16.3
Issue description
Can't backspase/delete on mobile the text already present in a TextEdit and LineEdit after gaining focus with grab_focus(), not with touch.
Steps to reproduce

Type text in a TextEdit/LineEdit
Switch or release the focus of the TextEdit/LineEdit
Gain focus of the TextEdit/LineEdit back using grab_focus()
Try to backspace/delete the text. Can't.

Minimal reproduction project
Can't_backspace_after_grab_focus.zip
Can't_backspace_text_after_grab_focus_4.x.zip

Issue present in godot 4

Issue present in Godot 4.2.1

Issue still present in Godot 4.3.


build SCons packages with python tool 'build'

Pushed to see if the GH Action will build this way (works locally).  This an experiment to respond to the Py Packaging Authority's plea to "not call setup.py directly, use one of the tools".  Don't see how to build the .zip file of the package this way, so at the moment that's commented out, with a question of whether we need. Does build the zipfile of the portable version.  Updated: restored the old way of building the sdist-zipfile.
Update: this does seem to work, but I'll leave it as WIP, and it can be grabbed if wanted.
Changes only SCons' own build, not SCons itself, so no docs/tests/etc.
Contributor Checklist:

[ ] I have created a new test or updated the unit tests to cover the new/changed functionality.
[ ] I have updated CHANGES.txt (and read the README.rst)
[ ] I have updated the appropriate documentation

From the Verify Package section of the GH Actions report:

1s
Run ls -l build/dist
total 23932
-rw-r--r-- 1 runner docker  4156653 Nov  5 19:23 SCons-4.2.0-py3-none-any.whl
-rw-r--r-- 1 runner docker  3120289 Nov  5 19:23 SCons-4.2.0.tar.gz
-rw-r--r-- 1 runner docker 10189706 Nov  5 19:25 scons-doc-4.2.0.tar.gz
-rw-r--r-- 1 runner docker  3018361 Nov  5 19:25 scons-local-4.2.0.tar.gz
-rw-r--r-- 1 runner docker  4017901 Nov  5 19:25 scons-local-4.2.0.zip
SCons by Steven Knight et al.:
	SCons: v4.2.0.cf664d3da93b5ad1eac48e4b5688e4fdea6231e6, Fri, 05 Nov 2021 19:22:24 +0000, by runner on fv-az269-943
	SCons path: ['/home/runner/work/scons/scons/build/scons-local/scons-local-4.2.0/SCons']
Copyright (c) 2001 - 2021 The SCons Foundation

Is the pypi build module only Python 3.7+?
https://pypa-build.readthedocs.io/en/latest/installation.html

I don't think so, I think the limitation is they're only testing with supported Python versions, which 3.6 no longer is.  However, will have to verify that - if it matters. I'd doubt anyone is going to build the wheel to upload to pypi with the oldest Python version.

I don't think so, I think the limitation is they're only testing with supported Python versions, which 3.6 no longer is. However, will have to verify that - if it matters. I'd doubt anyone is going to build the wheel to upload to pypi with the oldest Python version.

Indeed.

Merging


cleanup(OWNERS): remove inactive approvers

What type of PR is this?
/kind cleanup
/kind documentation
Any specific area of the project related to this PR?
/area pkg
What this PR does / why we need it:
For https://github.com/falcosecurity/falco/issues/2115, this PR moves inactive approvers (who had very little or zero contributions over the past 6 months) from approvers to emeritus_approvers in OWNERS.
Which issue(s) this PR fixes:
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jasondellaluce
To complete the pull request process, please assign leodido after the PR has been reviewed.
You can assign the PR to them by writing /assign @leodido in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@fntlnz, given https://github.com/falcosecurity/falco/issues/2122 I understand that you'd like to step down as maintainer of this repository, so can you please remove your Change Request so that other maintainers can proceed?
This PR is overlapping with the #74 that you opened, so if you prefer to proceed with that one please sign-off your commit to unblock the DCO.
Of the two, I would prefer proceeding with this one that puts your name under the emeritus_approvers section instead of removing you from OWNERS entirely. Looking forward to hearing back from you.

@jasondellaluce: Closed this PR.

In response to this:

This PR has been on hold for 12 days now and it is still blocked because of the pending "change requests". However, @FedeDP and I agree to merge it. @jasondellaluce could I ask to recreate this PR from scratch so that we can merge it, please?
Thank you in advance.

Closing this in favor of #76.
/close

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


PWA-956 optimize pdp reviews

Pull Request Test Coverage Report for Build 1690

33 of 41 (80.49%)  changed or added relevant lines in 13 files are covered.
9 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.3%) to 40.874%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

components/Reviews/components/AllReviewsLink/connector.js
1
4
25.0%

components/Reviews/connector.js
1
6
16.67%

Files with Coverage Reduction
New Missed Lines
%

components/Reviews/components/List/components/Review/index.jsx
9
0.0%

Totals

Change from base Build 1689:
-0.3%

Covered Lines:
1446

Relevant Lines:
3338

💛  - Coveralls


No focus/blur visual feedback for buttons

Steps to reproduce:

Start screenshot tests
Go to button screenshots
Bring to focus a button using the keyboard

Actual Results:
Background color of the button should change
Expected Results:
Background color of the button doesn't change

This would require the MDC Ripple component to expose public focus and blur methods in the foundation, similar to activate and deactivate.


when should we expect the next npm-published version?

can't wait...
any timeline for that?

You're the prime contributor to this next release. What's your confidence level in it as a patch release?

Well.
I know that about all my PRs we discussed and made sure we're backward compatible.
At least by design.
I did my best to add tests - I was stopped only on tests for connect_middeware - which has no unit-test suite. however, I do see it's involved in e2e tests - so...
If there are more tests you'd like to add to the test suite - let's discuss it - I'll try to be quick about it

No, I don't have anything in mind. I just wanted to get your feedback. I think we can move forward with what we have now.

Release notes:  https://github.com/theganyo/swagger-node-runner/releases/edit/untagged-5ed17a7cd68bc47bdda3
Please let me know of any comments / corrections.

it won't let me open the link 😮
is it a permissions thing?

Must be permissions. Ok, I just went ahead and published it (both git & npm). Please let me know if you see any issues.
https://github.com/theganyo/swagger-node-runner/releases/tag/v0.7.1

Scott - that's wonderful!
Now I can decouple my handlers from ctx.response!
For my next trick - decouple handlers from ctx.request. Basically - everything is on ctx.request.swagger.params, so I think we can spare the user following this trail...
Anyway - I'll open a new thread for that :)

Thanks again!! 😄

Ah - one point missed from the release notes:
You can now use fitting/swagger-cors instead fitting/cors of  and include your node_modules in fittingsDirs

Thanks. Updated.

swell.
I just found there's another way to do it
  - _cors:
    name: cors
    type: user     # <--  look it only in user fittings
    ...


Cannot figure out how to set the Javascript (Analytics.JS) source's settings

The documentation for segment_source suggests that it may be possible to set a source's settings with it.
It doesn't appear to work.
Try this:
terraform {
  required_version = ">= 1.0"

  required_providers {
    segment = {
      source  = "segmentio/segment"
      version = "1.0.0"
    }
  }
}

resource "segment_source" "test" {
  slug    = "test_source"
  name    = "Test Source"
  enabled = true

  metadata = {
    id = "IqDTy1TpoU" # Javascript (Analytics.JS)
  }

  settings = jsonencode({
    website_url = "https://www.segment.com"
  })
}

Applying that creates a source whose Settings looks like this:

No value in the "Website URL" setting.
Am I using the wrong key in the setting value in the resource?  Is there a place in the documentation where the correct key strings can be found for each source?

Thanks for your question! Can you try the format from the documentation here? The settings should be in JSON.

@deanhuynh The documentation has this:
  settings = jsonencode({
    "token" : "xyz321",
  })

while my test case has:
  settings = jsonencode({
    website_url = "https://www.segment.com"
  })

Use of colons in Terraform map object literals was supported in Terraform v0.11, but from Terraform v0.12 onward has been changed to favor using the equal sign as the separator, e.g., <KEY> = <VALUE>
See this issue for more details.
All this to say: exactly how would you like me to change the sample TF file I provided in this issue?
Thanks!

You're absolutely right, sorry misunderstood how jsonencode works in Terraform. This actually looks to be an gap with our Public API not allowing the setting of this specific field for the Javascript source. Your setup should work for any other source settings (which you can see the options for by calling this endpoint and taking a look at the options field. I'll put in a ticket to fix this for Javascript sources and let you know when it is done.

Hi, this issue should be fixed now. Please use website_url as the setting to set the URL for Javascript sources. Thanks for your patience and let me know if you run into any other issues!

Thanks, @deanhuynh!  I can confirm that it's working as expected now.


Only search relative paths when @-mentioning files in chat

[This depends on a function added in https://github.com/sourcegraph/cody/pull/2215 so this will fail bots until that lands and I rebase/merge]
Fixes https://github.com/sourcegraph/cody/issues/2208
Test plan

Run pnpm test:e2e at-file to run the updated test, or
Open chat, and mention a file using @ but type part of the file path outside of the folder opened in VS Code (eg. if you have C:\Source\cody\ open, type source`)
Ensure that the results don't list every file because source exists in their full fspaths

Hmm, there's something odd going on now. With this change, .vscode\settings.json\ shows up in the search results for @vgo (it has no g!), which results in the test selecting the wrong item - but that also results in and @vg being duplicated on the end:
https://github.com/sourcegraph/cody/assets/1078012/3c833a18-cfa1-4776-867b-59fbad9610bf
This is reliably reproducible for me, and feels like two bugs (non-matched items in the results, and the duplicated text). I might not get chance to look into this before Friday now, so if this is important and anyone else has time, feel free to take a look!

it has no g!

lol, it very much as a g 😄 I'll update the test and file another bug about the duplication (which seems to occur only when you select a file that's already listed).

I've filed https://github.com/sourcegraph/cody/issues/2243 about the bug.
@dominiccooney heading off, but if you're happy with this as-is and the last bots go green feel free to merge :)


BREAKING CHANGE: SqlRSSecureConnectionLevel: Remove this resource

Details of the scenario you tried and the problem that is occurring:
I suggest we move SecureConnectionLevel parameter to the SqlRS resource and remove SqlRSSecureConnectionLevel.
This was initially suggested in issue #587, but that issue is more to add SSL functionality. We could start by adding the parameter SecureConnectionLevel to the SqlRS resource. This would improve the SqlRS resource, and remove a lot of technical debt.
The resource SqlRSSecureConnectionLevel only changes value of property SecureConnectionLevel, so it's a bit unnecessary for it to be a separate resource.
The DSC configuration that is using the resource (as detailed as possible):
n/a
Version of the Operating System, SQL Server and PowerShell the DSC Target Node is running:
n/a
What module (SqlServer or SQLPS) and which version of the module the DSC Target Node is running:
n/a
Version of the DSC module you're using, or 'dev' if you're using current dev branch:
Dev

I wrongly wrote deprecate when I meant remove. I updated the issue title, and also added breaking change label.


Schlage Door Lock change user codes

trying to figure out how to get back the ability to change door lock codes.  i see nothing under the gui but on the mqtt side there is a topic 99/1 that seems to hold the data.  i believe its supposed to be in hex but its returning an array of numbers.  Any thoughts on how to get into this functionality?

Never got a device that uses that class so I don't know how to handle that (should be COMMAND_CLASS_USER_CODE 0x63) Maybe @Fishwaldo could help?

In 1.4 it’s exposed as a Raw Byte string. For some devices you can convert to ASCII to get the value, for others like Tag Readers it’s a series of bytes. There was ambiguity from the specs in how data should be represented.
In 1.6 by default it’s exposed as a ValueString. This works for 75% of the devices on the market. For those 25% we can set a option in the config file to also expose the value as a Raw Bytes. (To handle those devices that don’t follow the specifications exactly now that it’s clarified).
Also the way codes are “cleared” has changed in 1.6. The release notes has details.

So would you recommend i build my own image of zwave2mqtt w/ 1.6 instead of 1.4?

Forward thinking 1.6 is the best, but @robertlando has to confirm if the CC is supported and if ValueRAW works for those “weird” devices.

I think @ksuclipse could give a try with his own built image using ozw 1.6 and than tell if it works

still going to try this, unfortunately havent had time

build new docker image off of most recent commit and swapped out for 1.6.  unfortunately no go, nothing came up like it should have so theres still a lot of inconsistencies w/ 1.6 and openzwave

Need to make 1.6 fully supported on openzwave-shared in order to make it supported on zwave2mqtt
Daniel

On 26 Sep 2019, at 04:43, ksuclipse<EMAIL_ADDRESS>wrote:
Reopened #113.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


[NCL-8838] Change useDataBuffer hook to output all available data soon as possible

Depends on: https://github.com/project-ncl/pnc-web-ui-react/pull/577

Hi @patrikk0123 , let's wait for #577 to be merged first, I would like to improve this PR a little bit so that setDataOut is performed only when necessary, as there is currently an infinite loop. Here's a basic idea:
const throttleCallback = throttle(() => {
    console.log('useDataBuffer -> setInterval -> setDataOut');
    setDataOut(dataIn.current);
  }, 1000);

  const addLines = useCallback(
    (lines: string[]) => {
      dataIn.current = [...dataIn.current, ...preprocessor(lines)];

      console.log('useDataBuffer -> addLines');

      throttleCallback();
    },
    [preprocessor]
  );


cmd/compile: internal compile error when using sync.Pool: mismatched zero/store sizes

What version of Go are you using (go version)?

$ go version
go version go1.14.4 linux/amd64

Does this issue reproduce with the latest release?
Yes, go1.14.4 is the latest release (released about a week ago). I've also reproduced this using go1.14.1.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/petsta/.cache/go-build"
GOENV="/home/petsta/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GONOPROXY="github.com/nearmap"
GONOSUMDB="github.com/nearmap"
GOOS="linux"
GOPATH="/home/petsta/go"
GOPRIVATE="github.com/nearmap"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/petsta/bug/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build913647161=/tmp/go-build -gno-record-gcc-switches"

What did you do?

I attempted to compile the following program, which is a minimum working example that exhibits the problem:
https://play.golang.org/p/C5P2Zh6X_i-
package main

import "sync"

type foo struct {
    bars [2]bar
}

type bar struct{}

var pool = sync.Pool{
    New: func() interface{} {
        return new(foo)
    },
}

func newFoo() *foo {
    f := pool.Get().(*foo)
    *f = foo{}
    return f
}

func main() {
    f := newFoo()
    *f = foo{}
}

What did you expect to see?
The program to compile successfully.
What did you see instead?
The following is emitted from the go toolchain:
./main.go:24:13: internal compiler error: 'main': mismatched zero/store sizes: 0 and 1 [v27 = Zero <mem> {foo} v29 v9]

Please file a bug report including a short program that triggers the error.
https://golang.org/issue/new

I can reproduce this with Go 1.12, 1.13, and 1.14, but it is fixed on tip.

Do you really need an array of elements of zero size?  Given that this is fixed on tip, I'm trying to judge how important it is to backport a fix to 1.14.

Do you really need an array of elements of zero size?

bar only has zero size in the minimum working example -- in the 'real' program bar has many fields (sorry, my minimum working example may have been a bit misleading in that regard).

Given that this is fixed on tip, I'm trying to judge how important it is to backport a fix to 1.14.

For me personally, I'm able to work around the problem by replacing *f = foo{} with code that zeros out each field within foo manually (e.g. f.bars = [2]bar{}). In my situation, this is new code as opposed to existing code that worked in a previous version of Go, so a backport is less important for me.

According to bisection, this was fixed by 396833c

Thanks for the bisection.
That CL is just an optimization. It's probably optimizing away the code that triggers the bug, but I suspect there may still be some underlying bug here.

The underlying bug is just a mistaken invariant check. For the opcode (Zero {typ} ptr mem), it checks that the base type of the pointer and the aux type field have the same size. That's not always going to be the case, though. The typ field is authoritative. The ptr field can have a different base type in situations like the OP's program, because the pointer comes from the data portion of a type-casted interface{}. We give the interface data field a byte* type because we don't know its actual base type at the time it is loaded. Only when the cast succeeds do we know the size that needs to be zeroed.
I'll see if I can make a repro that works at tip.
The fix is just to remove the invariant check. It isn't generating any wrong code that I can see. Might be worth auditing all our rules to make sure we're not depending on the types of ssa.Value inputs. Reminds me of #37753.

@gopherbot please open backport issues for 1.14 and 1.13.
This issue can cause the compiler to crash. The compiler was checking an invariant that doesn't, and does not need to, hold.


classNames order mismatch between VSCode Prettier extension and prettier CLI

Seeing similar errors to #19 & #21 in regards to class names order mismatches... In VS Code with the ESLint extension + Prettier extension, class names are formatted as expected and VSCode doesn't show any errors or warnings. However, when running prettier OR eslint (with prettier plugins) from the command line it's complaining that the classnames are in the wrong order... this is in direct contradiction to the rules described in the blog post, which says custom class names should come first.
// Correct className in editor, no warnings shown...

prettier warning output...
→ npx prettier --check src
Checking formatting...
[warn] src/components/header.tsx
[warn] Code style issues found in the above file(s). Forgot to run Prettier?

... eslint warning output...
→ npx eslint src
./src/components/header.tsx
  6:23  error  Replace `wrapper·grid·h-full·grid-cols-12·items-center·gap-4` with `grid·h-full·grid-cols-12·items-center·gap-4·wrapper`  prettier/prettier

As you can see, it wants to put wrapper at the end for some reason.
Here's my eslint config:
{
  "plugins": ["prettier"],
  "extends": ["next/core-web-vitals", "plugin:prettier/recommended"],
  "overrides": [
    {
      "files": ["**/*.ts?(x)"],
      "plugins": ["@typescript-eslint"],
      "extends": "plugin:@typescript-eslint/recommended",
    }
  ]
}

And relevant packages...
    "@typescript-eslint/eslint-plugin": "^5.10.2",
    "autoprefixer": "^10.4.2",
    "eslint": "8.8.0",
    "eslint-config-next": "12.0.10",
    "eslint-config-prettier": "^8.3.0",
    "eslint-plugin-prettier": "^4.0.0",
    "postcss": "^8.4.6",
    "prettier": "2.5.1",
    "prettier-plugin-tailwindcss": "^0.1.4",
    "tailwindcss": "^3.0.18",
    "typescript": "4.5.5"

And for what it's worth, here's the very simple plugin for the custom .wrapper class...
    plugin(({ addUtilities, theme }) => {
      const wrapper = theme("wrapper");

      addUtilities({
        ".wrapper": {
          width: "100%",
          maxWidth: wrapper.maxWidth,
          paddingLeft: wrapper.padding,
          paddingRight: wrapper.padding,
          marginLeft: "auto",
          marginRight: "auto",
        },
      });
    })

Hey! Since the wrapper class is defined using a Tailwind plugin it will be sorted alongside other Tailwind classes, and should appear as the last utility in your class list, before any modifiers like hover or lg.
I was explicit about that in the blog post:

This is the correct order:

Not sure how setting up Prettier with ESLint actually works, does it continuously run Prettier in the background to compare the output against your actual code and warn if anything is wrong? We don't have any official ESLint plugin or anything for class name order so unless that's how it works I wouldn't expect any warnings.
Going to close as "not a bug" (the order is right), but happy to continue the discussion here or in the Tailwind CSS discussions area 👍🏻

Ah, missed that crucial bit! Sorry about that.
So prettier's eslint plugin is correct, but the eslint extension is contradicting it. I'll start digging there.

I ended up moving this custom utility class out of the plugins in my tailwind config and into the @layer utilities layer in my CSS entry point.
@layer utilities {
  .wrapper {
    @apply mx-auto w-full max-w-screen-xl px-6;
  }
}

That seems to resolve any mismatches and puts it in the the intended order for custom classnames not added via a plugin:

I assume this plugin isn't concerned with CSS files or the order of classes in the @apply directives. Which is totally fine, I'm happier having wrapper first in the classlist. But I do wonder why the extension thought that wrapper was a custom class instead of a class added via a plugin, and the cli got it right. Maybe the extension is out of date.
Anyways, thanks @adamwathan, love the official plugin and the Tailwind ecosystem.


Pages update auto built from graphscope/web, commit 287acca

What do these changes do?

Related issue number

Fixes

 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.


feat: issue template for new feature 💡

Description

This issue template is designed to streamline the process of requesting new features for our project.
If you have an idea for an exciting new functionality or improvement, please use this template to provide the necessary details and context for the feature request.

Screenshot

Hey there @Anupkjha2601 👋🏻
Please make sure to assign this issue to me to make the work done!
Thank you.

Hey there @Anupkjha2601 👋🏻
Please make sure to assign this issue to me to make the work done!
Thank you.


Push Docker images to GitHub

Now that docker hub is removing free storage of images, we should move hosting of images to GitHub

no longer necessary as dockerhub have changed their mind


adding some hover effects in css

hey maintainer, can I add some hover effects on frontend-flow projects , could you please assign me for that ?

Hey @anishaxtha sure! You can do that. You can also add some transition property to make it look better !
But before that please star the repo ⭐⭐ . Happy coding!


envoy: use errors.Is(..., net.ErrClosed) instead of string matching

Use errors.Is to check whether err (or some error that it wraps) is
net.ErrClosed instead of comparing error strings.
Same for syscall.EINVAL.

net.ErrClosed is only exported in gotip, not in Go 1.15. Will reopen once Go 1.16 is release and we use it.


(ccs) do not prefix sal services with instrument- on lsstcam-mcm hosts

For historical reasons, the ccs SAL services use an instrument- prefix (eg comcam-) on comcam and auxtel, but on lsstcam no prefix is used.

@glennmorris Rebasing on current production should fix the CI failure.


CSS property completion with semicolon: multiple semicolons

If the wrong property is completed and you backspace to delete then tab to complete the correct property, another semicolon is outputted.
Suggestions:
On the deletion of the colon, delete the semicolon.
OR
On completion of the correct property, check to see if semicolon already exists.

Verifier:

Try you can complete .foo { colo|: ; } to get . foo { color: ; }
Try you can complete .foo { colo; } to get .foo { color: ; }


Backport 2.16: Fix compilation failure when MBEDTLS_SSL_HW_RECORD_ACCEL is enabled

Description
This is a backport of https://github.com/ARMmbed/mbedtls/pull/2262, please refer to that PR description for details.
Status
READY

I force-pushed in order to resolve a conflict and CI errors that I suspect were due to the outdated base branch. I took the opportunity to squash commits that fixed previous commits in the same branch, and also made the new build test stricter (in line with the base PR).
The previous branch is at https://github.com/mpg/mbedtls/tree/mbedtls-2.16-iotssl-2544-deprecate-record-accel-andres but I suspect it's easier to review again from scratch.

This has two approvals (Paul's a team member even if it doesn't show in github yet), a passing CI and no conflicts, so it's ready for merge (even if github can't see it yet).


Added automated available skins configuration data using files from directory instead of manually editing index.html

what title says

Dynamically load cone skins from files


Bam reader

SAM/BAM/CRAM reader [#3]
get basic test coverage high [#5]
restore custom PAF reader [#8]
replace noodles with rust-bio fasta parsing

Codecov Report

Merging #14 (f8ade7c) into main (c8e0179) will decrease coverage by 0.78%.
The diff coverage is 98.21%.

@@             Coverage Diff             @@
##              main      #14      +/-   ##
===========================================
- Coverage   100.00%   99.21%   -0.79%
===========================================
  Files            4        4
  Lines          177      256      +79
===========================================
+ Hits           177      254      +77
- Misses           0        2       +2

Impacted Files
Coverage Δ

src/align.rs
98.78% <98.16%> (ø)

src/cli.rs
100.00% <100.00%> (ø)

tests/app.rs
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

Configured codecov due to this match statement I have no idea how to test:
let reader: Box<dyn BufRead> = match path.file_name() {
    Some(os_str) => match os_str.to_str() {
        Some("-") => Box::new(BufReader::new(std::io::stdin())),
        Some(_) => Box::new(BufReader::new(File::open(path)?)),
        None => return Err(ReadAlignmentError::FileInputError()),   // not captured
    },
    None => return Err(ReadAlignmentError::FileInputError()),
};


User assert pattern in test code of exporterhelper

address #266
Signed-off-by: Hui Kang<EMAIL_ADDRESS>

This is the first attempt to address #266 . Could anyone help to take a look? If it is on the right direction, I will complete the change for the exporter package. Thanks.

I will take first pass.

This is looking good thank you! Please apply the comments to all applicable places where you are making these changes.


Fix development pod hash affected by path change

Description
This is a tricky fix now, I intercepted twice to make the path an absolute path. Obviously, this might cause issues in other scenarios. I hope we can find a solution that is compatible with various cases. Until then, I will use this branch to ensure the work can continue.
By the way, since we are using a mono repo, the relative paths for development pods are consistent, so the value of PODS_TARGET_SRCROOT remains constant. Therefore, when :path in Podfile changes, this value itself will also affect the result of the hash.
References
https://github.com/swiftyfinch/Rugby/issues/279
Checklist (I have ...)

[ ] 🧐 Followed the code style of the rest of the project
[ ] 📖 Updated the documentation, if necessary
[ ] 👨🏻🔧 Added at least one test which validates that my change is working, if appropriate
[ ] 👮🏻♂ Run make lint and fixed all warnings
[ ] ✅ Run make test and fixed all tests

❤ Thanks for contributing to the 🏈 Rugby!

@cragod Hey, why did you decide to close your request?
I don't have enough free time right now to deep dive, but I'll return to this maybe on weekend.

I think I clicked it by mistake😅

@cragod Hey, why did you decide to close your request?

I think I clicked the wrong button.


Change ruby-class of rvm wrapper to Jenkins::Tasks::BuildWrapperProxy

This is due to version of jenkins-plugin-runtime that rvm-plugin depends has been changed to 0.2.3. This PR should partially fix JENKINS-37422.

Dup of #897, closing...


Ability Tags not working

Hello! I started using this framework couple days ago. Seems good so far. But it seems like Cancel Abilities with Tags, Block Abilities with Tags and  Activation Owned Tags doesn't work. Should i implement logic for them myself? If so how would i do that?

Hi, thanks for trying out this package.  Those haven't been implemented yet.
Cancel Abilities With Tags
Cancel existing abilities on a character.  Usually, the lifetime of an ability itself is quite short (most of the lingering effects should happen with a GameplayEffect), so this would be used where e.g. the animation hasn't finished.   You could implement this functionality yourself by looping through all active abilities on the Owner in ActivateAbility() in your ability class, and calling CancelAbility() on the abilities that have one of these tags.
Block Abilities With Tags
Block new abilities with these tags from starting, e.g. if your character has a "I'm in space" tag, you could remove the "breathing" ability (sorry for the poor example).  You can either override CanActivateAbility() in AbstractAbilitySpec to loop through all active abilities on the player, check their BlockAbilitiesWithTags, and return false if they have those tags.
Activation Owned Tags
They're there to assign tags to the player while an ability is active.  They're there for use in your own code - e.g. if you want to do something yourself (such as modify UI), you can use these tags to determine which abilities are currently active.
I've made a number of major changes to the framework, which is currently in development in the 2d-sample branch, the most notable being using prefabs instead of ScriptableObjects for various things (as suggested in #22) (but the things you've mentioned above are not implemented in that branch, either).


client should support client supplied metadata

The current JS client M-Lab provides supports the addition of metadata about the client.
The ndt7-js reference client should also support this.

The mechanism I'm thinking of supporting is the following:

clients provide extra http parameters to the locate API request.
the locate api copies "safe" parameters from that request to the websocket URLs generated for access to the measurement service

For example:
https://locate.measurementlab.net/v2/nearest/ndt/ndt7?client_name=foo&client_version=0.1.1

Generates URLs like:
wss://ndt-mlab1-foo01.mlab-oti.measurement-lab.org/ndt/v7/download?client_name=foo&client_version=0.11&access_token=...

This would preserve the current behavior where clients only use the urls provided by the locate api without needing to manipulate them.

The method described above is now in production, and in use by at least two clients. Please use this method for the Javascript client also.

At a minimum the ndt7-js client should provide a client_name= parameter to the locate request identifying that this is the ndt7-js client. The ndt7-client-ios and ndt7-client-android clients already do this. Ideally, the ndt7-js client would also provide client_version=. These variables would be propagated to the ndt client metadata.


PR: Add path widgets

Added a new widget to help selecting and displaying a file or a folder.

Hello @jnsebgosselin! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file qtapputils/widgets/path.py:

Line 36:9: E731 do not assign a lambda expression, use a def


Twitter list of speakers

Hey @lenae what do you think about making a twitter list for all our speaker? 2016-speakers?
http://citycampnc.org/speakers/
Is that something you can help with?

Got it!
On Tuesday, September 20, 2016, Jason Hibbets<EMAIL_ADDRESS>wrote:

Assigned #303 https://github.com/codeforraleigh/CityCampNC/issues/303
to @suzanneccnc https://github.com/suzanneccnc.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/CityCampNC/issues/303#event-795642903,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARrpxmsdQiYEjqVswf43ss4q4EKK8qVGks5qr9-ugaJpZM4KBn7y
.

Sure, do you want some sort of widget like you mentioned or @suzanneccnc do you have something else in mind?

separate but related - do you need a cheat sheet with all the handles for live tweets?

I'll post that on the schedule page
On Tue, Sep 20, 2016 at 6:01 PM, Chris Mathews<EMAIL_ADDRESS>wrote:

separate but related - do you need a cheat sheet with all the handles for
live tweets?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/CityCampNC/issues/303#issuecomment-248448311,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADgoVzzJ9lTdw4c8EdpoYR82-sHf2GR8ks5qsFe3gaJpZM4KBn7y
.

Yes, I would love a cheat sheet. @jhibbets - to your earlier question, were you thinking a widget? If not i can also get these into the speaker/schedule page

Sooo, Jason posted most of the twitter handles with the speakers' bios.
Here is a cheat sheet:
https://docs.google.com/spreadsheets/d/1ueZ-5HLOyjtQ4zefsO-KLYJ3rnckX-RtoV2Mkrw4gS8/edit?usp=sharing
On Tue, Sep 20, 2016 at 6:48 PM, lenaecb<EMAIL_ADDRESS>wrote:

Yes, I would love a cheat sheet. @jhibbets https://github.com/jhibbets

to your earlier question, were you thinking a widget? If not i can also
get these into the speaker/schedule page

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/CityCampNC/issues/303#issuecomment-248458921,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARrpxjPJnelRDo3srjTzEF4RK3FmkPZSks5qsGKqgaJpZM4KBn7y
.

Pro tip - ask for Twitter handles when you get  their other details, like
bio and headshot :)
On Tue, Sep 20, 2016 at 10:38 PM, suzanneccnc<EMAIL_ADDRESS>wrote:

Sooo, Jason posted most of the twitter handles with the speakers' bios.
Here is a cheat sheet:
https://docs.google.com/spreadsheets/d/1ueZ-5HLOyjtQ4zefsO-KLYJ3rnckX-
RtoV2Mkrw4gS8/edit?usp=sharing
On Tue, Sep 20, 2016 at 6:48 PM, lenaecb<EMAIL_ADDRESS>wrote:

Yes, I would love a cheat sheet. @jhibbets https://github.com/jhibbets

to your earlier question, were you thinking a widget? If not i can also
get these into the speaker/schedule page

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/codeforraleigh/CityCampNC/issues/303#issuecomment-
248458921>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ARrpxjPJnelRDo3srjTzEF4RK3FmkPZSks5qsGKqgaJpZM4KBn7y>
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/CityCampNC/issues/303#issuecomment-248495053,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADgoV3b7rstVNgGxr13l9WnE7sOGjlUfks5qsJiugaJpZM4KBn7y
.

Just to be sure I'm clear, I meant a list called 2016-speakers on Twitter.com via the @citycampNC handle. As in, adding our speakers to a list that need to be created
https://twitter.com/citycampnc/lists

https://twitter.com/citycampnc/lists/speakers-2016/members - ready to go. Use how you wish

Can you add @tourtech and @churchonmorgan or point me to how to do it
Chris Mathews
On Wed, Sep 21, 2016 8:22 PM, lenaecb<EMAIL_ADDRESS>wrote:
Closed #303.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@ChrisTheDBA - i have added both to the list as well


🎉 2.0.5

ℹ About this release

Version: 2.0.5
Type: patch
Last Release: 2.0.4 (4/28/2022, 10:59:58 AM) [?]
Commits to merge: 40 [?]

📦 Development Dependencies

Update @types/mocha from ^9.1.0 to ^9.1.1
Update @types/node from ^17.0.23 to ^17.0.31
Update @typescript-eslint/eslint-plugin from ^5.17.0 to ^5.22.0
Update @typescript-eslint/parser from ^5.17.0 to ^5.22.0
Update mocha from ^9.2.2 to ^10.0.0
Update typescript from ^4.6.3 to ^4.6.4

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

v2.0.5
GitHub release
Docker container (sebbo2002/iubh-campus-sync:2.0.5)
v2.0.5

Your semantic-release bot :package::rocket:


functionalities

Platform - Both
how can i remove Copy, Share , Define functionalities ?
for example : When i select text only appears colors highlight

i want to like that : https://ibb.co/DR5BLJW

Have you solved it? I want to customize  define functionalities right now


CB-5582 Differentiate environment related credential API

We need to separate (independent) credential API and environment related credential API because we need to do different authorization on them. API paths will not change.

We discussed with @lnardai  that separating credential authorization into credential based and environment based authorization can cause anomalies, so I close this for now.


Needed a program in any language that can directly generate the staircase sequence instead of passing all the numbers and checking it by a function.

can you limit upto which number should be generated otherwise its possible to generate the sequence upto infinite terms

Yeah I get your point.
So see.
It can be like the program asks for a value of "n".
Then the program generates the staircase numbers till nth position.
Like generate a staircase number, do n++, and when n == "user given input ", then break.

Or maybe if staging can be done.
Like in first page, the first 100 numbers.
Then in 2nd page the next 100 and so on....

@Bisso1998 I would like to take this one :blush:

can i work on this ?

@Vishwaak
Thanks a lot for stopping by the repo and taking your time to explore it.
Feel free to work on the feature and make a PR when it is done.
Would be waiting for your PR


Wrong .gitignore file

Folder "Sources/EPiServer.Reference.Commerce.Manager/App_GlobalResources/*" should be deleted as this folder contains important source files

Hi,
This folder contains the language resource files. We need them to display localized strings in Commerce Manager. Try to delete it - you'll see why we need it there.

We pushed a new change which removes that line from .gitinore.
Thanks.


send signal_quality via mavlink

Fixes #32

Seems ok in principle, although we may need to check how ArduSub handles it (especially in older versions) - IIRC we were initially reporting a confidence value but switched to a return for the no-confidence case because ArduSub was ignoring the confidence value and treating it as a valid reading, but it's quite possible I'm just misremembering / mixing this up with something else.

This will be required once we have https://github.com/ArduPilot/ardupilot/pull/24418 and https://github.com/ArduPilot/ardupilot/pull/23435
I'm not sure if we should check the ardusub version to enable the signal quality, though...

This will be required once we have https://github.com/ArduPilot/ardupilot/pull/24418 and https://github.com/ArduPilot/ardupilot/pull/23435

Yes, I think it's good to include, even just because it's part of the established MAVLink message specification. That said, it's a problem if doing so reduces performance for currently supported vehicle firmwares.
Speaking of, we'll also need to check/update this for the Ping Sonar integration in BlueOS.

I'm not sure if we should check the ardusub version to enable the signal quality, though...

Perhaps a more robust solution would be to add a toggle switch to the UI that determines whether or not to send MAVLink messages for zero (/low?) confidence distance measurements, with an info hover thingo that informs it should be turned off for firmwares that don't consider the confidence value (and an "e.g. ArduSub <= 4.x.y")?
That would be a bit more development work, but fixes the problem in a more general way, and avoids breaking compatibility with other firmwares that we don't have suitable feature support information for.

More generally, did anyone end up checking whether this will cause issues with old versions of ArduSub, or is the idea that it's resolved by not sending low confidence messages using the cutoff?

Hi, @ES-Alexander -- signal_quality was added to Rangefinder drivers in this fairly recent PR: https://github.com/ArduPilot/ardupilot/pull/25550
So no releases prior to Nov 2023 will be affected by setting signal_quality to something other than 0.
To make this 100% backward-compatible you could default the confidence cutoff to 0 so all messages get sent even if the confidence is very low. That way they are logged in tlog and BIN logs, they flow from the autopilot to the GCS so the pilot can see them, etc. But I can see the value in setting the confidence to something like 80 as well.
The RNG_HOLD PR also has a cutoff, currently hard-coded to 90. Perhaps this should be a parameter.

To make this 100% backward-compatible you could default the confidence cutoff to 0 so all messages get sent even if the confidence is very low. That way they are logged in tlog and BIN logs, they flow from the autopilot to the GCS so the pilot can see them, etc. But I can see the value in setting the confidence to something like 80 as well.

If I'm remembering correctly there were issues with using the Ping Sonar as a rangefinder when low/zero quality messages were being sent, so having a reasonable threshold in the code here should prevent a similar issue when using the DVL with older ArduSub versions.
That's the only issue I remember, so I think this is likely fine (and setting a non-zero default confidence cutoff is likely advisable) - I just thought it was probably worth checking whether there are any obvious issues to providing the value to firmwares that previously weren't receiving it, but if they're just completely ignoring it then it shouldn't have an effect.

I pushed this PR to my dockerhub for testing later today, and I'm seeing errors on my bench Pi running BlueOS 1.3.1:
2024-10-11 17:56:06.200 | DEBUG    | dvl:report_status:77 - waiting for cable-guy to come online...
2024-10-11 17:56:07.203 | WARNING  | blueoshelper:request:13 - Error in request: http://<IP_ADDRESS>/cable-guy/v1.0/ethernet: <urlopen error [Errno 111] Connection refused>
2024-10-11 17:56:07.204 | DEBUG    | dvl:report_status:77 - waiting for cable-guy to come online...
2024-10-11 17:56:08.207 | WARNING  | blueoshelper:request:13 - Error in request: http://<IP_ADDRESS>/cable-guy/v1.0/ethernet: <urlopen error [Errno 111] Connection refused>
...

Does this PR need a rebase?

@clydemcqueen rebased! I can`t test it right now, though

@Williangalvani Thanks! We have a test scheduled for the week of 20-Oct, so hopefully I'll finally get this done then. :-)


To create procedure like we create .hdbprocedure in sap HANA

Hi,
I was trying to create project using cds-dbm. I was able to create tables and view using CAP. However I also wanted to create procedures and function like we create .hdbprocedure and .hdbfunction in sap hana. Currently I am unable to find a way to create design time artifacts for procedures or functions and then to deploy it.
Is there a way to create and deploy this?

Hi @jyotiranjanrath-sap,
sorry for answering late.
By default PostgreSQL does not support design time files for procedures (or any other fragments).
I am in the process of developing and releasing version 2 of cds-dbm. This will introduce a manual changelog based approach, which makes is possible to manually add .sql files as part of the changelog and thus adds support for creating and deploying native DB fragments.
A release of version 2.0 will happen within the next weeks.


TypeScript 1.5 const enum changes break enum.toString()

I followed the recommendation by changing my .d.ts files to use const for enum definitions (these are generated view Web Essentials plugin from server-side classes.
Now I am able to compile but I get run time errors when I try to use toString on a number literal. Previously this was not a problem because the compiler put in a comment (which I liked btw) and a space. Here is some example code to reproduce the issue.
// FileId.d.ts
declare module server {
	const enum FieldId {
		ABSTRACT = 7000,
		RANK = 40002
	}
}

// Usage
var f = getById(server.FieldId.RANK.toString());

// Previous output
var f = getById(4002 /* RANK */.toString());

// TypeScript 1.5 output
var f = getById(4002.toString());

This is disappointing because TypeScript is supposed to catch errors like this at compile time. Should this be a compiler error in 1.5? What is the suggested solution?

The comment is back in master, but it is removed under --removeComments. We should be inserting the extra . automatically when needed.

I have the Keep comments in JavaScript output unchecked to remove comments. Enabling it seems to show the enum comment as it did in the previous version. It sounds like the the enum comment should be emitted regardless of the flag.
Thanks for the quick response.


HCL Parsing doesn't report azurerm_app_service_plan

I just tried the new infracost breakdown --path=. --terraform-parse-hcl. It is so much faster! 🎉
However, it didn't report my azurerm_app_service_plan resource, so it omitted $229.95 of costs. The rest of the output was identical though.
Here's the end of the output from regular infracost breakdown:
[ 31 lines skipped]
 module.XXX.azurerm_application_insights.this

 +- Data ingested                                                             Monthly cost depends on usage: $2.30 per GB

 module.XXX.azurerm_app_service_plan.service_plan

 +- Instance usage (P1v3)                                                                    730  hours
         $229.95

 OVERALL TOTAL
         $455.87
----------------------------------
23 cloud resources were detected, rerun with --show-skipped to see details:
· 5 were estimated, 4 include usage-based costs, see https://infracost.io/usage-file
· 11 weren't estimated, report them in https://github.com/infracost/infracost
· 7 were free

Here's the end of the output from infracost breakdown --terraform-parse-hcl (the beginning lines are the same):
[ 31 lines skipped ]
 module.XXX.azurerm_application_insights.this

 +- Data ingested                                                             Monthly cost depends on usage: $2.30 per GB

 OVERALL TOTAL
         $225.92
----------------------------------
23 cloud resources were detected, rerun with --show-skipped to see details:
· 5 were estimated, 4 include usage-based costs, see https://infracost.io/usage-file
· 11 weren't estimated, report them in https://github.com/infracost/infracost
· 7 were free

As you can see, the module.XXX.azurerm_app_service_plan.service_plan resource is entirely missing when using --terraform-parse-hcl.

@bgrainger Thanks for the report, this is exactly the kind of thing we're hoping the community can help us find!  Is there any chance you could send a sanitized tf project with the issue so we can reproduce it?

Here's a file that reproduces the problem:
terraform {
  required_providers {
    azurerm = {
      source  = "hashicorp/azurerm"
      version = "~> 2.98"
    }
  }

  required_version = ">= 1.1.0"
}

provider "azurerm" {
  features {}

  subscription_id = "[redacted]"
}

resource "azurerm_resource_group" "this" {
  name     = "Issue1433"
  location = "westus2"
}

resource "azurerm_app_service_plan" "this" {
  name                = "issue1433-plan"
  location            = resource.azurerm_resource_group.this.location
  resource_group_name = resource.azurerm_resource_group.this.name

  sku {
    tier = "PremiumV3"
    size = "P1v3"
    # capacity = 1
  }
}

Without capacity = 1 (an optional property, and I assume 1 is the default), --terraform-parse-hcl calculates a monthly cost of $0.00.

@bgrainger Thank you for the provided example! We're working on resolving this.

@bgrainger Both terraform plan and HCL parsing result in empty estimate if capacity is omitted. We updated the resource to have a default capacity 1 if the attribute is not set (#1435). It will go out with the next release. Until then setting capacity = 1 should be able to unblock you. We'll notify when it is live. Thank you for reporting the issue!

@bgrainger If that's okay, I'm going to close this issue for now. We'll notify when a new release is out, so you'll receive a notification.


[In-Process] Consider merging UseNativeIIS() and UseIISIntegration()

Currently, we specify that we are in-process by calling:
var host = new WebHostBuilder()
         .UseNativeIIS();

We should consider merging this call with UseIISIntegration(), where we can somehow specify we want to run in-process:
var host = new WebHostBuilder()
         .UseIISIntegartion(hostingModel: "inprocess"); // or an enum

or
var host = new WebHostBuilder()
         .UseIISIntegartion(); // Picked up by an environment variable or setting.

.UseIISIntegartion(hostingModel: "inprocess"); doesn't work, that can only be set in the web.config.

After further investigation, I definitely think we need to do this. The single switch for turning on inprocess vs out of process should be in web.config's hostingModel. IISIntegration will need to pick up that we are running in "inprocess".
By having the "UseNativeIIS()" call, if people call this and say they are using hostingModel="outofprocess", their app will fail to load because IISIntegration expects to be running in process while ANCM is configured to run out of process.
Do we just want to try to see if ANCM is loaded and if it fails, assume we are out of process? Specifically: https://github.com/aspnet/IISIntegration/blob/dev/src/Microsoft.AspNetCore.Server.IIS/IISHttpServer.cs#L130-L142


SP-1657 - Switch to docker compose V2 #minor

Codecov Report
Patch and project coverage have no change.

Comparison is base (3575835) 85.10% compared to head (0638def) 85.10%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #344   +/-   ##
=======================================
  Coverage   85.10%   85.10%
=======================================
  Files          35       35
  Lines        1296     1296
=======================================
  Hits         1103     1103
  Misses        131      131
  Partials       62       62

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


Change Config/CRD to support mulit-authproviders

What would you like to be added?
Ratify plans to add support for multiple auth providers the ORAS referrer store. Each auth provider will be selected via a regex/prefix matching scheme. A dictionary of auth providers will need to provided in the authProvider field instead. Even though functionality will not be added to support his until post v1.0, we should consider changing the config to accept a dictionary of providers now so there won't be a breaking change post v1.0.
Anything else you would like to add?
No response
Are you willing to submit PRs to contribute to this feature?

[X] Yes, I am willing to implement it.

use #135 for tracking actual implementation work post v1.0

Here are my thoughts so far:
To avoid breaking change post v1.0, we want to look into introducing/updating the existing authProvider field in the config to accept an array of auth provider config instead of a single config. The authProvider field is used in the ORAS store AND it's used in the verifier/store plugins for OCI plugin source support. Ideally we want to extend same funcitonality as ORAS store auth provider to OCI plugin auth provider.

Edit existing field in ORAS store and OCI plugin source authProvider --> authProviders
This involves editing all the configs for both targets which is feasible. However, there is an issue with CRD versioning for OCI Plugin source support. How would we update the existing CRD field? Would we need need new CRD version? If we use existing version, how does conversion API work?

Add a new field called authProviders that sits alongside authProvider
This would require side-by-side support for both fields. Requires updating our factory create methods of Auth Provider to take multiple configs. Do we need a new CRD version for this anyways?

Summarizing community meeting discussion from 8/16/23:

multi auth provider support must be backwards compatible with single auth provider configs in the Store and Verifier CRDs
add to v1.1 milestone along with full multi-auth provider backend support including (prefix/regex) matching

Brainstorm on implementation for CRD versioning support:

Update the unversioned (hub) API to have PluginSource accept a list of AuthProviders
Update the v1alpha1 and v1beta1 (spokes) APIs conversion functions for Store and Verifier Spec to unversioned to create an AuthProvider list with a single element.
release a new CRD version v1beta2 with auth providers list and bump controllers to use new API version for CRD spec.