Module recovery process is necessary

denoland modules can't be deleted but GitHub repositories can, so there must be a way to recover a module when its GitHub repo is deleted or not available (e.g. flagged by GitHub).
For example, 12 days ago, two of my repositories was mistakenly flagged by GitHub bots, and my conversations with support didn't work. so I lost two modules on deno.land and there is no way to recover them

Hey @erfanium, sorry this is happening to you, that sucks. Our recovery process is very much manual at the moment; The scale of the registry means we can comfortably accommodate such support requests. We will most likely look into an automated process when the current process no longer scales.
As for your current predicament, I would happy to help you out, feel free to reach out to me via email (available on my profile) or through Discord and we can work something out from there.

Handled offline.


Simple server

Coverage decreased (-11.1%) to 88.889% when pulling cdcd0821e1556283d9a723348d501da5ee3789d2 on simple_server into e34c17f2248d00db053546a0f8541359f5ee7a58 on master.


Adds clean_build_artifacts action

Adds a clean_build_artifacts action which deletes the files that get put in your repo as a result of running the ipa and sigh commands. It doesn't delete the fastlane/report.xml though, this is probably more suited for the .gitignore.
Useful if you quickly want to send out a test build by dropping down to the command line and typing fastlane beta, without leaving your repo in a messy state.

Hey Luka, neat idea, thanks! :+1:
Can you drop me a short email (on my profile), thanks!

Could you also add a short entry to the README and explain what the action does in one or two sentences?

Sure thing, was going to create another PR that updates the README.md depending on which PRs your merged ;)


Use @carousel-control-font-size for in min-width sm

Fix #16973
As 30px was hard coded for the following attribute values: width, height, and font-size, I have used the same pixel formula for each of these three as the @carousel-control-width is a percent value not a pixel value in variables.less
If margin-top should be calculated we can also do that with a (@carousel-control-font-size * -0.75)

If margin-top should be calculated we can also do that with a (@carousel-control-font-size * -0.75)

Yup, it should.

Took care of the margin changes in 1565c1196e788a7e75e6115bcfb9967430ef2648.


standard: add systemd unit drop-in directory on persist

Add a directory on the persist partition, say, skiff/systemd that allows us to specify .systemd unit files and other drop-ins.
We will need to decide if we want to do an overlay mount over /etc/systemd/system or if it would be better to make a user drop-in directory at /root/.local/share/systemd/user/ followed by a systemctl --user daemon-reload.

This is somewhat done with /etc/systemd/system in the overlay dir.


Install after local no TODO site

On second install I have install the Node js version as required but still getting multiple npm warnings and no TODO app on localhost:8080
node version: Your environment has been set up for using Node.js 6.3.1 (x64) and npm.
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture<EMAIL_ADDRESS>

Warnings are fine. Feel free to ignore them. As long as you finish without errors, you're good :)


docs: Iterate on --breaking docs

This is a follow up to #13979 to try to clarify things in prep for users testing this.

@bors r=weihanglo

:pushpin: Commit 6bd7623ea7f9c35d95103b85769e1ed7af137308 has been approved by weihanglo
It is now in the queue for this repository.

:hourglass: Testing commit 6bd7623ea7f9c35d95103b85769e1ed7af137308 with merge 30e5580d954b151c4e0f629d89a766ac14d1923d...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing 30e5580d954b151c4e0f629d89a766ac14d1923d to master...


Typo offline/online?

Regarding the section here...
Is my database offline while the scaling up/down operation is in progress?
No. A database remains offline during operations to a scale up or down.
This text doesn't seem to make sense. If it is offline then the Answer should begin "Yes" - not "No"
But I assume it is meant to say
No. A database remains online during operations to a scale up or down.

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

ID: 9cf979a7-c638-5cc2-08d2-3bc6fe0d178c
Version Independent ID: 905e3b9c-d8f4-0362-01f5-8b529e533d90
Content: Azure SQL Database Hyperscale FAQ - Azure SQL
Content Source: azure-sql/database/service-tier-hyperscale-frequently-asked-questions-faq.yml
Service: sql-database
Sub-service: service-overview
GitHub Login: @dimitri-furman
Microsoft Alias: dfurman

@asos-martinsmith
Thanks for your feedback! We will investigate and update as appropriate.

@asos-martinsmith thanks for catching this! The fix should be live later today.

@dimitri-furman
Thank you for your response.

@asos-martinsmith
Please verify if the document has been fixed.

We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.
#Please-close


feat: migrate layout and campaigns

@akshatnema @Shurtu-gal will open pr for navigation by tomorrow night

/rtm


Deploy Map Visualization stories into Pathfinders and Registry sections

Repo
After the integration of standalone Map Visualization into existing website, it will need to be used for story in pathfinders section.

[ ] create a story and text for Pathfinders story

[ ] Integrate map in Pathfinders Countries section to improve heavy text mixing it with images (technical idea like in this Washinghtonpost article)

[ ] create documentation on how to update stories

Hello @amreenp7 @nathanfletcher @lacabra
I asked comms team about integration map visualization inside What we do section
Quote from the team:
"Since the early discussions on the pathfinding map, we've lightened the reporting load for the pilots. So, it might be too much to ask ISG members and pathfinders for sufficient info to keep a stand alone map up to date. At this point, I think keeping the map linked from the pathfinding section of the What We Do page is a good stop gap. Happy to hear if others disagree here. "
Is it better to close this issue or rename it to Link the map from the What We Do page?

Great job @Rolikasi
I will close this issue now.


Line-Height in Notes field is too short for roll expressions

If we can make the roll expressions shorter, that's probably the best solution.  Otherwise we'll need to increase the line-height to fit them if they appear.

I've had a play and picked some hopefully reasonable values. The defaults seem to end up tiny, we were using a relative font size of 1.2rems and not adjusting the line height. They're now both specified absolutely in px.

That looks better. I think we can go with that.
On Mon, May 31, 2021 at 7:24 AM Steve Barnett @.***>
wrote:

I've had a play and picked some hopefully reasonable values. The defaults
seem to end up tiny, we were using a relative font size of 1.2rems and not
adjusting the line height. They're now both specified absolutely in px.
[image: image]
https://user-images.githubusercontent.com/371357/120199971-b74b4100-c21b-11eb-821b-627c03d06614.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/foundryvtt-dcc/dcc/issues/239#issuecomment-851489633,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAMEH4YZZ6O7Y5YFJ6JFETTQOEXHANCNFSM45LYMRQQ
.


fix: Update Documentation

Fix documentation to reflect fact that defaultHandlers should be a default import.
Resolves issue in https://github.com/LDflex/async-iteration-handlers/issues/137

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


How to configure Homebridge-ups with Synology

Hello,
my ups is already configured in Synology DSM 7.2. I try to configure Homebridge-ups but I'm not able to connect it.
This is the error message:
[6/25/2023, 7:49:04 PM] [UPS] DS1: ERR ACCESS-DENIED, API vERR ACCESS-DENIED
[6/25/2023, 7:49:04 PM] [UPS] DS1: warning: recommended version: API v1.2
I would be very pleased if I get help to connect them.
best regards

Did you follow the steps in the Wiki?

I guess so...
This is the log, when I restart the UPS-Childbridge:
[6/26/2023, 8:36:19 AM] Registering platform 'homebridge-ups.UPS'
[6/26/2023, 8:36:19 AM] [UPS] Loaded homebridge-ups v1.1.8 child bridge successfully
[6/26/2023, 8:36:19 AM] [UPS] homebridge-ups v1.1.8, node v16.16.0, homebridge v1.6.1, homebridge-lib v6.3.18
[6/26/2023, 8:36:19 AM] [UPS] warning: recommended version: node v18.16.1 LTS
[6/26/2023, 8:36:19 AM] Homebridge v1.6.1 (HAP v0.11.1) (UPS) is running on port 38547.
[6/26/2023, 8:36:19 AM] [UPS] hardware: Synology Synology NAS DS920+
[6/26/2023, 8:36:19 AM] [UPS] os: DSM 7.2-64570 Update 0
[6/26/2023, 8:36:36 AM] [UPS] DS1: warning: timeout after 15s
[6/26/2023, 8:36:36 AM] [UPS] DS1: ERR ACCESS-DENIED, API vERR ACCESS-DENIED
[6/26/2023, 8:36:36 AM] [UPS] DS1: warning: recommended version: API v1.2

So what’s the output of the commands under Verify?

sh-4.4# upsc -l
Init SSL without certificate database
ups
sh-4.4# upsc ups
Init SSL without certificate database
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 50
battery.date: 2001/09/25
battery.mfr.date: 2019/11/10
battery.runtime: 5760
battery.runtime.low: 120
battery.type: PbAc
battery.voltage: 27.1
battery.voltage.nominal: 24.0
device.mfr: American Power Conversion
device.model: Back-UPS RS 900G
device.serial: 4B1945P23564
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 5
driver.parameter.port: auto
driver.parameter.synchronous: no
driver.version: DSM7-2-60108-221130
driver.version.data: APC HID 0.96
driver.version.internal: 0.41
input.sensitivity: medium
input.transfer.high: 294
input.transfer.low: 176
input.voltage: 237.0
input.voltage.nominal: 230
ups.beeper.status: disabled
ups.delay.shutdown: 20
ups.firmware: 879.L4 .I
ups.firmware.aux: L4
ups.load: 12
ups.mfr: American Power Conversion
ups.mfr.date: 2019/11/10
ups.model: Back-UPS RS 900G
ups.productid: 0002
ups.realpower.nominal: 540
ups.serial: 4B1945P23564
ups.status: OL
ups.test.result: No test initiated
ups.timer.reboot: 0
ups.timer.shutdown: -1
ups.vendorid: 051d

Could, but unlikely.
What the output of ups info?  Are you running Homebridge on the Synology as a package or through Docker?   Are you connecting to NUT using localhost / <IP_ADDRESS> or through a hostname / IP address?  Did you enable the network service and whitelist the IP address used by Homebridge?

the output of "ups info" is:
-sh: ups: command not found
I'm running Homebridge from the synology package.
changing the host in the configuration from my local ds-ip adress to "localhost" worked.

ups -info (on hb-console):
homebridge@ds1:/etc/ups $ ups info
{
"version": "Network UPS Tools upsd DSM7-2-60108-221130 - http://www.networkupstools.org/",
"apiVersion": "1.2",
"devices": {
"ups": {
"description": "Unavailable",
"nCients": "2",
"clients": [
"<IP_ADDRESS>",
"<IP_ADDRESS>"
],
"commands": [
"beeper.disable",
"beeper.enable",
"beeper.mute",
"beeper.off",
"beeper.on",
"load.off",
"load.off.delay",
"shutdown.reboot",
"shutdown.stop",
"test.battery.start.deep",
"test.battery.start.quick",
"test.battery.stop",
"test.panel.start",
"test.panel.stop"
],
"constants": {
"battery.charge": "100",
"battery.charge.low": "10",
"battery.charge.warning": "50",
"battery.date": "2001/09/25",
"battery.mfr.date": "2019/11/10",
"battery.runtime": "5760",
"battery.runtime.low": "120",
"battery.type": "PbAc",
"battery.voltage": "27.1",
"battery.voltage.nominal": "24.0",
"device.mfr": "American Power Conversion",
"device.model": "Back-UPS RS 900G",
"device.serial": "4B1945P23564",
"device.type": "ups",
"driver.name": "usbhid-ups",
"driver.parameter.pollfreq": "30",
"driver.parameter.pollinterval": "5",
"driver.parameter.port": "auto",
"driver.parameter.synchronous": "no",
"driver.version": "DSM7-2-60108-221130",
"driver.version.data": "APC HID 0.96",
"driver.version.internal": "0.41",
"input.sensitivity": "medium",
"input.transfer.high": "294",
"input.transfer.low": "176",
"input.voltage": "237.0",
"input.voltage.nominal": "230",
"ups.beeper.status": "disabled",
"ups.delay.shutdown": "20",
"ups.firmware": "879.L4 .I",
"ups.firmware.aux": "L4",
"ups.load": "12",
"ups.mfr": "American Power Conversion",
"ups.mfr.date": "2019/11/10",
"ups.model": "Back-UPS RS 900G",
"ups.productid": "0002",
"ups.realpower.nominal": "540",
"ups.serial": "4B1945P23564",
"ups.status": "OL",
"ups.test.result": "No test initiated",
"ups.timer.reboot": "0",
"ups.timer.shutdown": "-1",
"ups.vendorid": "051d"
},
"variables": {
"battery.charge.low": "10",
"battery.runtime.low": "120",
"input.sensitivity": "medium",
"input.transfer.high": "294",
"input.transfer.low": "176",
"ups.delay.shutdown": "20"
}
}
}
}

changing the host in the configuration from my local ds-ip adress to "localhost" worked.

I think, if you use the external IP address, instead of localhost or <IP_ADDRESS>, NUT will treat it as a network connection, requiring a whitelist entry.


[FEATURE] Display pictures in search comparison tool

Is your feature request related to a problem?
Current comparison tool only display text document, which is not very intuitive comparing search results. We propose to display pictures when a url is available.
What solution would you like?
See attachment for a mock up

What alternatives have you considered?
We could use greasemonkey script on client side to do the job, but it's not as easy.
Do you have any additional context?
Add any other context or screenshots about the feature request here.

Hi @sean-zheng-amazon, do you have a link to the GreaseMonkey script that you are referring to?

Had some more questions needed for clarification:

How does the tool know when to display an image? Will the field name always be image if there is an image to display?
If not, will the tool need to parse through every link to determine whether or not it is an image?

Had some more questions needed for clarification:

How does the tool know when to display an image? Will the field name always be image if there is an image to display?
If not, will the tool need to parse through every link to determine whether or not it is an image?

Looks like these decisions should be included in a low level design. It's fine to make implicit assumptions when prototyping. But, for the feature issue, can you elaborate on alternatives and trade-offs? Thanks.

closing this as complete; images will be moved to the main plugin in #286


how to download the pretrained weights  to local

Thans for your contribution! But how to download the pretrained weights to local ,would you pls offer me a url, thanks!

The model is hosted on huggingface.co
You can access the model's files using this url https://huggingface.co/asafaya/bert-base-arabic#list-files


Refactor HTPrimaryButton

Currently, HTPrimary uses the screen as a context. This isn't scalable when screen can take polymorphic forms.
Refactor to use intent(?)

Should intent be a new enum of simple String?

Implementation converted:
HTPrimaryButton(Screen, Bool, PrimaryStyle, Binding<Bool>?) to HTButton(ButtonContext, Bool, ButtonSize, Binding<Bool>?)

HTPrimaryButton -> HTButton because it's no longer a Primary
Screen -> ButtonContext because there are multiple HTButtons on a Screen. That context doesn't make sense anymore.

Opted out of String so we could aggregate all of our Button labels in one place  (ButtonContext) rather than scattered throughout the code.

PrimaryStyle -> ButtonSize because this isn't a style, it's just a size


Conditional housing data display

One solution to #655
This way of doing it is fairly verbose, but I think it's also mostly transparent about what is happening and easy to change later. I can think of less repetitive ways of doing this, but there is already a lot of magic happening with these model tables. Trying to be explicit, here!

This looks good in principle, but there are a few style changes that I'd like to see slash loose ends to clean up.

I think I'd prefer to see a private _display_housing_data method on the model table rather than a public method on the model.
This would be a good spot to use the python ternary operator - i.e. return obj.other_needs if obj.needs_housing() else ''
The related_objects_list() wrapper exists as a thin wrapper around a manager - it's just shorthand for a method calling obj.related.all() so that it takes one line instead of two. Calling it from a defined method defeats the little benefit it added and adds a layer of distance that could end up being confusing later. And really the layer of distance it already adds is not great. Probably best to just get rid of it.
We should handle the reverse case while we're at it – i.e. if someone had said they'd host but changed their mind.

I can go ahead and make these changes -- they are good! Though do you think that Attendee.needs_housing is unnecessary? To me it's reasonable that an Attendee knows whether it needs housing and the model table doesn't need to know exactly how that's implemented. _display_housing_data would call attendee.needs_housing.

I'm pretty ambivalent about Attendee.needs_housing()... I'm fine with it staying in.

(Also, if you do have needs_housing() the _display_housing_data is of course unnecessary.)

I guess my general philosophy is that the cost of adding methods to models is pretty low. Would you directly compare against Attendee.NEED (or even the string 'need') in the model table?

Adding methods is in principal low-cost, but it can easily make the code less clear (slash explicit) by adding levels of indirection. For a simple shortcut like this, it also means there's more than one obvious way to do things. These both mean that people coming on to the project in the future will have a tiny bit higher of a learning curve – and the code will be less immediately understandable to us as well, if we leave it alone for a while. And the benefit doesn't seem to be that great – it doesn't make a common pattern more compact, it just makes a one-line comparison a bit shorter.
That being said, needs_housing() is a very semantic method name, and Attendee doesn't have a lot of methods for it to get lost among, so I think it would probably be fine. It might even be a bit more understandable than attendee.housing_status == Attendee.NEED...
Hence: ambivalent in this case.

@chigby is this ready for review again?

@melinath Okay, this should be good to review again.

@chigby failing tests on postgres

Is there a good way to run the tests locally on postgres?

If you set up a postgres server and then just update the DATABASE dict locally to point there instead of sqlite, it should work fine.

Slash... setting DB=postgres in the env should trigger the test settings already included in settings.py

@melinath: Ok, now it's working (curse my hard-coded primary key references).

hard-coded pk references always get you in the end! :-) That was like 90% of the issues I had switching MR tests over to mysql.

Hm, it looks like this doesn't actually handle the hosting side of things - but that works out fine for now because the forms already (currently) delete the hosting information when you uncheck the box. (And I don't expect that to really change in the future.)

No? There's a couple of tests for displaying the hosting information on the order table. Am I testing the wrong thing?

This doesn't display things if the box is unchecked, yes, but as far as I can tell that's because the data is deleted, not because it isn't displayed. I can't test manually because there's no way to end up in that state.

This is why line 647 of model_tables.py doesn't need to look like line 375. (This refers specifically to custom data fields. The date-related fields are handled.
Again though, this isn't a place where anything needs to change, just an interesting fact.

Okay, I think this addresses all of @melinath's comments now.

I found an edge case that still isn't handled, but it's really more an issue with the system as a whole rather than an issue with this PR. See #718 for more details.


first change to check for vintage cluster

Checklist

[ ] Update changelog in CHANGELOG.md.

Same comment applies here as on the other PR - it's a bit over-cautious, but since the false positive case silently disables a security feature, I'd err on the side of requiring the provider to explicitly match and exposing errors if it hits an unknown provider.
This logic can go away completely once all clusters move, so the likelihood we add a new provider before then is pretty slim. If it happens, we can update the list or invert the logic if we need to keep the toggle for a while after all clusters have moved.

This PR does not add any new behavior for now, except logging messages for non-legacy providers. LMK when it's ready for re-review.

Same question, isn't the change in behaviour that it now will also do the thing on non-vintage clusters? And the extra version checks for vintage-clusters is now behind a: if-vintage check?
And isn't that what we wanted?


Warm Reset can lead to undefined state

(Starting in RTL repo, but outcome could lead to transfer to SW repo)
Warm reset cannot be pre-conditioned by Caliptra SW. Warm Reset does not clear RAMs, reset Key Vault, or reset Data Vault. Caliptra spec does not bound when a Warm Reset can occur. Therefore a Warm Reset could leave Caliptra in an undefined state.
@bharatpillilli @vsonims @jhand2 @bluegate010 @korran

Transferred to SW repo and assigned to @jhand2 who has action items

determining whether runtime can continue to behave on surprise warm reset (use a debug key instead)
@bluegate010 what journeys to be kept

Ack. Thanks Varun.

@FerralCoder the FMC spec needs updating to handle Warm Reset as well. My expectation is:

FMC checks whether the reset type is warm_reset.
** If yes, FMC checks whether CDIFMC and PrivateKeyFMC are locked.
*** If yes, proceed to RT boot.
*** If no, fatal error.

@FerralCoder the FMC spec needs updating to handle Warm Reset as well. My expectation is:

FMC checks whether the reset type is warm_reset.
** If yes, FMC checks whether CDIFMC and PrivateKeyFMC are locked.
*** If yes, proceed to RT boot.
*** If no, fatal error.

Hi @varuns-nvidia
I thought we said we will clear the key vault and continue the boot so that we don't stop the platform from booting @bluegate010  also to keep me honest.

@bharatpillilli , yes for RT. Should we do the same for FMC? I suppose we can still support measurement storage.

Added details about this in https://github.com/chipsalliance/caliptra-sw/pull/330
If we detect possible corruption, we'll call DISABLE_ATTESTATION. All commands will still work, but the key will not be endorsed by any trusted CA (since the CDI's are cleared from KeyVault).

is more work still needed here or can this be closed?


Remove northamerica-northeast1 from Vertex AI regions

... because it does not support long context (> 32K). https://cloud.google.com/vertex-ai/generative-ai/docs/learn/locations#canada_1

Addresses:

https://github.com/google/oss-fuzz-gen/pull/717#issuecomment-2480019241
https://github.com/google/oss-fuzz-gen/pull/718#issuecomment-2484720901

/gcbrun skip


Non-zero values returned wit non-zero errors

Fixed #1972.

The tests are not passing, this is because the example.go file must also be updated to return a nil or empty slice in case of an error. Alternatively, we can also change the test to not care about the slice returned when an error is returned.

Sorry, I deleted the file by mistake, I'll restore it as soon as I can.


Suggestion: set to migrate/down default value for limit is 1 (now revert all migrations)

Alternatively, we can require specifying a number and introduce --all option.


update responsibleai to interpret-community 0.30.0

Description
update responsibleai to interpret-community 0.30.0
Checklist

[ ] I have added screenshots above for all UI changes.
[ ] I have added e2e tests for all UI changes.
[ ] Documentation was updated if it was needed.

Codecov Report

Merging #2275 (c322d94) into main (a714c25) will increase coverage by 3.48%.
Report is 1 commits behind head on main.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #2275      +/-   ##
==========================================
+ Coverage   89.07%   92.55%   +3.48%
==========================================
  Files         129       55      -74
  Lines        7387     2137    -5250
==========================================
- Hits         6580     1978    -4602
+ Misses        807      159     -648

Flag
Coverage Δ

unittests
92.55% <ø> (+3.48%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 74 files with indirect coverage changes


Can we have working launch.json out of the box for .Net?

Can we have a working launch.json generator out of the box for .Net?
Similar to the JetBrains products that have working out of the box env configs.
Thank you for your consideration and have a nice day :)

/extC#


[Type checker] Use DependentMemberType instead of type variables for nested types.

In the constraint solver, we've traditionally modeled nested type via
a "type member" constraint of the form
$T1 = $T0.NameOfTypeMember

and treated $T1 as a type variable. While the solver did generally try
to avoid attempting bindings for $T1 (it would wait until $T0 was
bound, which solves the constraint), on occasion we would get weird
behavior because the solver did try to bind the type
variable.
With this commit, model nested types via DependentMemberType, the same
way we handle (e.g.) the nested type of a generic type parameter. This
solution maintains more information (e.g., we know specifically which
associated type we're referring to), fits in better with the type
system (we know how to deal with dependent members throughout the type
checker, AST, and so on), and is easier to reason able.
This change is a performance optimization for the type checker for a
few reasons. First, it reduces the number of type variables we need to
deal with significantly (we create half as many type variables while
type checking the standard library), and the solver scales poorly with
the number of type variables because it visits all of the
as-yet-unbound type variables at each solving step. Second, it
eliminates a number of redundant by-name lookups in cases where we
already know which associated type we want.
Overall, this change provides a 25% speedup when type-checking the
standard library.

@swift-ci please smoke test and merge

Darn.
Fndation/NSScanner.swift:605:49: error: 'Int1' is not convertible to 'Bool'
let options: NSString.CompareOptions = [caseSensitive ? [] : NSString.CompareOptions.caseInsensitive, NSString.CompareOptions.anchored]
^~~~~~~~~~~~~

Reduced bug:
struct X : OptionSet {
  let rawValue: Int

  static let option: X = X(rawValue: 1)
}

func test(b: Bool) {
  let x: X = [ b ? [] : X.option, X.option]
}

Overall, this change provides a 25% speedup when type-checking the
standard library.

Bugs aside, this is awesome!

@swift-ci please smoke test and merge

... fixed a latent bug in gatherAllSubstitutions() that this somehow triggered.

@swift-ci please smoke test and merge

@swift-ci please smoke test and merge

@swift-CI please smoke test Linux

@swift-CI please smoke test Linux

@DougGregor Thank you! Excellent stuff! :-)


Feat: sha1 with rsa encryption

Implements sha1WithRSAEncryption in #38

Temporarily, uncomment sha1 test leaf for tests to pass, as they make the app registration fail for now
Will fix in next contract deployment


PlayerKits2 Folia

Let me know what you think of this PR.

If you have any questions or anything let me know.

I did update the description, so if you want to change it is okay.


Possible Race Condition in "Next Assessment"

Describe the bug
We've recently run into the bug that two teaching assistants had to assess the same solution which lead to issues regarding the grading. After talking to @krusche the idea is that this behavior might be caused by a not handled race condition in the "Assess next solution" functionality. As you can see in the picture, you can see less dates than assessments.
As this state could only be resolved by manually editing the Database, I've marked this bug as "priority:high".
EDIT: @krusche gave me the information that the lock mechanism for complaints has been reworked in the recent past; maybe this mechanism can be used for the assess next solution feature as well
To Reproduce

As this might be caused by a race condition, it's quite hard to reproduce.
Expected behavior

A Submission shall be assessed by only one teaching assistant
Screenshots

Environment
Artemis 4.12.1 (Gitlab/Jenkins)

@joschahenningsen do you have any idea about the details of the race condition :) ?

Thanks for pinging me, I kind of forgot about this. :smile:
I'll work on it and keep you updated. Is this happening regularly?

Actually, that occurs from time to time (luckily not that often) and as it's possible to delete the results for a submission, the race condition is currently not that critical :)

@dfuchss was the issue fixed in the mean time?

@krusche I think it might be fixed (I didn't encountered the behavior in the last corrections). If it occurs again, I'll reopen the issue.


Added Slovak language support #12

Coverage remained the same at 100.0% when pulling c38d213dc066ccd4cdde093f27b3f8be583eb074 on Blarne:feature/slovak-support into 1bff95ec79cf1ba85ef5bad7e0f5a259ba9fd473 on allegro:master.

Coverage remained the same at 100.0% when pulling 2fcf70f53e3bc1718c05f07e3ea341e730bbe0cb on Blarne:feature/slovak-support into 1bff95ec79cf1ba85ef5bad7e0f5a259ba9fd473 on allegro:master.

Coverage remained the same at 100.0% when pulling 24eba3b610308aaeac6a6b98768d992651b1ffd7 on Blarne:feature/slovak-support into 1bff95ec79cf1ba85ef5bad7e0f5a259ba9fd473 on allegro:master.

Some progress in merge request accept?

I created pull request with tests for Slovak languages. Could you take a look at it and review it?


Add autocapitalize attribute to  maintained concerns

It creates a more direct way to overwrite autocapitalize and deals with at the concerns level rather than in extraAttributes for greater clarity. The side effect of this should be on mobile devices that the keyboard is always in caps mode.

Thanks!


Add olm-managed label to configmap-based catalogsource for e2e test

Currently, OLM only caches configmap with olm-managed label to reduce
memory usage footprint. There is an automatic mechanism to inject
this label to all configmaps that belong to catalogsource. However,
for e2e test, this label should be added by default to avoid extra
logic to be executed.
Signed-off-by: Vu Dinh<EMAIL_ADDRESS>
Description of the change:
Motivation for the change:
Reviewer Checklist

[ ] Implementation matches the proposed design, or proposal is updated to match implementation
[ ] Sufficient unit test coverage
[ ] Sufficient end-to-end test coverage
[ ] Docs updated or added to /doc
[ ] Commit messages sensible and descriptive

/approve

/lgtm


[question] Reset() in VecEnv

Hi,
while running my simulations using PPO2 in a VecEnv I noticed a weird behaviour. By design, when the done is set to True in the episode, the reset() method is automatically called and an observation is return.
    def step_wait(self):
        for env_idx in range(self.num_envs):
            obs, self.buf_rews[env_idx], self.buf_dones[env_idx], self.buf_infos[env_idx] =\
                self.envs[env_idx].step(self.actions[env_idx])
            if self.buf_dones[env_idx]:
                obs = self.envs[env_idx].reset()
            self._save_obs(env_idx, obs)
        return (np.copy(self._obs_from_buf()), np.copy(self.buf_rews), np.copy(self.buf_dones),
                self.buf_infos.copy())

I am wondering if this makes sense. In my scenario, a robot crashes into an obstacle and, due to the reset() method, the observation returned is not the crash but the one obtained immediately after resetting the position. In this way, the robot shouldn't learn to avoid obstacles because it's not learning to associate a bad reward to the obstacles but to a random position in the environment.
Please correct me if I am wrong.

Hello,

Please correct me if I am wrong.

I think the current implementation is correct. As a reminder, we are in the Markov Decision Process (MDP) framework.
So, given an observation o_t at time t, the agent takes an action a_t. From those two, a reward r_t and termination done_t are computed.
If the episode is not over (done_t = False), the agent receives a new observation o_{t+1}, otherwise a new episode begin, and therefore the agent receives the first observation of the next episode (obs = env.reset())
Without VecEnv, the workflow looks like this:
obs  = env.reset()
# Forever
while True:
    # Choose an action given the observation, here a random agent
    action = env.action_space.sample()
    # One step in the env
    obs, reward, done, _ = env.step(obs)
    # If the episode is over, start a new one
   # note that the obs variable is replaced here
    if done:
       obs = env.reset()

In this way, the robot shouldn't learn to avoid obstacles because it's not learning to associate a bad reward to the obstacles but to a random position in the environment.

In your case, what causes the crash is taking a given action in a certain situation, so it is not random. Giving the observation of the crash would not add more information, as it is already contained in both the terminal signal (done) and the reward (I suppose you maybe give a negative reward for crashing).

Giving the observation of the crash would not add more information, as it is already contained in both the terminal signal (done) and the reward (I suppose you maybe give a negative reward for crashing).

Ok, I guess this makes sense. Thank you for clarify this point!


Allow tinder like left and right swiping.

Hi Crowdlinker Team,
Thank you for the library, I've just tried it out and it felt really responsive. I was looking at a specific use case where the pager can register right-swiping to allow for the current card to be swiped right, rather than bringing the previous screen back. I was going through the props but I couldn't find anything that I could use.
Let me know if you need any other details regarding the usecase.

hi there - thanks so much. i too have thought of this use case but haven't come up with a solution just yet. my initial thoughts would be that you would have to pop the top child after swiping it away so that it couldn't come back. i will think about this a little bit, if you come up with a solution it would be awesome if you could share! thanks

following up on this -- i've tried a couple different approaches with no luck. i dont think this library is the right tool for the job, but i have a good idea of how this kind of thing could be done. let me know if you want some guidance on building something to achieve this kind of component. cheers

So I've been looking at some apps who do the pagination along these lines, and essentially the idea is not to pop the top screen off but rather allowing for going to the previous screen with a tap. Here is a video that explains this.

But I understand how this could be difficult, and I would love to understand how should I go about building this. Especially when the next clamp is 0, kinda like the stacked cards example. I am also a fan of the transformation config for cards, its genius :)


README:  add temporary status disclaimer

To be removed when the documentation is rendered accurate.

closing stale pr

What is stale?  Does closing this indicate that the current state of the documentation is accurate?


[Sandbox] Gimbal

Application contact emails
<EMAIL_ADDRESS><EMAIL_ADDRESS>Project Summary
Gimbal is a developer tool which helps developers deploy and manage AI pipelines of model variants across a fleet of heterogeneous edge devices.
Project Description
By providing an abstraction layer for compatibility with diverse sensors, hardware, and underlying AI frameworks, Gimbal helps developers deploy and manage AI pipelines of model variants across a fleet of heterogeneous edge devices.
The edge refers to a computing paradigm that brings data processing closer to the source of data generation. This encompasses a wide array of devices and environments, from embedded systems in IoT devices to on-site servers in industrial settings. By processing data locally or at nearby edge nodes, rather than relying solely on centralized data centers, it enables faster, more efficient computing, especially in scenarios with limited connectivity or stringent real-time processing requirements.
However, existing AI model development and deployment solutions are not designed to handle problems unique to the edge:

Developers may be deploying to a fleet of heterogeneous devices, but models must be optimized for specific hardware and frameworks.
Per device sensor and environmental differences may require heterogeneous models to achieve the best performance, however, deploying multiple variants of the model to your fleet of devices can be challenging.
Models must be able to run in resource constrained environments, requiring low memory and CPU footprint

To tackle these problems, Gimbal offers a comprehensive suite of tools designed to streamline the deployment and manage the life-cycle of AI models across a diverse fleet of edge devices.
Org repo URL (provide if all repos under the org are in scope of the application)
https://github.com/gimbal-ai
Project repo URL in scope of application
https://github.com/gimbal-ai/gimbal
Additional repos in scope of the application
No response
Website URL
No response
Roadmap
https://github.com/gimbal-ai/gimbal/blob/main/ROADMAP.md
Roadmap context
No response
Contributing Guide
https://github.com/gimbal-ai/gimbal/blob/main/CONTRIBUTING.md
Code of Conduct (CoC)
https://github.com/gimbal-ai/gimbal/blob/main/CODE_OF_CONDUCT.md
Adopters
No response
Contributing or Sponsoring Org
https://gimletlabs.ai/
Maintainers file
https://github.com/gimbal-ai/gimbal/blob/main/MAINTAINERS_oss
IP Policy

[X] If the project is accepted, I agree the project will follow the CNCF IP Policy

Trademark and accounts

[X] If the project is accepted, I agree to donate all project trademarks and accounts to the CNCF

Why CNCF?
Our goal with Gimbal is to provide a vendor agnostic way for deploying AI pipelines across a fleet of devices. Hardware has been a historically fragmented space, characterized by varying architectures (e.g., x86, ARM) and GPUs (e.g., Intel, NVIDIA, AMD). These disparities create challenges in standardizing deployments across platforms due to differences in instruction sets, performance optimizations, and compatibility requirements. Building a deployment standard requires close collaboration amongst the stakeholders in the domain. We believe that the CNCF can provide diverse and neutral grounds for healthy collaboration and governance for the project. We also believe that CNCF can help provide visibility to the project and help establish it as an industry standard.
Benefit to the Landscape
Gimbal provides infrastructure for deploying AI models and pipelines to the edge, encompassing environments such as IoT devices to local servers and edge data centers. Bringing data processing closer to the source provides benefits such as more efficient compute, real-time processing, and ability to operate in limited connectivity environments. We are seeing a growing number of developers deploying their workflows to the edge to leverage these advantages.
There exists other projects in the CNCF landscape to deploy general applications and workflows to edge devices (K3s, KubeEdge). KubeFlow also helps deploy ML workflows to Kubernetes environments, but has a large focus on training/data science pipelines, rather than inference. There are currently no projects which focus uniquely on deploying AI workloads to edge environments. The nature of edge environments necessitates a targeted solution which cannot be solved by generalized approaches:

Heterogenous edge devices, such as hardware or peripheral differences, can require differently optimized models
Environmental differences of edge devices, such as lighting, necessitate specialized models for specific environments
Resource constraints of edge devices require models with low memory/CPU footprints

These differences cannot be fully captured in generalized model deployment solutions, and can be unwieldy to deploy without proper infrastructure.
Cloud Native 'Fit'
As with other edge-focused projects such as K3s and KubeEdge, we believe that the “Cloud Native” experience extends beyond the cloud. We believe that people should be able to develop and deploy applications to edge environments with the same ease, including those involving AI/ML. The edge/hardware domain has historically been a fragmented space. Gimbal aims to provide an open standard to bridge that gap.
Gimbal’s governance is designed to ensure that the project remains open and transparent, without favoring any specific partisan interests. Relatedly, Gimbal aims to be platform agnostic by allowing developers to manage and optimize their AI models across heterogenous edge devices. The project is also built to be scalable, so that users can deploy Gimbal in enterprise environments where there may be thousands of edge devices.
Cloud Native 'Integration'

OpenTelemetry is utilized for all telemetry data that Gimbal collects and fits well into the border observability framework.
Prometheus: Metrics can also be exported to Prometheus.
NATS is used on the control plane as a messaging backend.
GRPC is used as the primary communication scheme.
Helm is used as a way to deploy Gimbal to a Kubernetes cluster.

We expect Gimbal to be deployed on KubeEdge and K3s clusters.
Cloud Native Overlap
KubeFlow and KServe are existing machine learning deployment systems for machine learning models on K8s. Gimbal is distinct from these due to the focus on edge devices and life-cycle management of models that run on edge devices.
Similar projects
While there isn’t an existing system that provides Gimbal’s capabilities there are projects adjacent to Gimbal.

OpenVino: Toolkit for optimizing and deploying models on Intel platforms.
Tensorflow:  Platform for developing and training deep learning models.
Eve: Eve abstracts away the complexity of managing an edge environment. It’s part of the Linux Foundation. Gimbal is a layer that sits on top and can leverage Eve.
Tensorflow Serving: Provides infrastructure to deploy tensorflow models behind a GRPC API.

Landscape
No, we are not in the CNCF landscape yet.
Business Product or Service to Project separation
Gimlet Labs is a sponsoring company of Gimbal and uses Gimbal as its mechanism for deploying AI models and pipelines on customer devices. Gimlet Labs’s product builds on top of Gimbal to provide additional functionality beyond deployment, such as model generation and retraining. Any changes requiring updates to Gimbal components (agent, CLI, API) will be contributed directly to the open source project. Any enhancements beyond AI model/pipeline deployment will not be contributed to Gimbal.
Project presentations
No response
Project champions
No response
Additional information
No response

Hi all, we're going to close this out as we're thinking through some high-level direction changes for the project.
We'll resubmit when that's all finalized and we're ready again!


The @aware tag doesn't get default property values from parent components

Laravel Version: v8.83.1
PHP Version: 8.1.1
Database Driver & Version: MariaDB 10.6.5

Description:
It appears the new @aware tag cannot access default property values from parents. It can only get properties that were explicitly given. If a parent component has a property that was left as the default, the corresponding property in the @aware tag of a child component will be null.
You will need to repeat the value as a default value in the @aware tag in the child component. This is not ideal. Ideally the @aware tag would get the default value of whatever parent component it is in, so the same child component can be reused for different parent components.
Steps To Reproduce:

Create the following two anonymous components.

@props(['name' => 'Mother'])

    {{ $slot }}

@aware(['name'])

{{ "$name has a $slot" }}

Add the following tags, and observe that the one without an explicitly defined name property does not render as you would expect.

{{-- Works fine --}}
<x-parent name="Father">
    <x-child>daughter</x-child>
    <x-child>son</x-child>
</x-parent>

{{-- Does not work. The default value "Mother" is not passed on to the child component. --}}
<x-parent>
    <x-child>daughter</x-child>
    <x-child>son</x-child>
</x-parent>

This, unfortunately, isn't possible. It's a limitation of @aware that we can't overcome. The values in @aware need to be the same as in the parent component.
I've sent in a PR to clarify this: https://github.com/laravel/docs/pull/7721


Reverse not working since update

It appears that the 'reverse': true feature has stopped functioning since the 1.6.1 update... unless there is another required attribute on the individual path that I am unaware of. My LLP animation can be seen here - Codepen!.
Any help would be much appreciated.

I have it set on:
var dci1B - path #2,
var dci1D - path #2,
var dci1F - path #2,
var dci1H - path #2,
var dci1J - path #2
among others...

Hi SkyPages, thanks for bringing to to my attention.
I've have a look into this today or tomorrow.
I'm currently clearing the backlog of tickets, some of which include some exciting feature requests.

Thank you Cam - I think I can speak for everyone in expressing that we really appreciate this plugin and all your hard work to continue to improve it. I have a question about combining Paint with Set but will open it as a separate comment/ticket/issue.
An alternative fix /  work around (for any LLP users that may experience the same issue) - you can do the following by opening your SVG inside Illustrator (I'm using CC 2015 - so not sure on version requirements):

Select the path with the Selection Tool (black arrow, V) || or if said path is already complexly grouped with several other paths use the Direct Selection Tool (grey arrow) and then press Cmnd-8 (mac) or Ctrl-8 (PC). Congratulations you just converted your path into a compound path, which can still be animated with LLP and which is the only kind of path that Illustrator lets you easily "reverse".

Now open the attributes window (menu->window->attributes) and use the "Reverse path direction" buttons (they are only available for compound paths).

Note: If you cannot see these buttons it is because the Attributes window is "minimized", so it is not showing all the attributes. Click on the top right corner and select "Show all".

You will no longer need to reverse the path within LLP.


Basic Functions Exercise

https://docs.base.org/base-camp/docs/contracts-and-basic-functions/basic-functions-exercise

Submitted to Base Goerli: https://goerli.basescan.org/address/0x322afec27673f531567ccb953e6e53b5562dc78f#code


Overcome hyprland wrapper

Discussed in https://github.com/hyprwm/Hyprland/discussions/1690

Originally posted by SimoriccITA March  3, 2023
use a wrapper to set the necessary env variables and exec Hyprland is more inconvenient that have the possibility to simply write Hyprland in your terminal or use the default /usr/share/wayland-sessions/ file (that launch the command exec Hyprland)  and have Hyprland itself that execute a script
i propose an hyprlandrc in the same folder of hyprland.conf  that'll be a script executed before loading hyprland.conf and the user will write the enviroment variables there.

This would remove the need for a wrapped session in sddm too

I use several compositors, and
wayfire creates the executable and a wayfire-session script that calls wayfire, with desktop files for both.
labwc uses an environment file similar to autostart that has env vars, they only parse the env vars once though.
As far as desktop files it's easy enough to create one, for a wrapper script.
I've created several for various programs that don't provide one, XDG typically looks in /.local/applications and they get found by fuzzel/rofi/etc automatically.

done in d5093f7af0f2d1e6d39a3facd0806c36e9667af1 to dc7d783d1439b92b16bfe1851c2b699e7c7267e0
env = YOUR_ENV,VALUE in the config. Initialized prior to the Wayland server, so even stuff like WLR_NO_HARDWARE_CURSORS will work.

wrapper section got removed from the wiki too :)

Hey team, I am using NVIDIA and I am trying to set the necessary nvidia settings in a wrapper, and execute it in /usr/share/wayland-sessions but it does not seem to work.
This is hyprland.desktop
Name=Hyprland
Comment=An intelligent dynamic tiling Wayland compositor
Exec=/home/frosty/.local/bin/wrappedh1
Type=Application

and this is my  /home/frosty/.local/bin/wrappedh1
#!/bin/sh

cd ~

env = LIBVA_DRIVER_NAME,nvidia
env = XDG_SESSION_TYPE,wayland
env = GBM_BACKEND,nvidia-drm
env = __GLX_VENDOR_LIBRARY_NAME,nvidia
env = WLR_NO_HARDWARE_CURSORS,1

exec Hyprland

when I start the session, the environment variables are not set , how do I proceed? am I doing anything wrong here?

env keywords are invalid in bash. Where did you read you need a wrapper? Wrappers have been deprecated for months.

My bad I meant
#!/bin/sh

cd ~

export LIBVA_DRIVER_NAME=nvidia
export XDG_SESSION_TYPE=wayland
#export GBM_BACKEND=nvidia-drm
export __GLX_VENDOR_LIBRARY_NAME=nvidia
export WLR_NO_HARDWARE_CURSORS=1

exec Hyprland

I have a hybrid graphics card, intel and NVIDIA. When I try to set the GBM_backend as nvidia-drm my SDDM manager does not let me login. After correct password it pushes me back into the login screen instead of going inside. I ran "journalctl -b 0 --grep "renderer for" according to the docs present here and I get the result
"--- no entries --- "
any clue why? @vaxerski

No. Nvidia is fully community-driven, I don't provide support for it

oops

wait tf you mean there is no quick start page anymore its been removed ages ago

well that's odd. I confirm that that link I posted gets 404, but it didn't when i first posted that a few weeks ago. Maybe I had an old version cached in a browser or something..

I removed the page as it was deleted months ago and was terribly outdated, the automatic site sync util doesnt automatically remove old pages

Headslap Deja vu moment: forgot about this convo and ended up creating a wrapper again while troubleshooting some other stuff and finding the same old outdated wiki QuickStart link as 2nd google hit for "hyprland wrapper".. i see now that it's just a very old version :(
I wonder if its possible to put a WARNING: OUTDATED banner on outdated wiki pages?


Extra Pandoc Arguments do not recognise " or ' and mess up with directory paths and export fails.

Hello! First off I would like to thank you for this plugin, it has been of great use to me and so many others.
In the plugin settings, when you type Extra Pandoc Arguments, the conversion between the string and the actual command (line ~310 in the main.js file) is faulty. The " and ' are not applied properly, and the spaces essentially separate a single command in two.
I will give an example from your examples. Let's say we typed --bibliography "Zotero Exports\My Library.json". This would run
--bibliography "Zotero which does not exist, and the export will fail.
I found a work around for myself, and since I do not know any Java Script, I do think there are better ways of doing this. Specifically, I changed:
if (extraParams) {
    extraParams = extraParams.flatMap(x => x.split(' ')).filter(x => x.length);
    args.push(...extraParams);
}

to:
if (extraParams) {
    for (let i = 0; i < extraParams.length; i++) {
        let extraParam = extraParams[i].split('=');
        args.push(extraParam[0], extraParam[1]);
              }
}

This way you can only add arguments as --template=letter.tex (so the = is mandatory) and separate them by new lines, not spaces. Now you do not have a problem with --bibliography=Zotero Exports\My Library.json, meaning that even in a weird format, you get the full functionality of the argument settings.
I am hoping that with this issue report, we will eventually find a better work around on the main topic of  " and '.
P.S. For extra ease, when calling pandoc, instead of passing the extra arguments as (line ~ 11280) this.settings.extraArguments.split('\n'), I pass them as this.settings.extraArguments.replace('$VAULT_PATH$', this.vaultBasePath()).split('\n'), allowing me to use the vault path, without writing it out. It would be a cool feature to add to later releases. This way I can define a new --data-dir=$VAULT_PATH\.pandoc for pandoc, which will be saved in the local vault folder and better reflects Obsidian's mentality of having everything local and in the same folder. I am sorry for getting slightly off topic with this.

same issue here. Arguments parser doesn't respect " or '.

Hello, thank you for sharing!
I have the same problem. Where do you add the new script?

I'm having the same issue. Would love to see this fixed. Thanks for the workaround in the meanwhile!


install jsnode & script

Hi
I have establish to install jsnode. I don't know where to run the code provided in your instructions. How can i run it? I am in the terminal i am doing node upload.js but not working. I am doing for sure something wrong. Please give more begginer instructions

I have also try to donate your project but gives me an error if i am try to paypal. Please give me a contact way to contact you and help me to configure it with a payment & donation.

Hi, you can hire a developer from sites such as upwork or freelancer  to help you out.
Thanks


Fix resource visiting and position util issues

Purpose

With this fix the issue of not suggesting the symbols within the resource via the visibleSymbol API and fix NPE in position util.

Fixes #27482
Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

 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.Nadeeshaan Gunasinghe seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Update<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

Summary
This pull request updates the import_map.json and slack.json Deno modules to the latest published versions.

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
Requirements (place an x in each [ ] that applies)

[x] I’ve checked my submission against the Samples Checklist to ensure it complies with all standards
[x] I have ensured the changes I am contributing align with existing patterns and have tested and linted my code
[x] I've read and agree to the Code of Conduct

Thanks @selfcontained 🤾🏻


Extract GNU Readline helpers from REPL, replace one use of directories

Add a new crate, artichoke-readline.
This crate extracts out readline helpers from the artichoke REPL code to allow easier dependency management for platform-specific crates.
This setup allows dropping the problematic directories dependency which can no longer be upgraded. See:

https://github.com/artichoke/artichoke/pull/2543

dead link in the markdown job is expected: artichoke-readline docs haven't been deployed to GitHub Pages yet:
FILE: artichoke-readline/README.md
  [✓] https://github.com/artichoke/artichoke/actions
  [✓] https://discord.gg/QCe2tp2
  [/] https://twitter.com/artichokeruby
  [/] https://crates.io/crates/artichoke-readline
  [/] https://docs.rs/artichoke-readline
  [✖] https://artichoke.github.io/artichoke/artichoke_readline/
  [✓] LICENSE
  [✓] https://github.com/artichoke/artichoke/workflows/CI/badge.svg

  [/] https://img.shields.io/discord/607683947496734760
  ERROR: 1 dead links found!
  [/] https://img.shields.io/twitter/follow/artichokeruby?label=Follow&style=social
  [/] https://img.shields.io/crates/v/artichoke-readline.svg
  [/] https://docs.rs/artichoke-readline/badge.svg
  [/] https://img.shields.io/badge/docs-trunk-blue.svg

  13 links checked.
  [✖] https://artichoke.github.io/artichoke/artichoke_readline/ → Status: 404


Feature: Add Support for Optional Params when Adding Device to a Distribution

The Add Device to an existing Distribution endpoint provides parameters for further defining the Device attributes, however, the Distribution.add_device() method of the M2X Python client library does not support passing params.
Update this method to allow **params.

Fixed by #31


The devtools cannot be toggled to show/hide until an action was dispatched.

The devtools cannot be toggled to show/hide until an action was dispatched.

Fixed in v2


Migrating ESLint to flat config

#943  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @CatChen and the rest of your teammates on  Graphite


Handle expiration on refetch tokens and jwt tokens

REFETCH_TOKEN_EXPIRES
JWT_TOKEN_EXPIRES <-- add this
Both in minutes.

implementing
documenting

closed by #25


Generate JDBI ResultSetMapper

If a message has sql annotations, generate matching jdbi ResultSetMapper for the message class. Will only handle simple / flat tables.

Both jdbi.v2 and jdbi.v3 mappers included. Will be in 1.4.0


feature: add 'customresourcedefinitions' as a default resourceName in our examples for edgeplacements

Feature Description
customeresourcedefinitions are very common and it would be a good idea to include this in our examples on kubestellar.io
Proposed Solution
replace:
resourceNames: [ "bind-kubernetes", "bind-apps" ]

with:
resourceNames: [ "bind-kubernetes", "bind-apps", "customresourcedefinitions" ]

Want to contribute?

[ ] I would like to work on this issue.

Additional Context
No response

Here is my take on this. First, for downsynced objects: just like a namespace is automatically created when/where needed to transport a namespaced object that the explicit configuration says is downsynced, I think that it would be reasonable to automatically carry the needed CustomResourceDefinition (if any) along too. There is a little more to say, regarding the ObjectMeta of the Namespace object, and thus corresponding things to say about the ObjectMeta of the CustomResourceDefinition object.
Multiple WDSes can direct workload objects to the same WEC. You might expect this to be uncommon. For upsynced objects, you might expect it to be common for mulitple WECs to direct the same kind/namespace/name to the same WDS. This makes the question of consistency of colliding CRDs more prominent.

thank you for finding the backlog item here.  I think this will really help our customers.

FYI, here is what an APIBinding has to say for itself.
bash-3.2$ kubectl get apibindings tenancy.kcp.io-7axfd -o yaml
apiVersion: apis.kcp.io/v1alpha1
kind: APIBinding
metadata:
  annotations:
    kcp.io/cluster: 24ea110rxpjxryp1
  creationTimestamp: "2023-10-13T01:16:18Z"
  finalizers:
  - apis.kcp.io/apibinding-finalizer
  generation: 1
  labels:
    claimed.internal.apis.kcp.io/bmCdly9xXiUpEHe3ypvDwvXMTfoVZUE92mqAQf: LstvmbbzVDDOn90ZbhzSQO5U3DMCf88h1pZ
    internal.apis.kcp.io/export: bmCdly9xXiUpEHe3ypvDwvXMTfoVZUE92mqAQf
  name: tenancy.kcp.io-7axfd
  resourceVersion: "1663"
  uid: a0bb1ef6-97b6-4c5c-81d7-46dd6327b889
spec:
  reference:
    export:
      name: tenancy.kcp.io
      path: root
status:
  apiExportClusterName: root
  boundResources:
  - group: tenancy.kcp.io
    resource: clusterworkspaces
    schema:
      UID: 59d50429-f9ee-4639-9ceb-9333c682d151
      identityHash: 7cf8df60143bad7bc7e67135adfc7f15c7b5e77d32400b99f3618419d1a79df4
      name: v221219-c92ed8152.clusterworkspaces.tenancy.kcp.io
    storageVersions:
    - v1alpha1
  - group: tenancy.kcp.io
    resource: workspacetypes
    schema:
      UID: 7ad8ddb6-c3ac-429f-857c-e778ea9d6fba
      identityHash: 7cf8df60143bad7bc7e67135adfc7f15c7b5e77d32400b99f3618419d1a79df4
      name: v230110-89146c99.workspacetypes.tenancy.kcp.io
    storageVersions:
    - v1alpha1
  - group: tenancy.kcp.io
    resource: workspaces
    schema:
      UID: c6ad6c5e-c69e-4aa4-b554-0b228b83c7b9
      identityHash: 7cf8df60143bad7bc7e67135adfc7f15c7b5e77d32400b99f3618419d1a79df4
      name: v230116-832a4a55d.workspaces.tenancy.kcp.io
    storageVersions:
    - v1alpha1
  conditions:
  - lastTransitionTime: "2023-10-13T01:16:18Z"
    status: "True"
    type: Ready
  - lastTransitionTime: "2023-10-13T01:16:18Z"
    status: "True"
    type: APIExportValid
  - lastTransitionTime: "2023-10-13T01:16:18Z"
    status: "True"
    type: BindingUpToDate
  - lastTransitionTime: "2023-10-13T01:16:18Z"
    status: "True"
    type: InitialBindingCompleted
  - lastTransitionTime: "2023-10-13T01:16:18Z"
    status: "True"
    type: PermissionClaimsApplied
  - lastTransitionTime: "2023-10-13T01:16:18Z"
    status: "True"
    type: PermissionClaimsValid
  phase: Bound

FYI, here is what a CRD has to say about itself.
bash-3.2$ KUBECONFIG= kubectl get crds customizers.edge.kubestellar.io -o yaml
apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
metadata:
  annotations:
    controller-gen.kubebuilder.io/version: v0.10.0
  creationTimestamp: "2023-10-13T01:20:45Z"
  generation: 1
  name: customizers.edge.kubestellar.io
  resourceVersion: "3200"
  uid: 748af9a2-6599-4c34-a18d-0ffdaf888e60
spec:
  conversion:
    strategy: None
  group: edge.kubestellar.io
  names:
    kind: Customizer
    listKind: CustomizerList
    plural: customizers
    singular: customizer
  scope: Namespaced
  versions:
  - name: v2alpha1
    schema:
      ...
    served: true
    storage: true
status:
  acceptedNames:
    kind: Customizer
    listKind: CustomizerList
    plural: customizers
    singular: customizer
  conditions:
  - lastTransitionTime: "2023-10-13T01:20:45Z"
    message: no conflicts found
    reason: NoConflicts
    status: "True"
    type: NamesAccepted
  - lastTransitionTime: "2023-10-13T01:20:45Z"
    message: the initial names have been accepted
    reason: InitialNamesAccepted
    status: "True"
    type: Established
  storedVersions:
  - v2alpha1


How to create a future order at a specified price ？

For example, the current price of ETH is 2000 usdt. And now, I want to create a SHORT future order  at a specified price of 1500 usdt by the function " client.futures_create_order() " . So, when the price falls to 1500 usdt, the order will be triggered.  How to do it? thanks!

https://www.binance.com/en/support/faq/c-4?navId=4#18-62
https://binance-docs.github.io/apidocs/futures/en/#new-order-trade
Only when closing position can one set such order to be triggered. To open position, one needs to track orderbook or latest price from websocket API manually.


Added a newline to the end of index.md

Fixes #724
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

This pull request was created as a demo - closing out.  No functional changes suggested.


Constant-fold for the type-casting in switch-case labels

Closes https://github.com/shader-slang/slang/issues/5372
When the expresion used as a switch-case labels is a type-casting from floating-point type to an integer type, the floating-point literal also need to be constant-folded.

/format


Support any built-in controller for boids

cc @Nickniyihan
This PR,

Updates some of the interfaces/plumbing between vehicle index and bubble management to allow any of the built-in controllers to be used for boids (e.g. TrajectoryTracking which was the initial ask)
Pushes Visdom client down into SMARTS (from the envs) so that they're usable for social agents
Supports visualizing boid agent in Visdom

 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.


Update to go 1.17 and newest goreleaser

Background
Fixes brew warning about bad manifest.
Updates to latest go, goreleaser
Updates to dependencies
Versioning
patch?
Additional Requests to Reviewers

Tasks

[ ] Specs written
[ ] Manual testing

Changeset seems fine. Tests pass. I assume local testing was all good too?

will be doing a more complete smoke test manually - but some of the basic operations worked no problem.

everything worked. but I'm going to wait till after the holiday to push this since there are a lot of auto-updating use cases.


Prevent TestEnvironment class from emitting warnings.

Test runners pick up the TestEnvironment class as a valid test, then emiiting a warning as the class has its own __init__ method defined. To prevent this, the class is prepended with a single underscore.

Coverage remained the same at 93.605% when pulling 57e03b8e5831c04740f1b82f5f825d2bfb18a1c3 on mjmoore:master into 95c33e31a2f7d35fb8cae3b4a392bb640503c3de on jakubroztocil:master.


[EM] Return a full DMatrix instead of a Ellpack from the GPU sampler.

Slice meta info using GPU.
Work with DMatrix intead of Ellpack in the hist updater.
This way we can support page concatenation and batch training at the same time.

todos:

[x] Test NumNonMissing.

cc @rongou .


Removed channel tab from admin app

This closes #43

Since we don't have Channel tab anymore we have to add channels after database creation.
check this out :) http://www.entityframeworktutorial.net/code-first/seed-database-in-code-first.aspx


Move Guide topic: Assigning Pods to Nodes.

This change is

@pwittrock, Can you suggest a tech reviewer for this?

Putting this on hold until after the 1.6 release.

FYI, 1.6 is out.

Closing the PR ans starting over in https://github.com/kubernetes/kubernetes.github.io/pull/3071.


New Paper: RETRO

Detailed Description
https://medium.com/syncedreview/deepminds-retro-retrieval-enhanced-transformer-retrieves-from-trillions-of-tokens-achieving-c54313fec51d
Context
Paper is mostly about language models, but has an interesting idea for searching for similar text to help the model learn, and seems to work well. I believe we talked about that at some point, using similarity search, for satellite predictions, and this seems to say it works for nlp at least.
Possible Implementation
Have a database of similar historical PV data to search from, or satellite images, and use something like faiss for fast search. Then would be able to include historical past and future gsp data as well for those days to help with predictions

Related to #65


Leverage engine to execute queries with parameters

Summary

Fixes https://github.com/finos/legend-studio/issues/1535
Depends on https://github.com/finos/legend-engine/pull/1068
How did you test this change?

[ ] Test(s) added
[x] Manual testing (please provide screenshots/recordings)
[ ] No testing (please provide an explanation)

https://user-images.githubusercontent.com/73408381/196782197-4c3d95de-ef4d-4d00-a084-962c2eaab7c4.mov
execute query whose parameter is of type Enum:
https://user-images.githubusercontent.com/73408381/197635953-9e1d335b-e83d-4628-ac5e-761ea5034a80.mov

Please also test the enum parameters, model for reference
###Relational
Database test::DB
(
Table employeeTable
(
ID INTEGER PRIMARY KEY,
employeeType VARCHAR(200)
)
)
###Service
Service test::EnumParamEqualOpFilter
{
pattern: '/anumam/enumservice/{eType}';
owners:
[
'anumam',
'finead'
];
documentation: '';
autoActivateUpdates: true;
execution: Single
{
query: eType: test::EmployeeType[1]|test::Employee.all()->filter(x|$x.employeeType == $eType)->project([x|$x.id], ['ID']);
mapping: test::Map;
runtime: test::Runtime;
}
}
###Pure
Enum test::EmployeeType
{
CONTRACT,
FULL_TIME
}
Class test::Employee
{
id: Integer[1];
employeeType: test::EmployeeType[0..1];
}
###Mapping
Mapping test::Map
(
*test::Employee: Relational
{
~primaryKey
(
[test::DB]employeeTable.ID
)
~mainTable [test::DB]employeeTable
id: [test::DB]employeeTable.ID,
employeeType: EnumerationMapping EmployeeTypeMapping: [test::DB]employeeTable.employeeType
}
test::EmployeeType: EnumerationMapping EmployeeTypeMapping
{
CONTRACT: ['FTC', 'FTO'],
FULL_TIME: ['FTE']
}
)
###Runtime
Runtime test::Runtime
{
mappings:
[
test::Map
];
connections:
[
test::DB:
[
connection_1:
#{
RelationalDatabaseConnection
{
store: test::DB;
type: H2;
specification: LocalH2
{
testDataSetupCSV: 'default\nemployeeTable\nID,employeeType\n101,FTC\n102,FTE\n103,FTO\n104,FTCC\n---';
};
auth: DefaultH2;
}
}#
]
];
}

Please also test the enum parameters, model for reference

Could we file an issue to improve editing of multplicity for parameters in query builder.
We should only allow (0..1,1, 0..*) and make it more user friendly options such as optional, required, list


tarfile.ReadError: not an lzma file

When downloading model using download.py, there are some trouble. To avoid this, I had to download directly using the URL at the beginning of the script and to decompress it myself in the pretrained-models folder.
Traceback (most recent call last):
  File "download.py", line 105, in <module>
    main()
  File "download.py", line 102, in main
    download_model(name=args.model)
  File "download.py", line 79, in download_model
    tar = tarfile.open(file_destination, "r:xz")
  File "/users/troux/.conda/envs/character-bert/lib/python3.8/tarfile.py", line 1621, in open
    return func(name, filemode, fileobj, **kwargs)
  File "/users/troux/.conda/envs/character-bert/lib/python3.8/tarfile.py", line 1734, in xzopen
    raise ReadError("not an lzma file")
tarfile.ReadError: not an lzma file

Regards,

My case too

It's fixed, sorry for the delay :)


Link is wrong

The link to "Packaging the Permission Set" is not going to the right spot.

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

ID: 885cbacd-b3e7-1730-812c-9148ebfc90e9
Version Independent ID: eb11ce7e-1efb-106c-5d79-19c206860da0
Content: Checklist for Submitting Your App - Business Central
Content Source: dev-itpro/developer/devenv-checklist-submission.md
Service: dynamics365-business-central
GitHub Login: @SusanneWindfeldPedersen
Microsoft Alias: solsen

Thanks for the feedback. The link points to a topic which is very lengthy, but under the SourcePath you can read more about how to package the permission sets. With the next version of Business Central, or if you are in the Ready to Go program, you have the option of exporting permission sets using VS Code Exporting Permission Sets.


Testing functional components

Apologies if this is a duplicate
I am having trouble figuring out how to test function expressions (equivalent of component methods in a react class) in functional components?
const someFunc = ({someValue}) => {
 const someCalc = () => {
   ...
   return result
   }
 return <div>{someCalc}</div>
}

How would we test the someCalc() here?

You can't. Closure privacy is the only true privacy JS has, and private things shouldn't be tested.
You certainly can and should make assertions on the children of the element your component renders - but that's all you can do.
(Separately, component names need to start with a capital letter - ie. SomeFunc, not someFunc)


JS: add dataflow model of 'async' package

This adds a model of the async package. It handles calls to async.waterfall and all functions in the collection category.
There are still some functions we don't handle, like async.queue. Outside the collection category, only waterfall is handled because I've seen it used to handle user-controlled data in a few places.
Evaluation shows no new results and a minor slow-down.
I've named the QL module AsyncPackage to avoid hijacking the QL module Async, which might be needed for a more general purpose in future.

@xiemaisi any further comments?

Fixed the typos, also added a change note, and rebased to fix change note conflict.


Add feedback to result

Good to go. Please also increase the version in pubspec.yaml so we can publish it right after merging.


The repartition method of insert-select

Fixes https://github.com/citusdata/citus_docs/issues/898

@pykello does this look good now?

@jonels-msft yes, it looks good


Missing new lines in reply messages.

They were missing new lines in the replies from coqbot, messing with the rendering of the details HTML tags.

Good catch, thanks!

Testing:

Testing:

Testing:
@coqbot minimize
# You can insert a bash script which produces the error message here,
# our bot will answer with a stripped down version of it.
# Example:
#opam install -y coq-ext-lib
#eval $(opam env)
#mkdir temp
#cd temp
#wget https://github.com/coq/coq/files/4698509/bug.v.zip
#unzip bug.v.zip
#coqc -q bug.v

@coqbot minimize
# You can insert a bash script which produces the error message here,
# our bot will answer with a stripped down version of it.
# Example:
#opam install -y coq-ext-lib
#eval $(opam env)
#mkdir temp
#cd temp
#wget https://github.com/coq/coq/files/4698509/bug.v.zip
#unzip bug.v.zip
#coqc -q bug.v

@coqbot: run CI now

Testing:
@coqbot: run CI now

@coqbot: minimize it
opam install -y coq-ext-lib
eval $(opam env)

mkdir temp
cd temp
wget https://github.com/coq/coq/files/4698509/bug.v.zip
unzip bug.v.zip
coqc -q bug.v


Provide ES5 browser build for pretty-format

Do you want to request a feature or report a bug?
Report an unintended regression.
What is the current behavior?
pretty-format lacks build-es5 subdirectory after the excellent improvement in #3532
See https://github.com/facebook/jest/pull/3532/files#diff-9b3b0a5fd27925d64d045cf1394e5143L11
What is the expected behavior?
There are enough dependents on pretty-format and its code goes to enough effort so an ES5 build is possible, that we will probably be sorry to publish the next version without it.
@skovhus In case there is more to consider beyond the browser property in package.json would you be willing to look at this?
@cpojer I guess this implies pretty-format never had a smoke test for the build-es5 subdirectory. Is it worth the effort to test it with the subset of ES5 values?

Should be fairly simple to add, just descoped it in #3532.
Can be solved by:

add browser field in package.json
add it to pretty-format to the Karma browser tests I added to ensure it works


File is not a zip file

i have also cloned from the link you provided in the issues but still its the same

@jsjadh This screenshot doesn't include using the gitlab link. So it's not clear which one you are using

print.pdf
hello , im also getting this error , any help would be appreciated


[IphoneX] can't get fullscreen while playing

FFS.
PLEASE USE THE TEMPLATE
https://github.com/sampotts/plyr/issues/new?template=bug.md

Also. It's not something Plyr can really fix unless we can somehow inject/remove the viewport change on enter/exit fullscreen ... https://webkit.org/blog/7929/designing-websites-for-iphone-x/


Programming Language Icons

Okay so I wasn't sure what to post this as "Feature Request" or "Icon Request" and I think it's kind of both.
I think it would be a great idea to have Programming Language icons/logos into the set of icons. I'm not sure about anybody else, but there doesn't seem to be that many icon sets that actually have most, if not all programming language logos.
Useful when building sites for developers, portfolio or whatever. It would be helpful having these icons in the set. So, I am proposing a programming language set of icons for this system.
Think it's a good idea?
Here's an example: https://konpa.github.io/devicon/

Thank you for your advice.
The tag Feature Request  means to add new features to the official website, such as downloading icons in XML encoding format, etc.
I‘m afraid we may not be able to add most of the programing language icons, especially there is already good icon library exits. RemixIcon was not made for LOGOs, we only add logos commonly used in websites or Apps. Currently, we've included several well-known and commonly used programming icons, such as Vue.js or Angular icons.
If you think some of the dev icons are important for many users, can you list them so that I can tell which one should we include?
Thanks again for your request.


Desktop version fails to build ('openssl_fips' is not defined)

the error occurs while trying to build<EMAIL_ADDRESS>from source:
npm ERR! gyp: name 'openssl_fips' is not defined while evaluating condition 'openssl_fips != ""' in binding.gyp while trying to load binding.gyp
relevant node-gyp issue thread:
https://github.com/nodejs/node-gyp/issues/2673
dependency tree:
npm ls<EMAIL_ADDRESS><EMAIL_ADDRESS>`--<EMAIL_ADDRESS>  `--<EMAIL_ADDRESS>    `--<EMAIL_ADDRESS>

When manually going through these steps, this error appears when running the following command:
npm run desktop:local
Appending the flag to that specific command fixes the issue:
npm run desktop:local --openssl_fips=''

After some testing building in my computer (OS: ArchLinux, npm version: 8.19.4, node version: 16.20.1), my recommendation that would allow for an easy installation is to modify the desktop:build and desktop:local scripts directly in the packages.json file.
Each one of these should include an openssl configuration flag.
These work:
"desktop:build": "NODE_OPTIONS=--openssl-legacy-provider npm run wallet:build-desktop && npm run desktop:compile",
"desktop:local": "npm_config_openssl_fips='' electron-builder -p never"
With this modification, the github build release should also work.
From looking at the above-cited issue (https://github.com/nodejs/node-gyp/issues/2673#issuecomment-1477682343), these flags may not be necessary with more recent versions of electron and electron-builder, so it may be a worthy project to update the dependencies.

You can see the successful action run here, modifying only the packages.json file: https://github.com/nanogarden/Nault/actions/runs/5843583237
The "cross-env" npm package allows you to pass a variable in a way that will be accepted across platforms. So, the flag is passed in this way:
"desktop:local": "cross-env npm_config_openssl_fips='' electron-builder -p never"
And cross-env is added to the dependencies as:
"cross-env": "^7.0.3",

Hey @keerifox, I know this is taken care of, but I noticed while looking at the PR's that PR #566 "Bump electron from 9.4.4 to 18.3.7" built correctly, while several builds before it and everything after it failed to build.
So, I have tested by removing the openssl_fip flag and updating the electron version to the version that the bot jumped to (^18.3.7), and it builds: https://github.com/nanogarden/Nault/actions/runs/5859447706
I'm just letting you know in case that you consider a cleaner solution than passing a flag!
I also tried bumping electron to the newest version (25.5.0), but that fails: https://github.com/nanogarden/Nault/actions/runs/5859529104/job/15885732316


Update schemas to version v0.26.0

This is an auto-generated PR.
Schemas release: https://github.com/ONSdigital/eq-questionnaire-schemas/releases/tag/v0.26.0

Once this merges there is a benchmark pull request that needs to be merged before the daily overnight test - https://github.com/ONSdigital/eq-survey-runner-benchmark/pull/48


Backend has too many servers configured, every second request fails

Do you want to request a feature or report a bug?
Bug.
What did you do?
I have an Ingress configured with a single backend service which points to a single pod:
[...]
spec:
  rules:
    - host: [REDACTED]
      http:
        paths:
          - path: /issue-20-alternatives-a/
            backend:
              serviceName: review-app-issue-20-alternatives-a
              servicePort: 80

# kubectl describe ingress review-app-issue-20-alternatives-a
Name:             review-app-issue-20-alternatives-a
Address:          [REDACTED]
Default backend:  default-http-backend:80 (<none>)
Rules:
  Host                                          Path  Backends
  ----                                          ----  --------
  [REDACTED]
                                                /issue-20-alternatives-a/   review-app-issue-20-alternatives-a:80 (<IP_ADDRESS>:80)

# kubectl describe service review-app-issue-20-alternatives-a
[...]
Selector:          app=review-app-issue-20-alternatives-a
Type:              ClusterIP
IP:                <IP_ADDRESS>
Port:              <unset>  80/TCP
TargetPort:        80/TCP
Endpoints:         <IP_ADDRESS>:80
Session Affinity:  None
Events:            <none>

What did you expect to see?
Normal operation, all requests served successfully
What did you see instead?
Every second request fails with "bad gateway".
I'm guessing it has to do with the fact that in the Traefik Dashboard there are two Servers listed:

<IP_ADDRESS>:80 is from the Kubernetes Service but I don't know where <IP_ADDRESS>:80 comes from or how to get rid of it.
Output of traefik version: (What version of Traefik are you using?)
The Helm Chart that comes with k3s.
Dashboard shows: V1.7.19 / MAROILLES
What is your environment & configuration (arguments, toml, provider, platform, ...)?
k3s
https://k3s.io/
https://github.com/rancher/k3s
If applicable, please paste the log output in DEBUG level (--log.level=DEBUG switch)
Currently it seems my log level is pretty high because the log doesn't say much:
{"level":"info","msg":"Server configuration reloaded on :8080","time":"2020-07-07T12:55:31Z"}
{"level":"info","msg":"Server configuration reloaded on :9100","time":"2020-07-07T12:55:31Z"}
{"level":"info","msg":"Server configuration reloaded on :80","time":"2020-07-07T12:55:31Z"}
{"level":"info","msg":"Server configuration reloaded on :443","time":"2020-07-07T12:55:31Z"}
{"level":"info","msg":"Skipping same configuration for provider kubernetes","time":"2020-07-07T12:55:31Z"}
{"level":"info","msg":"Server configuration reloaded on :8080","time":"2020-07-07T12:55:33Z"}
{"level":"info","msg":"Server configuration reloaded on :9100","time":"2020-07-07T12:55:33Z"}
{"level":"info","msg":"Server configuration reloaded on :80","time":"2020-07-07T12:55:33Z"}
{"level":"info","msg":"Server configuration reloaded on :443","time":"2020-07-07T12:55:33Z"}

Hi @AndreKR - would it be possible for you to open up a thread in the community forum with details on how you've configured your services (deployment/service yaml), and possible steps to reproduce this issue you're having? It's hard to say what the issue could be without knowing more about the services and how they're configured.
Thank you

Hi! I'm Træfiker :robot: the bot in charge of communication regulation.
Thanks for your interest in Traefik!
We dedicate the issue tracker to bug reports and feature requests only. My advanced AI has spotted that your issue might be a configuration problem or relates to something that doesn't look like a bug.
To confirm this, please join our Community Forum and reach out to us on the Traefik section.
In case I'm wrong (well, that would be embarrassing :sweat_smile:), my developers will re-open the issue and fix me!
In the meantime, you can double check Traefik's documentation.

Done


Replace string references used in non user facing components in Feast

Background
Currently Feast uses string references in 3 areas:

Feature Set References
Feature References
Subscriptions

As a result many implementations of string reference parsing and formatting has cropped up all over Feast's code:

Feast Serving's RefUtil
Feast Core's Store
Feast Ingestion's SpecUtil
Feast Storage Writers: Redis RedisCluster.
Feast Storage Retrievers Redis RedisCluster
etc...

Problem
Changes to the feature/feature set references/subscriptions are difficult as we have to track down all the different string parsing/formatting implementations. Changes to these areas should not require a comb over the entire codebase to rectify all these parsing and formatting implementations.
Examples  of currently WIP and potential changes that is currently affected by this and why the problem is relevant:

Feature Set version removal #386
Changes to the Feast concept & hierarchy and data model #479
Removal of Projects from Feature References when in the string form #631

Scope
String references that should still be kept around:

those exposed by the user facing API (ie the SDKs, config files) as they need to be humanly readable.
those used by interface with components outside of feast (ie PostgreSQL, BigQuery, etc.), although non string references should be preferred if possible.

Possible Solution
Replace string references in non user facing components with their Protobuf equivalents.
Examples of this include:

Using message types directly in protobuf definitions:

message FeatureRow {
    repeated Field fields = 2;
    google.protobuf.Timestamp event_timestamp = 3;
    FeatureSetReference feature_set_ref = 8;
    string ingestion_id = 7;
}

Using references as keys in maps directly.

HashMap<FeatureSetReference, FeatureSetSpec> featureSetMap = new HashMap<>();

:warning: There might be possible caveats to this

Serialize references without having to extract its internals:

String refStr = Base64.getEncoder().encodeToString(featureSetReference.toByteArray());

Some comments:
I agree on the Proto message type, but FeatureReferences should be a non-Proto model class ideally, with toProto and fromProto. This would allow us to also have a single toStringRef() or fromStringRef().
FeatureSetRef and FeatureRef seem very similar. I think we could possibly have the following after version removal
// Defines a composite key that refers to a unique FeatureSet
message FeatureSetReference {
    // Name of the project
    string project = 1;
    // Name of the FeatureSet
    string name = 2;
}

message FeatureReference {
    // Name of the feature set
    FeatureSetReference feature_set_ref = 1;

    // Name of the feature
    string name = 2;
}

Although this would increase nesting, which is also frowned upon by some.

I mostly agree with the problem, but I'm not convinced about the solution. Swapping strings with encoded protobuf is merely trading one compatibility issue for another (less readable) one, in my mind. I think we're missing clear stated goals to answer whether the solution will meet them.
Definitely agree with @woop in general on avoiding the generated classes in domain logic if this is part of a solution—we've been moving away from that and although there is overhead (CPU + allocation/GC, and code maintenance), I believe it is a net win. The noted hash key behavior is one of many example pitfalls.
There are perhaps two related problems conflated, it could help to distinguish goals for solving them:

Code maintenance effort and fragility. This is primarily what the issue description elaborates so far.
Representations in persistence/serialization create challenges for evolving the data model.

For the first, I believe some goals for improving could be met sheerly through code factoring, encapsulation of the domain concepts of references as first-class types instead of Strings pervading.
The second one is harder, I'm not sure there is an infinitely flexible solution with reasonable complexity (though I'd be glad to hear suggestions), rather some design decisions need to be reached on #479 that we're ready to live with for awhile and/or have a plan for evolving. It's a conceptual problem before it's a technical one. If we're ready to go with https://github.com/gojek/feast/issues/479#issuecomment-615544705 as the first steps, I think that should be a clear part of specs in this issue or an explicit non-goal, since #631 seems meant to cover that at least in part.
With this perspective, the first problem could be appreciably addressed without being blocked by exhaustive answers for #479, except that it might overlap a lot with work for #631. Once goals of this issue are clearly established, it might just become a subtask of #631.
Definitively solving the second is blocked by #479 in such ways that it could put this issue at risk of not being closeable in the near term.

For the first, I believe some goals for improving could be met sheerly through code factoring, encapsulation of the domain concepts of references as first-class types instead of Strings pervading.

Putting this another way, I'd like to explore how this might look with only code changes that are not proto schema changes, then evaluate if and when proto changes should be made. If there can be some win from the first step, it seems more in line with @woop's inclination in https://github.com/gojek/feast/issues/479#issuecomment-615544705 to be conservative about the conceptual + data model direction, to defer until we learn more.


LSM6DS0 Gyroscope rad/s Calculation Error

Describe the bug
It appears the LSM6DS0 driver uses an incorrect constant when calculating the rad/s angular velocity for its gyroscope.
The following calculation is used:
// drivers/sensor/lsm6ds0/lsm6ds0.c
static inline void lsm6ds0_gyro_convert(struct sensor_value *val, int raw_val,
          float numerator)
{
  double dval;

  dval = (double)(raw_val) * numerator / 1000.0 * SENSOR_DEG2RAD_DOUBLE;
  val->val1 = (int32_t)dval;
  val->val2 = ((int32_t)(dval * 1000000)) % 1000000;
}

With the SENSOR_DEG2RAD_DOUBLE constant defined as:
// drivers/sensor/lsm6ds0/lsm6ds0.h
#define SENSOR_DEG2RAD_DOUBLE (180.0 / SENSOR_PI_DOUBLE)

Resulting in an incorrect value (in deg^2 / rad).
The correct value can be obtained by modifying the macro definition to:
// drivers/sensor/lsm6ds0/lsm6ds0.h
#define SENSOR_DEG2RAD_DOUBLE (SENSOR_PI_DOUBLE / 180.0 )

To Reproduce
The samples/shields/x_nucleo_iks01a1 project can be used. However an additional sensor_sample_fetch needs to be added for the lsm6ds0 gyroscope, as it is currently not included in the example.
Expected behavior
When the lsm6ds0 is near stationary, the measured angular velocity should be close to 0. Currently the readings for each axis are floating up to +- 100 rad/s.
Environment (please complete the following information):

OS: Linux
Toolchain :  gcc-arm-none-eabi 1.80201.181220 (8.2.1).
Commit SHA or Version used: Zephyr 2.20600.210721 (2.6.0) ,

@stuianna Please take a look to the fix. I missed this bug until now, sorry.

@avisconti Works as expected. Sorry I couldn't get back to you earlier.
Thanks.


Simpler Metadata querying from inside the VM

Hello!
I would like to use gcloud-node on a VM to fetch its Metadata. I expected this to be simple, since the CLI way of grabbing the Metadata is a simple CURL to a magic URL. My expectation would be that gcloud-node wraps that nicely for me already. Unfortunately, this is not the case.
Instead, the docs say:
var gcloud = require('gcloud')({
  keyFilename: '/path/to/keyfile.json',
  projectId: 'grape-spaceship-123'
});

var gce = gcloud.compute();

var zone = gce.zone('zone-name');

var vm = zone.vm('vm-name');

var metadata = vm.getMetadata(); // Finally!

Whoa, whoa, whoa, I'm already on the VM in question, do I really need to know Project ID, Zone, and VM Name just to get back to square one?
How about some kind of factory method for grabbing the current VM, such as:
var vm = gcloud.getCurrentVM();

...that does whatever magic is needed to figure out where it is running? (Or even better maybe just getLocalMetadata()?)
Just a friendly suggestion! I spent a day trying to figure out "the right way" to do this and I am ultimately falling back to the HTTP method, wanted to put this here in case it is helpful for someone else or adds some usability to the project.
Thank you!

I'm a big fan of that. A couple questions:

If you run this while not on a VM, should the result be null or an
Error thrown ?
If you're trying to develop against this, how do you do it?

This is a great explanation of what you went through. We actually have this discussed in #917, please feel free to add any thoughts over on that issue, as we talked through some problems/solutions.
Supporting this is not exactly at the top of the priority list (reaching 1.0, using promises natively, introducing more services are currently ranked higher), but it's definitely planned.

@lorennorman @jgeewax please continue discussing in #917


UI/UX Stretch Goals - Part 2

This is part 2 of the UI/UX updates for side by side.
Add Cell Type info to new info panel created here

Add cell type endpoint
Add tab to info panel
Add info icon to cell types to trigger cell type tab
Add search box to cell tab
https://github.com/chanzuckerberg/single-cell-explorer/assets/8716829/f242406e-4ac3-41e8-8482-4fb9b96f0278

figma: https://www.figma.com/design/eJ3acPxG04PKVlom6eS8ft/Spatial?node-id=0-1&t=yAWU6j6wSLKV9eIJ-0

@kaloster what's the status of this ticket again? Thank you!

@kaloster realized that this ticker is blocked by not having easy access to cell ontology id (ticket). Moved to post launch epic


[Narwhal] use ToBytes and FromBytes in Events

This simplifies the (de)serialization of Events and removes a dependency on bincode.
In addition, this change appears to reduce the number of allocations.

The CI error is unrelated.


feat/places-feature

Please review before merging.

:tada: This PR is included in version 1.11.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


wse create binding doesn't include ;e or ;e/ct  etc.

wse create binding doesn't include ;e or ;e/ct (for e.g it binds to /echo)

HTTP request path and headers are used to to determine next protocol
and that will help in finding the right binding.
This will reduce the number of http bindings

Forward porting the change set.

@jitsni looks good, just a few test scripts need to be updated

@jitsni I just merge this to 5.0 (wse reduce bindings). You can forward port any 4.0 fixes now.


Processor can't fetch lava from Deep resonance tank

I set up a program to fetch liquid from a tank and I'm just getting a 0 as log message without anything happening.
Inserting a bucket to only fetch specific Liquids doesn't work at all.
Version  1.11-1.6.3

Can you give more information? Did you specify a side or not? A bit more details would be nice

Yes, I tried specifying a side which did nothing. The program is literally every 20 ticks move 100ml of lava from the tank nothing more. I also allocated some storage of the Multitank inside the processor.

Can you copy/paste the program here? (just do ctrl-a/ctrl-c in the programmer and paste it here)

My program is just this.
[
{
"pos": {
"x": 2,
"y": 2
},
"opcode": {
"id": "do_fetchliquid",
"primary": "R",
"parameters": [
{
"type": "inventory",
"value": {
"side": "south",
"intside": "up"
}
},
{
"type": "integer",
"value": {
"v": 100
}
},
{
"type": "fluid",
"value": {
"null": true
}
},
{
"type": "integer",
"value": {
"v": 0
}
}
]
}
},
{
"pos": {
"x": 1,
"y": 2
},
"opcode": {
"id": "ev_timer",
"primary": "R",
"parameters": [
{
"type": "integer",
"value": {
"v": 50
}
},
{
"type": "boolean",
"value": {
"null": true
}
}
]
}
},
{
"pos": {
"x": 3,
"y": 2
},
"opcode": {
"id": "do_log",
"primary": "R",
"parameters": [
{
"type": "string",
"value": {
"fun": "last_str"
}
}
]
}
}
]

Did you try the fetchliquid without a side too? i.e. just say 'south' and don't specify the intside

Great now I just need to figure out why this didn't work the last time I tried it... Probably a combination of fixing something else and forgetting to set everything back to zero after I found out what it was...


(packageName)

Chocolatey Version
1.1.0
Chocolatey License
No response
Package Version
1.16.3
Current Behaviour
A preliminary note to this error is that I tried navigating to C:\ProgramData\chocolatey\lib\virtualbox\tools, only to see that not even the virtualbox directory exists under C:\ProgramData\chocolatey\lib
Installing virtualbox...
Microsoft.PowerShell.Commands.WriteErrorException
VirtualBox-6.1.34-150636-Win.exe: error: Installation failed! Error: The system cannot open the device or file specified.
ERROR: Running ["R:\Temp\chocolatey\virtualbox\6.1.34\VirtualBox-6.1.34-150636-Win.exe" -s -l -msiparams REBOOT=ReallySuppress ALLUSERS=1 ] was not successful. Exit code was '1'. See log for possible error messages.
The install of virtualbox was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\virtualbox\tools\chocolateyInstall.ps1'.
See log for details.
Expected Behaviour
It should install without this issue.
Steps To Reproduce
My best guess is that this is just the result of trying to run this type of installation on a laptop with an AMD processor. I've waited quite some time to report this, as I figured re-installing my Windows installation would fix it, and I only just got around to doing that now. Re-installing Windows is a pain.
Environment
- Operating System: Windows 10.0.19044
- PowerShell Version: 5.1.19041.1682
- Shell: A fresh Windows PowerShell in Administrator mode? I'm not sure what you want here.

Chocolatey Log
https://gist.github.com/logan-kling/be69b62d38644300bd4c19b9be7c4e1d

Anything else?
No response

@logan-kling Can you go back and update the issue title?

As the changes that pauby requested hasn't been done, I'll be closing this issue.
Additionally, the issue you are seeing is not related to the package, but rather the installer itself since you have changed the location of the %TEMP% directory.
See https://forums.virtualbox.org/viewtopic.php?t=92774