Linear classification performance on CIFAR10/STL10 DataModules drops from Lightning 0.8.5/Bolts 0.1.0 to Lightning 0.9.0/Bolts 0.1.1

🐛 Bug
Linear classification performance on CIFAR10/STL10 Bolts DataModules drops from Lightning 0.8.5/Bolts 0.1.0 to Lightning 0.9.0/Bolts 0.1.1.
I know you do careful performance-matching testing for the different Lightning versions, so I thought I'd post this here too thinking it could be from something in the DataModules changing rather than Lightning. However, since switching Bolts versions gave errors without switching Lightning versions, I can't be certain about that. It could also be some change in defaults.
To Reproduce
Steps to reproduce the behavior:

Train Moco on (unlabeled data from) STL10 DataModule with the Bolts implementation using resnet18 (I can provide a pretrained model of this part if it would be helpful)
Load trained model, freeze weights, set .eval()
Add a linear classifier on top of the penultimate layer representation, train with (labeled data from) STL10 DataModule with traditional self-supervised performance evaluation. (Train for 100 epochs with batch size of 256 and initial learning rate of 0.12; decay learning rate by a factor of 0.2 at epochs 60,80.)
Observe substantial drop in performance

On STL10, I am getting a performance drop of 16% top-1 validation accuracy (88->72), and a 0.5 increase in cross-entropy loss (0.3 to 0.8). On CIFAR10 I get a smaller, but consistent drop of 2% top-1 validation accuracy. Both of these are using the exact same code, just with switching conda envs. (The reason for changing both the Lightning version and the Bolts version is that it seems required for compatibility between the two.)
Code sample
I can provide pretrained models on CIFAR10 and STL10 if that would be helpful, along with my full hyperparameter configs, but not the code at this time (sorry!). It's just a linear classifier though.
Expected behavior
Expected: same performance across versions.
Environment

PyTorch Version (e.g., 1.0): 1.5.1 with the former/1.6.0 for the latter (compatibility)
OS (e.g., Linux): Linux
How you installed PyTorch (conda, pip, source): conda
Build command you used (if compiling from source):
Python version: 3.8.3
CUDA/cuDNN version:
GPU models and configuration: 2080Ti
Any other relevant information:

Additional context

@annikabrundyn mind have a look 🐰

The reason there is a decline in performance of the linear classifier is that DataModules were initially mixing training and validation sets. Now we have made sure that we pass a fixed random seed to the random_split function in the datamodules.

@ananyahjha93 thanks for clearing this up - that makes a lot of sense. I'm going to close the issue then 👍


[IMUSensorBroadcaster] Create ParamListener and get parameters on configure

Hi,
It seems there is a very similar issue as in https://github.com/ros-controls/ros2_controllers/pull/698. The IMUSensorBroadcaster stopped working for me.
After looking for the issue, I've found that there is a validation of the parameter sensor_name (added here), that is failing always because the parameters have not been loaded into the node yet and then, the parameter is empty at that point.
I have the parameter declared in the yaml file that I'm loading in the node but the error I'm having is the following:
[spawner-4] [INFO] [1696928866.880159937] [spawner_imu_sensor_broadcaster]: Set controller type to "imu_sensor_broadcaster/IMUSensorBroadcaster" for imu_sensor_broadcaster
[gzserver-1] [INFO] [1696928866.881161921] [controller_manager]: Loading controller 'imu_sensor_broadcaster'
[gzserver-1] [ERROR] [1696928866.897606928] [imu_sensor_broadcaster]: Exception thrown during init stage with message: Invalid value set during initialization for parameter 'sensor_name': Parameter 'sensor_name' cannot be empty
[gzserver-1]
[gzserver-1] [ERROR] [1696928866.897674246] [controller_manager]: Could not initialize the controller named 'imu_sensor_broadcaster'
[spawner-4] [FATAL] [1696928866.904203561] [spawner_imu_sensor_broadcaster]: Failed loading controller imu_sensor_broadcaster
[ERROR] [spawner-4]: process has died [pid 61163, exit code 1, cmd '/opt/pal/alum/lib/controller_manager/spawner imu_sensor_broadcaster --controller-manager controller_manager --controller-type imu_sensor_broadcaster/IMUSensorBroadcaster --param-file /home/yueerro/git/my_dockers/shared/alum/staging/pmb3_ws/install/pmb3_controller_configuration/share/pmb3_controller_configuration/config/imu_sensor_broadcaster.yaml --ros-args'].

I guess the same happens with the validation of the parameter frame_id (added here).
By creating the ParamListener and reading the parameters on configure instead of on init is working for me:
[spawner-4] [INFO] [1696930457.282406584] [spawner_imu_sensor_broadcaster]: Set controller type to "imu_sensor_broadcaster/IMUSensorBroadcaster" for imu_sensor_broadcaster
[gzserver-1] [INFO] [1696930457.283297464] [controller_manager]: Loading controller 'imu_sensor_broadcaster'
[gzserver-1] [INFO] [1696930457.295975680] [controller_manager]: Setting use_sim_time=True for imu_sensor_broadcaster to match controller manager (see ros2_control#325 for details)
[spawner-4] [INFO] [1696930457.302856674] [spawner_imu_sensor_broadcaster]: Loaded imu_sensor_broadcaster
[spawner-4] [INFO] [1696930457.305764498] [spawner_imu_sensor_broadcaster]: Loaded parameters file "/home/yueerro/git/my_dockers/shared/alum/staging/pmb3_ws/install/pmb3_controller_configuration/share/pmb3_controller_configuration/config/imu_sensor_broadcaster.yaml" for imu_sensor_broadcaster
[spawner-4] [INFO] [1696930457.306153768] [spawner_imu_sensor_broadcaster]: Loaded /home/yueerro/git/my_dockers/shared/alum/staging/pmb3_ws/install/pmb3_controller_configuration/share/pmb3_controller_configuration/config/imu_sensor_broadcaster.yaml into imu_sensor_broadcaster
[gzserver-1] [INFO] [1696930457.306952999] [controller_manager]: Configuring controller 'imu_sensor_broadcaster'
[spawner-4] [INFO] [1696930457.333095661] [spawner_imu_sensor_broadcaster]: Configured and activated imu_sensor_broadcaster
[spawner-4] Set parameter sensor_name successful
[spawner-4] Set parameter frame_id successful
[spawner-4] Set parameter publish_rate successful
[INFO] [spawner-4]: process has finished cleanly [pid 66228]

I would like to have also a backport for humble.
Thank you in advance!

I think you are onto something!
Even recent code such as the toy controller I created for the roscon workshop does the same in the on_init() function. That being said, those parameters had a default value and no validator.
I think we need to take a closer look at generate_parameter_library and find where validation happens.
On first read I don't see anything wrong with moving those two lines into on_configure() and it'd probably be good to future-proof all our controllers if this is the right solution.

Maybe @tylerjw can help to answer how to use generate_parameter_library properly here?

thanks @tylerjw, best-practice would be then doing it in on_configure of all lifecycle nodes?

Maybe, I'm not confident on the best way to use a lifecycle node.

Hello!
As far as I have checked, It seems like we can declare params in the init method, however, we can only retrieve them in the configure phase as we tend to register the callbacks of the node post on_init method.
https://github.com/ros-controls/ros2_control/blob/bd6911d663abb687dc956bf19a104d03648f8985/controller_interface/src/controller_interface_base.cpp#L34-L55
I think for the same reason, we get the parameters of the update_rate and is_async in the on_configure method
https://github.com/ros-controls/ros2_control/blob/bd6911d663abb687dc956bf19a104d03648f8985/controller_interface/src/controller_interface_base.cpp#L85-L89

I discussed this with @saikishor

In general, parameters should be declared in on_init to be able to set parameters (e.g. via CLI) before the controller is configured. This is also the issue with the failing tests of this PR -> they are not declared and, e.g.,
imu_broadcaster_->get_node()->set_parameter({"sensor_name", sensor_name_}); fails,.
If generate_parameter_library is used, this is done by the constructor of the ParamListener by calling the declare_params method.

But I still don't know why get_params is failing for @YueErro here. Could you check if the creation of ParamListener in the on_init() but leaving get_params() in the on_configure() works for you? Then the CI should be happy here too.

Hello @YueErro!
Can you please check if the fix in the above PR address your issue or not?

Fyi I'm happy to merge this PR if you get a green CI

@tylerjw and @christophfroehlich will your fix of those issues in Generate Parameter Library be beckported to humble? If yes, then there is not need for fixing this.

Yes, I will backport to humble.


angularjs not loaded when installed via composer

Hi I have installed angularjs and many other stuffs like foundation via composer.
But the angular is not defined. Is there anything I am missing? The foundation , jquery etc loads without any trouble.
I tried to edit the require.config.js of the require.config.js , but it is always over written when a composer update is made.
Thank you

@harikt Did you get it working?

That issue is not relevant any more.

@harikt What solution did you end up going with?

I had the same problem. In my local machine, it was working, but when cloning into server it was not downloading. My solution was to delete the folder vendor/components/angular.js/  and then running composer install / update again.


Replace tinyxml and libxml2 with pugixml

At the request of @snomos, I have updated the XML handling to work on Debian with upstream packages, and pugixml was found to be the best fit for this purpose as it's small, easy to read API, great documentation and Just Works™ :smile:
This builds and runs on Debian (stable, testing, unstable), macOS (with MacPorts or Homebrew) and should probably build fine on Windows though I have no system with MinGW to test on at this moment.

it doesn't seem to work on travis yet?

Yes, I am looking into it.


TypeError: Cannot read property 'empty' of undefined

From https://ticino-errors.azurewebsites.net/Errors?bucketIdHash=76782e1c-306d-a7ba-4b77-09619c96442f
TypeError: Cannot read property 'empty' of undefined
/vs/workbench/browser/parts/compositebar/compositeBarActions.ts#213:21 (updateBadge)
/vs/workbench/browser/parts/compositebar/compositeBarActions.ts#277:8 (call)
/vs/base/common/event.ts#144:18 (fire)
/vs/workbench/browser/parts/compositebar/compositeBarActions.ts#96:25 (setBadge)
/vs/workbench/browser/parts/compositebar/compositeBar.ts#186:10 (updateActivity)
/vs/workbench/browser/parts/compositebar/compositeBar.ts#146:7 (showActivity)
/vs/workbench/browser/parts/activitybar/activitybarPart.ts#100:28 (showActivity)
/vs/workbench/services/activity/browser/activityService.ts#29:30 (showActivity)
/vs/workbench/services/progress/browser/progressService2.ts#161:36

Not exactly sure when this can happen - looking that it only happens in 1.21 I can only assume it is related to the search to the panel change.
It seems that the activity service is trying to show progress for a composite which does not exist.
For now I could only add a null guard to not explode and silently not report any progress when trying to show progress for an unavailable composite.


Latest Interchaintest updates

summary
This updates release/v1.x.x to the latest interchaintest/v7. This is needed for Juno since the math.Int is used for balances instead of Int64()
It also fixes a SDK import in the app, and fixes the go.work file

oh turns out there is a 0.2.1 patch smh


External Status - Modal and confirmation banner

As an analyst
I want to give a reason for changing the external status
So that I can document for audit purposes and internal communication purposes
Description:
There is a modal to provide a reason for the change when the internal status is changed but there isn't one for the external status.  This card is to add the modal for when changed.
Acceptance Criteria:

[ ] Reason for change modal appears when changing the external status - same design and behaviour as the internal status

[wireframe 1]

[ ] Acceptance Criteria

[wireframe 2]

[ ] Acceptance Criteria

Implementation Details

Hey team! Please add your planning poker estimate with Zenhub @AntBush @marcellmueller @rafasdc @VB-at-Bis


Add email activation feature into signup

We have to insert this feature into signup page as soon as possible. So, we can ask our questions to backend team when encountering problem.

Please check #132

Done.


Implement analytic Jacobian for CartesianToElevationBearingRangeRate.

Implemented an analytic expression for the Jacobian of CartesianToElevationBearingRangeRate. This is a more-accurate calculation than the baseline numerical Jacobian calculation. Also, on my system, this sped up the calculation from 500 usec to 100 usec.

The comparison between the current numerically calculated Jacobian and the new analytic Jacobian, assert np.allclose(jac, jac0, atol=5e-6, rtol=1e-5) passed on my system, but I different systems will have different numerical errors. So, I reduced to assert np.allclose(jac, jac0, atol=5e-4, rtol=1e-5). The current Jacobian isn't a "truth" value, but we'd expect it to be close to the new value.


NuGet Gallery not detecting license type

NuGet Gallery is not detecting the license for Json.NET
https://www.nuget.org/packages/Newtonsoft.Json/
Is this a bug? Also I think it would be a good idea to have a couple of sentences somewhere in your documentation explaining how to get the license detected.

We are tracking this issue with #2396
Closing this one.


[terra-date-picker] Fixed crash issue for upper and lower bound dates in IE

Summary
Fixed crash issue for upper and lower bound dates in IE.
Closes #1405
Deployment Link

https://terra-framework-deployed-pr-#.herokuapp.com/
Testing

Additional Details

Thank you for contributing to Terra.
@cerner/terra

Should we add a test step around here to test clicking the Previous/Next buttons to get to January 1900 and December 2100 even though we don't run tests in IE?

@saket2403 @chrismichalewicz Does this need functional verification? If it does not, is there anything else we need before merging?

Oops, I accidentally clicked on the wrong button and closed it.

@saket2403 @chrismichalewicz Does this need functional verification? If it does not, is there anything else we need before merging?

This is ready to merge


Fix screenshot taking and screen recording in AR

Screenshot taking wasn't working due to a react "this" issue. In JavaScript, class methods are not bound to the instance like an arrow function is. So, when a user of ViroARSceneNavigator tries to use these functions, the "this" instance didn't have all of the React properties that make React Native's findNodeHandle work correctly.
Changing functions like:
async _takeScreenshot(fileName, saveToCameraRoll) {
  // ...
}

To
_takeScreenshot = (filename, saveToCameraRoll) => {
  // ...
}

Fixes the issue and allows "this" to be properly accessed by findNodeHandle()
Also adds more documentation to the ViroARSceneNavigator.

TODO:

[ ] Update documentation
[ ] Link GitHub issues that are closed by this PR
[ ] Test with community
[ ] Update version number to 2.23.2


Backend mysql colum error

hello,i have a error
when i run orchestrator,error messages is:
ERROR Error 1264: Out of range value for column 'uptime' at row 1
proxysql version：2.0.6
i runing tihs statement Problem Solving：
alter table database_instance modify column uptime text;
mysql> show global status like '%uptime%';
+---------------------------+----------------------+
| Variable_name             | Value                |
+---------------------------+----------------------+
| Uptime                    |<PHONE_NUMBER>3706509722 |
| Uptime_since_flush_status |<PHONE_NUMBER>3706509722 |
+---------------------------+----------------------+
2 rows in set (0.11 sec)

What is the Uptime value you see in your table after the fix?
Also, proxysql version is unrelated to this issue, right?

修复后您在表中看到的Uptime值是多少？
此外，proxysql版本与此问题无关，对吧？

mysql> select uptime from database_instance;
+----------+
| uptime   |
+----------+
| -2976072 |
| 144835   |
+----------+
2 rows in set (0.00 sec)

What is the Uptime value you see in your table after the fix?
Also, proxysql version is unrelated to this issue, right?

mysql> select uptime from database_instance;
+----------+
| uptime |
+----------+
| -2976072 |
| 144835 |
+----------+
2 rows in set (0.00 sec)

what does show global status like 'uptime'; show on the relevant mysql server?

show global status like 'uptime';在相关的mysql服务器上显示什么？

what does show global status like 'uptime'; show on the relevant mysql server?

what does show global status like 'uptime'; show on the relevant mysql server?

mysql> show global status like 'uptime';
+---------------+----------------------+
| Variable_name | Value                |
+---------------+----------------------+
| Uptime        |<PHONE_NUMBER>3706751416 |
+---------------+----------------------+
1 row in set (0.07 sec)
[root@risk-master ~]# uptime
09:35:00 up 36 days, 23:02,  1 user,  load average: 0.00, 0.01, 0.05

@baijiu1 there you have it. This is an impossible value for uptime (at least -- should be impossible!)
I'll leave it to you to investigate how that value came to be.
Please note this is peculiar: you value is almost the maximum for BIGINT UNSIGNED,<PHONE_NUMBER>3709551615.
orchestrator will not adapt to meet this value.


Unify TagFilter for Streaming scenario

This PR refactors TagFilter interface for better performance and replace the incomplete filter implementation in the TopN aggregation.
The new TagFilter fully takes advantage of parsed schema and improves O(N) match to O(1).
Closes https://github.com/apache/skywalking/issues/9770

Codecov Report

Merging #239 (415342c) into main (1c19243) will increase coverage by 0.81%.
The diff coverage is 49.09%.

@@            Coverage Diff             @@
##             main     #239      +/-   ##
==========================================
+ Coverage   45.23%   46.04%   +0.81%
==========================================
  Files          87       87
  Lines        8879     8793      -86
==========================================
+ Hits         4016     4049      +33
+ Misses       4484     4364     -120
- Partials      379      380       +1

Impacted Files
Coverage Δ

banyand/measure/measure_topn.go
30.06% <0.00%> (+6.67%)
:arrow_up:

pkg/query/logical/measure/measure_analyzer.go
0.00% <ø> (ø)

.../query/logical/measure/measure_plan_aggregation.go
0.00% <0.00%> (ø)

pkg/query/logical/measure/measure_plan_top.go
0.00% <0.00%> (ø)

banyand/measure/schema.go
12.06% <11.76%> (ø)

banyand/measure/measure.go
86.07% <89.28%> (+5.30%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

I've reverted changes made to the BuildSchema() in the logical/measure package, but extracted the underlying TagSpecRegistry to allow simply using the fine-grained component. This helps overcome the cyclic import issue without breaking the current design.
Further, I've polished the write part by sharing the measure write method among different cases,

write real measure entities,
write virtual measure entities, i.e. FlowRecord generated by TopNAggregation, by transforming to a DataPointForWrite entity.

The latter would help further optimization, e.g. fully separate topN to another package. But this required much work to be done, for example, the current Repository is high coupled with a so-called ResourceSupplier which is unexpected in the original design.
So I think this PR is sufficient to resolve the current issue. We could stop here.

I've refactored the wring path of TopN Aggregation results by creating new internal writing request to the pipeline. And every TopN schema is now bounded to a real Measure schema which is used to listen and write TopN entities.
The virtual/real measure concepts are still there since the measure of TopN is incomplete.


Lean.Meta.getConst? cannot extract any info from theorem

Description
Zulip chat reference
/-
Bug description

[Zulip chat reference](https://leanprover.zulipchat.com/#narrow/stream/270676-lean4/topic/.23widget.20questions.20about.20RPC.20method.20demo)
-/

import Mathlib.Tactic

open Lean

def a_is_zero (a : ℕ) : Prop := a * 1 = 0

theorem addition_comm (a b : ℕ) : a + b = b + a := add_comm a b

/-
(some (Nat -> Prop))
-/
#eval do
  let ci ← Meta.getConst? `a_is_zero
  IO.println s!"{ci.map ConstantInfo.type}"

/-
none
-/
#eval do
  let ci ← Meta.getConst? `addition_comm
  IO.println s!"{ci.map ConstantInfo.type}"

/-
lean4/src/Lean/Meta/GetConst.lean

def getConst? (constName : Name) : MetaM (Option ConstantInfo) := do
  match (← getEnv).find? constName with
  | some (info@(.thmInfo _))  => getTheoremInfo info
  | some (info@(.defnInfo _)) => if (← canUnfold info) then return info else return none
  | some info                 => return some info
  | none                      => throwUnknownConstant constName
-/

/-
lean4/src/Lean/Meta/Basic.lean

def getTheoremInfo (info : ConstantInfo) : MetaM (Option ConstantInfo) := do
  if (← shouldReduceAll) then
    return some info
  else
    return none
-/

Versions
leanprover/lean4:nightly-2023-06-20

Please use the provided template (click New Issue to see it again). It's important that bug reports actually have the
Expected behavior: [What you expect to happen]
Actual behavior: [What actually happens]
sections, with human readable text, for clarity. I can work out what's going on here, but you could make it much easier!

My apologies, you're using the wrong part of the API. The public facing function here is Lean.getConstInfo, which behaves as expected:
import Mathlib.Data.Nat.Basic

open Lean

def a_is_zero (a : ℕ) : Prop := a * 1 = 0

theorem addition_comm (a b : ℕ) : a + b = b + a := add_comm a b

open Lean Elab Meta

/--
info: Nat -> Prop
-/
#guard_msgs in
#eval show CoreM _ from do
  let ci ← getConstInfo `a_is_zero
  IO.println s!"{ci.type}"

/--
info: forall (a : Nat) (b : Nat), Eq.{1} Nat (HAdd.hAdd.{0, 0, 0} Nat Nat Nat (instHAdd.{0} Nat instAddNat) a b) (HAdd.hAdd.{0, 0, 0} Nat Nat Nat (instHAdd.{0} Nat instAddNat) b a)
-/
#guard_msgs in
#eval show CoreM _ from do
  let ci ← getConstInfo `addition_comm
  IO.println s!"{ci.type}"

The documentation could be clearer, here.


HLS Event Playlist: Getting QUOTA_EXCEEDED_ERROR when seek to a different position

Have you read the FAQ and checked for duplicate open issues?
YES
What version of Shaka Player are you using?
2.5.4
Can you reproduce the issue with our latest release version?
YES
Can you reproduce the issue with the latest code from master?
YES
Are you using the demo app or your own custom app?
Tried both
If custom app, can you reproduce the issue using our demo app?
YES
What browser and OS are you using?
Chrome 76 MacOS 10.14, But reproducible in other platforms as well
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
What are the manifest and license server URIs?

Unfortunately, I can't share this stream publicly :(
Note: Stream is working fine in other players.
What did you do?

Tried playing an HLS event playlist, and seeked backward to a different position.
What did you expect to happen?
The content should play.
What actually happened?

Shaka kept downloading and appending segments to the buffer, eventually got a QUOTA_EXCEEDED_ERROR.
I tried debugging the issue. Few observations,

The source buffer is not triggering any error on appendBuffer
bufferedAhead and SourceBuffer.buffered remained 0 hence the streaming engine kept requesting for new segments.
If I update child manifest with #EXT-X-PLAYLIST-TYPE:VOD, it'll work fine
handleQuotaExceeded_ method in streaming_engine is working as expected

@shaka-bot reopen

I've uploaded a test stream https://thecuriousdev.github.io/trailer/master.m3u8 please have a look
@shaka-bot reopen

I've attached a screen recording of the issue as well,
shaka-player-issue-edited.mp4.zip

I am also facing the exact same issue. Is there any resolution for this?

Looking at your example manifest, it seems that StreamingEngine is trying to buffer all the way to the live head, no matter where you tell it to seek to. So you're getting a QUOTA_EXCEEDED_ERROR  when you seek back far enough that it tries to over-fill the buffer.
Not sure why yet. I'll need to look into this more.

It looks like that's happening because, for event playlists, when you perform an unbuffered seek, we are not re-loading the initialization segment.
Specifically, we get the initialization segment from the EXT-X-MAP tag. If there is no EXT-X-MAP tag, we assume that there is no initialization segment.
Reading up about event playlists, segments cannot be removed from them, so presumably it's safe to use the first segment as an initialization segment. Like, there won't be a rolling window, such that the first segment will drop out eventually.
So I think this is probably safe to classify as a bug, anyway? I'll have a CL out for review for this soon, ideally. Sorry for the wait!

I did not see any update on this ticket. When can we expect v2.6 of shaka to be released?

For a discussion of v2.6 release date, see: https://github.com/google/shaka-player/issues/2208#issuecomment-548474623
Please note, however, that this issue is a bug, and a fix for it would be eligible for cherry-pick to v2.5.x .  So you don't necessarily have to wait for v2.6.  It really just depends on how soon we can determine the cause and fix it.

After much investigation, it is looking like this is a problem with mux.js, the tool that we use to turn ts content into mp4 content for platforms that do not support ts. For whatever reason, if you perform an unbuffered seek backwards with multiplexed ts content, the resulting mp4 outputs will start having empty audio tracks. This causes MediaSource to not register the output as being within a buffered range, and thus we keep buffering further and further ahead until we go past our quota.
This also means that, if you perform a very short unbuffered seek, such that it doesn't go over the quota, it will successfully start playing again, but without audio.
I have filed an issue for this on the github page for mux.js: https://github.com/videojs/mux.js/issues/312
You can track the progress of that bug there.
In the meantime, we can theoretically fix this by tearing down and re-creating the transmuxer between each operation. That seems like a very inefficient solution, however, so I'm not sure if it would be a good idea to implement.

Closing this stale external (non-Shaka) issue. If you disagree, please reply with @shaka-bot reopen, and it will be automatically reopened.
Also, I'm reasonably sure this was fixed in today's 5.5.3 release of mux.js.


Always add instance delete finalizer initially

What this PR does / why we need it:
To be sure we don't orphan instances
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #581
Special notes for your reviewer:
none

/assign @nikhita

        helper.go:151: verify failed due to error=failed to create machine migrateuid-gce-1145995029450330113: An error of type = InvalidConfiguration, with message = Failed to insert instance: googleapi: Error 403: Quota 'IN_USE_ADDRESSES' exceeded. Limit: 30.0 in region europe-west3., quotaExceeded occurred

:eyes: :thinking:

/retest

/retest


Remove links as properties

Coverage increased (+0.09%) to 93.802% when pulling f555c5651637317259f269dba555e6879c00bfdd on remove-links-as-properties into 9fe8aa80637775ba148b78878717188518f8ec5b on add-sqlachemy-schema-generation.


Cannot use library successfully

I tried to use this library like the example, but some errors were reported

Hi @Lee-42 do you have a public project that I can use to reproduce it? Also, which Vue version are you using, please?
I tested the yarn run serve which starts a small app that imports the library, and it worked. I am now using the Vue CLI to create a Vue 2 app and try to import it.
-Bruno

Never mind @Lee-42 , successfully reproduced the issue here. Let me see where I messed up with the build system since the previous releases.
vue create test-lumino
cd test-lumino
yarn install
yarn add @tupilabs/vue-lumino

Applied diff on README.md file, and got the error.

Fixed in 1.1.3.
@Lee-42 just released 1.1.3. You made me realize I had the wrong command in the release Wiki page. I used the correct command in previous releases, but somewhere I forgot it and copied/pasted the one from that Wiki and released an unusable version.
Hopefully next version works OK for you. Thanks!
-Bruno

Dependabot found some pending updates, I will release 1.1.4 as well, with these new dependencies, but shouldn't matter whether you have 1.1.3 or 1.1.4, both versions should work fine for you :+1:


[WIP] Add historical balance lookup

Fixes # .
Motivation

Solution

Open questions

Pull Request Test Coverage Report for Build 569

22 of 22 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.4%) to 89.855%

Totals

Change from base Build 562:
0.4%

Covered Lines:
434

Relevant Lines:
483

💛  - Coveralls


add support for blinds

Added support for roller blinds (e.g. FYRTUR) and basic tests.

Tested the code on my Dirigera Hub + Fyrtur blinds and the code appears to function properly.


Dart Error: error: import of dart:mirrors is not supported in the current Dart runtime

I get this error when trying to use this library in flutter.
flutter --version:
Flutter 1.17.1 • channel stable • https://github.com/flutter/flutter.git
Framework • revision f7a6a7906b (2 weeks ago) • 2020-05-12 18:39:00 -0700
Engine • revision 6bc433c6b6
Tools • Dart 2.8.2

I am having the same issue, any help is much appreciated.

reflectable package maybe alternative
https://pub.dev/packages/reflectable/example

Hi, I faced on the same issue. Currently, the only way I found to solve this issue is to remove references to reflection with some minor change. My version of the code is available at https://github.com/ostafen/irc.dart, under the "flutter" branch.


Improve the documentation in relation to the code of the different projects

[ ] https://github.com/koaning/mktestdocs
[ ] https://github.com/manuzhang/mkdocs-htmlproofer-plugin
[ ] https://github.com/mkdocs/mkdocs-redirects
[ ] https://github.com/mkdocstrings/mkdocstrings

@Antonyjin has work in progress regarding [mktestdocs](https://github.com/koaning/mktestdocs)


improve require docs

describe critical dependency warning

there was a section about critical dependency in archived docs about warning like:
Critical dependencies:
158:18-25 require function is used in a way in which dependencies cannot be statically extracted

will be great to add this in current docs too. not sure where place this better...
<!-- Name of the feature(s) and a link to related pull request of the feature implementat

- [ ] Read and sign the [CLA][1]. PRs that haven't signed it won't be accepted.
- [ ] Make sure your PR complies with the [writer's guide][2].
- [ ] Review the diff carefully as sometimes this can reveal issues.
- [ ] Do not abandon your Pull Request: [Stale Pull Requests][3].
- **Remove these instructions from your PR as they are for your eyes only.**

[1]: https://github.com/openjs-foundation/EasyCLA#openjs-foundation-cla
[2]: https://webpack.js.org/contribute/writers-guide/
[3]: https://webpack.js.org/contribute/#pull-requests

title is misleading since this warning related to all require functions

Then maybe try https://webpack.js.org/api/module-methods/#commonjs section if it's require specific?

technically this is part of commonjs section maybe we need a subtitle for this?

I have added title


Docs request: example setup.cfg

From https://github.com/wemake-services/flake8-eradicate/issues/69 it looks like config files are supported.
Can you document how to add a setup.cfg entry for flake8-eradicate in the README.md?  Specifically how to whitelist with eradicate-whitelist-extend.

--eradicate-whitelist-extend to extend the whitelist from eradicate (# separated list)

Also, what is a # separated list?

For example, I need to whitelist this line:
# Formula: (counts/distance) = (counts/step) (steps/turns) (turns/distance)

+1
This is not immediately clear


Looking for advice: Would like to know to to set nested graph with it's own Scaffold + shared viewmodel

I'm developing a Jetpack Compose app with a navigation structure that includes a main home screen and a multi-step "Create Group" flow. To ensure UI consistency and manage shared state efficiently, my aim is to implement a shared Scaffold and ViewModel for all screens within each navigation graph. However, I'm encountering challenges with the best approach to structure this using Jetpack Compose Navigation, especially considering the potential use of multiple NavHosts and its implications for deep linking.
note: I want to avoid using NavHost for each nested graph, but, should I?
Primary Goals:
Maintain a consistent UI (e.g., TopAppBar) across all screens within the "Create Group" flow without redefining the Scaffold in each composable. Share a ViewModel across these screens to handle state and data effectively. Concerns and Questions:
Shared Scaffold Implementation: What's the recommended practice for sharing a Scaffold across multiple screens within a nested graph in Jetpack Compose Navigation? Should each screen in the flow share the same Scaffold instance, and if so, how is this best achieved?
ViewModel Sharing: How can a ViewModel be shared effectively across all composables within a specific nested graph (like the "Create Group" flow) for cohesive state and data management?
Multiple NavHosts Consideration: In aiming for the above setup, could employing multiple NavHosts be a solution or would it complicate the architecture unnecessarily? Specifically, how might using multiple NavHosts affect deep linking across the app? Is there a risk of complicating deep link implementation or handling with multiple NavHosts, and if so, how can this be mitigated?
Deep Linking Concerns: Given the structured navigation, are there specific challenges or best practices to consider for implementing deep linking effectively in a setup with shared Scaffold and ViewModel across nested graphs or multiple NavHosts?
I am looking for insights into structuring navigation and shared UI/state management efficiently in a scalable Jetpack Compose application, particularly in regard to the use of nested graphs/ multiple NavHosts, and ensuring deep linking remains robust.
What about using DestinationWrapper?
Any examples, advice on best practices, or pointers to resources would be greatly appreciated:)

Hi.
I'm sorry If I don't go too deep in my suggestions, time is short these days :P
What I would do:

Single DestinationsNavHost and single Scaffold. Have logic around those to show / hide components of the Scaffold based on the current destination visible on screen. (you can check the sample of this repo for an example.. but it's really just if(currentDestination != .... or if (currentDestination in listOf() or if(SomeNavGraph.contains(currentDestination).

Have nested graphs for each flow, and create a VM tied to that nested graph. The same instance will be available and used by all destinations of that graph. (https://composedestinations.rafaelcosta.xyz/v2/common-use-cases/providing-viewmodels#share-viewmodels-between-multiple-destinations)

DestinationWrapper

Probably unrelated to your questions.


Add support for base dilation and window dilation to reduce window op…

…erators.
Refactor reduce-window tests to use many generated cases instead of a single large test case with a loop.
Treat inf - inf as a zero difference in gradient tests.
Fixes #3793

hey @hawkinsp . i just wonder what is the application scenario of dilation in reduce window. Is the dilation here similar to convolution dilation?


[Crates] Amount of Masterballs you get from Solar crate are less than displayed

Describe the bug
Masterballs displayed are lesser than the amount you get
To Reproduce
Steps to reproduce the behavior:

Go to /warp crates
Click on Solar Crate
Hover over 5 masterballs
See error

Expected behavior
Expected to show 3 masterballs
Screenshots

**Username:**TheKeyblade
Server name (all applicable): All

GUI now reflects correct amount, closing


sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) (1044, "Access denied for user 'microblog'@'%' to database 'microblog'") (Background on this error at: http://sqlalche.me/e/e3q8)

I deploy it use docker follow you， this problem I have no idea

The error suggests that the database user for the microblog app is not set up correctly in your database.
Did you create the database container earlier or at about the same time? If the database was just created, it can take a few seconds for it to fully complete its own initialization, so the microblog container may error trying to access the database. For that reason I have implemented the retries every 5 seconds. If this does not succeed after a few retries, then you need to review the database container, in particular the configuration for the microblog user.

@miguelgrinberg
Thanks so much! It’s problem exactly you say that name of the database  does not match.
I benefit a lot from your blog tutorial ,it’s really great. thank you for much again.


Add csv.Table.Write and csv.Table.SaveToFile

It's probably a good time to start using https://github.com/gocarina/gocsv.


v7.0.0

What does this PR do?

Update dependencies
Set v7.0.0

How should it be tested manually?
yarn test
# or
npm test

Pull Request Test Coverage Report for Build 128

42 of 42 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 117:
0.0%

Covered Lines:
355

Relevant Lines:
355

💛  - Coveralls


Add firebase adapter for sveltekit

What's the difference between this package and the existing https://github.com/jthegedus/svelte-adapter-firebase package?

What's the difference between this package and the existing https://github.com/jthegedus/svelte-adapter-firebase package?

The adapter you linked is not compatible with the current version of SvelteKit. Also it requires more configuration effort and is harder to set up.


Feature/auth method insight

This PR addresses the output being changed from N/A to null to accurately show the state of the object as well as a bugfix for returning a null AuthPolicy object when requirement is not set to types or amount and no geolocations are set.

I updated the ExampleCli output to better print the N/A or null based on your feedback.


Create multiple cloud scheduler to call the same function

Hello,
I am working on a simple use case : I have a cloud function that accepts a 'URl' parameter, calls that URl (which is a public API endpoint) and saves the data in a JSON file stored in Cloud Storage. I want to be able to set multiple cloud scheduler to call different endpoints on different schedules, but I only need 1 function.
Question : My guess is that @app.schedule('5 * * * *') creates both a Cloud Scheduler and a Cloud Function. Is there a possibility to only create a (or multiple) Cloud Scheduler and define parameters to use in the call to the Cloud Function ?

You are correct that the @app.schedule('5 * * * *') will create both the cloud function and the cloud scheduler. If you would like multiple schedules for the same function then you simply add additional decorators. having multiple schedules and multiple functions will still only create one http cloudfunction.
@app.schedule('5 * * * *')
@app.schedule('2 * * * *')
def scheduled_function(app.request)
...

@app.schedule('3 * * * *')
def scheduled_function2(app.request)
...

Right now app.scheduler doesn't take in any additional parameters, but it looks like a Scheduler Job http_target  supports a body, method, and additional headers, so will work on a pr this week to support that.

Thank you for your promptness, can't wait to try this feature !!

@amirbtb take a look at the latest release 0.5.0 and see if that solves your use case.

Hello, thank you for this feature it looks perfect on the paper. I will try it tomorrow and keep you updated.

I used the body argument of @app.schedule() in order to POST  a dict to the cloud function. I managed to encode my dict into a base64 string but the process is tedious :
I give base64.b64encode(json.dumps({"key":"value"}).encode('utf-8')).decode('ascii') to the body argument, then in my function in order to convert the base64 string into a python dict I use json.loads(base64.b64decode(raw_payload).decode('utf-8')).
Nonetheless, the Cloud Scheduler is created and it is working fine ! 🥳
I noticed the Cloud Scheduler had some parameters, like name description timeZone retryConfig and  attemptDeadline set  to default values by Goblet but they could be useful. Do you want me to create an issue for this ?

thats good to hear! Unfortunately i am not able to make the body any simpler since it is gcp that requires a base66 encoded string.
in terms of the additional configs, description and timeZone are already available.
name is generated by goblet right now since it needs to be unique and is based on the cloud function name as well as the function name it is decorated, so I am not sure if I want that to be configurabe.
I can certainly add overrides for retryConfig and attemptDeadline if you don't mind making another issue for those.

thats good to hear! Unfortunately i am not able to make the body any simpler since it is gcp that requires a base66 encoded string.

I understand. Maybe you want to add instructions about how to encode and decode using the body argument.

in terms of the additional configs, description and timeZone are already available.

Perfect, I'm gonna use them right away !

name is generated by goblet right now since it needs to be unique and is based on the cloud function name as well as the function name it is decorated, so I am not sure if I want that to be configurabe.

Using app.scheduler() multiple times for the same function creates multiple elements with similar names, it can be an issue. In the mean time, we can still use description in order to differentiate them.

I can certainly add overrides for retryConfig and attemptDeadline if you don't mind making another issue for those.
On it. Thank you again for your reactivity !


config/adldap_auth.php file not found

Laravel Version: 5.4
Adldap2-Laravel Version: ^4.0
PHP Version: 7.1
LDAP Type:  OpenLDAP

install
config/app.php file ... updated
Publish the auth configuration .. ok
config/auth.php configuration file ... updated
after installation:
BASIC SETUP
Inside your config/adldap_auth.php file there is a configuration option named usernames.
this file not found under config directory  !!
where is the problem?
How do we solve the problem?

Hi @asaadhoussam,
Since you're using Laravel 5.4, then you'll need to insert the Adldap\Laravel\AdldapAuthServiceProvider::class as well inside your config/app.php file to be able to publish the adldap_auth.php file.

Hello Steve
Thanks for your prompt reply my friend and for helping you to me
I wish you success always
On Wed, Apr 11, 2018 at 12:13 AM, Steve Bauman<EMAIL_ADDRESS>wrote:

Closed #518 https://github.com/Adldap2/Adldap2-Laravel/issues/518.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Adldap2/Adldap2-Laravel/issues/518#event-1567197924,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AO_9suRR_H-civr9Akb0pc_Sld7AYujHks5tnSB_gaJpZM4TLHZq
.

--
حسام أسعد

Hi Steve,
I want to make an update on laravel 5.5 auth, I want to allows users to access to my application and make authenticate with a openLDAP server
I work on windows and use composer with this require:
"require": {
"php": ">=7.0.0",
"adldap2/adldap2-laravel": "^4.0",
"fideloper/proxy": "~3.3",
"laravel/framework": "5.5.*",
"laravel/tinker": "~1.0"
}
1- update migration like this:
public function up()
{
Schema::create('users', function (Blueprint $table) {
$table->increments('id');
$table->string('name');
$table->string('ldap_username')->unique( );
$table->string('email')->unique();
$table->string('password');
$table->datetime('deleted_at')->nullable();
$table->rememberToken();
$table->timestamps();
});
}
2- Configure my LDAP settings in .env and /config/adldap.php files:
'schema' => Adldap\Schemas\OpenLDAP::class,
ADLDAP_CONTROLLERS="ldap.example.com"
ADLDAP_BASEDN="ou=staff,dc=example,dc=com"
ADLDAP_ADMIN_USERNAME="admin"
ADLDAP_ADMIN_PASSWORD="password"
3- update Illuminate\Foundation\Auth\AuthenticatesUsers file to use the ldap username instead of email address to login like this:
public function username( ) {
    return ‘ldap_username’;
}

4- update login view file to use uid and username like this:

5- Result:  nothing, No Login, No Error Message .. Only the login page appears again
The attempt did not succeed, LDAP integration and managing to authenticate users against it failed
Let me know where the error is / missing / modified/...?
thanks to your help


JWT Access Token Validation

Due to the way JWT access token verification is performed, an ID token can be passed into a secured endpoint as an access token and it is accepted.
Relevant code: https://github.com/anvilresearch/connect/blob/master/models/AccessToken.js#L259
Some possible solutions:

Add a claim to tokens indicating they are access tokens and validate that (variation on this is to use the presence or lack of certain claims to indicate an access token...)

Use a different signing token for access tokens and require it to be from that list

Even if (2) were done, I would recommend doing (1) also so that 3rd party applications can tell with certainty what the token is.
I'm sure some other solutions can be imagined

@msamblanet this is a great catch. Thanks!


Sometimes the question doesn't format well.

I'm using ollama -> gemma:2b with snowflake as the embedding model.


Consensus components implementation

[x] cw_rating_calculator (#142)
[x] entry_point_selector (#180)
[x] ledger_validator (#181)
[x] milestone_tracker (#214)
[x] snapshot (#280)
[x] tangle (#142)
[x] transaction_validator (#144)
[x] walker (#178)
[x] walker_validator (#179)
[x] bundle validator (#231)

done


allow => in objects in return types of arrow functions

Summary:
To avoid ambiguity, Flow disallows using a function type in the return type, like
const f = (): boolean => string => { return (b: boolean): string => "hello"; }
unless you wrap it in parens
const f = (): (boolean => string) => { return (b: boolean): string => "hello"; }
We forgot to allow it inside objects too, like
const f = (): { x: boolean => string } => { return { x: (b: boolean): string => "hello" }; }
Differential Revision: D18187492

Not a 'function type in object type' situation, but similar:
const f = (): ([boolean => string]) => { return [(b: boolean): string => "hello"]; }

This code breaks if I remove the parens from the return type. Is this expected? If not, is this the same bug or a different one?


model->toArray() add timezone to dates

Winter CMS Build
1.2
PHP Version
8.0
Database engine
MySQL/MariaDB
Plugins installed
No response
Issue description
When fetching model's attributes, the dates fields are corrects, but when calling toArray() method on the same model, date fields comes with timezone in ISO format.
If you add to pass this to the winter/src/Argon/Argon.php@createFromFormatWithCurrentLocale() method it result in an Carbon issue :
Carbon\Exceptions\InvalidFormatException with message 'Unexpected data found.
Trailing data'

Steps to replicate
In winter 1.2.1
$ php artisan winter:version
*** Detecting Winter CMS build...
*** Detected a modified version of Winter CMS build 1.2.1.

$ php artisan tinker
>>> $access = Backend\Models\AccessLog::first();
=> Backend\Models\AccessLog {#4383
     id: 1,
     user_id: 1,
     ip_address: "xxx.xxx.xxx.xxx",
     created_at: "2021-04-26 13:44:06",
     updated_at: "2021-04-26 13:44:06",
   }

>>> $access->attributes['created_at'];
=> "2021-04-26 13:44:06"

>>> $access->toArray()['created_at'];
=> "2021-04-26T13:44:06.000000Z"

>>> $attribut = $access->attributes['created_at'];
=> "2021-04-26 13:44:06"

>>> \Winter\Storm\Argon\Argon::createFromFormatWithCurrentLocale('Y-m-d H:i:s', $attribut);
=> Winter\Storm\Argon\Argon @1619444646 {#4351
     date: 2021-04-26 13:44:06.0 e (+00:00),
   }

>>>
>>> $array_attribut = $access->toArray()['created_at'];
=> "2021-04-26T13:44:06.000000Z"

>>> \Winter\Storm\Argon\Argon::createFromFormatWithCurrentLocale('Y-m-d H:i:s', $array_attribut);
Carbon\Exceptions\InvalidFormatException with message 'Unexpected data found.
Trailing data'

In winter 1.1.9
$ php artisan winter:version
*** Detecting Winter CMS build...
*** Detected a modified version of Winter CMS build 1.1.9.

$ php artisan tinker
Psy Shell v0.11.8 (PHP 8.0.20 — cli) by Justin Hileman
>>> $access = Backend\Models\AccessLog::first();
=> Backend\Models\AccessLog {#4079
     id: 1,
     user_id: 1,
     ip_address: "xxx.xxx.xxx.xxx",
     created_at: "2018-08-28 14:24:35",
     updated_at: "2018-08-28 14:24:35",
   }

>>> $access->attributes['created_at'];
=> "2018-08-28 14:24:35"

>>> $access->toArray()['created_at'];
=> "2018-08-28 14:24:35"

>>>
>>>
>>> $attribut = $access->attributes['created_at'];
=> "2018-08-28 14:24:35"

>>> \Winter\Storm\Argon\Argon::createFromFormatWithCurrentLocale('Y-m-d H:i:s', $attribut);
=> Winter\Storm\Argon\Argon @1535466275 {#4192
     date: 2018-08-28 14:24:35.0 e (+00:00),
   }

>>>
>>> $array_attribut = $access->toArray()['created_at'];
=> "2018-08-28 14:24:35"

>>> \Winter\Storm\Argon\Argon::createFromFormatWithCurrentLocale('Y-m-d H:i:s', $array_attribut);
=> Winter\Storm\Argon\Argon @1535466275 {#4268
     date: 2018-08-28 14:24:35.0 e (+00:00),
   }

You can quickly test it by tinkering :
$access = Backend\Models\AccessLog::first();
$access->attributes['created_at'];
$access->toArray()['created_at'];

$attribut = $access->attributes['created_at'];
\Winter\Storm\Argon\Argon::createFromFormatWithCurrentLocale('Y-m-d H:i:s', $attribut);

$array_attribut = $access->toArray()['created_at'];
\Winter\Storm\Argon\Argon::createFromFormatWithCurrentLocale('Y-m-d H:i:s', $array_attribut);

Workaround
No response

Maybe related :
https://laravel.com/docs/7.x/upgrade#date-serialization

I don't think this necessarily counts as a bug within Winter, as it's a change introduced by Laravel, unless this is breaking a feature within Winter.

Not noise at all - happy for the report. But yeah, just falls outside the scope of us fixing it, that's all 😄


Unicode characters support

According to Wiki you can use unicode symbols.

+1

+1

:100: :100: :100:

+3

+4

Thanks, and sorry for the delay.


⚠ ClamAV has degraded performance

In e32a93e, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 437 ms

Resolved: ClamAV performance has improved in 34f0e30.


Nested test structures?

Trying to play around with CodeceptJS, having never actually used Mocha or anything similar before.  Mocha's docs seem to indicate that you can set up nested tests using describe() and it().  It looks like Codecept's Feature() and Scenario() are an alternative method to setting up Mocha's Suites.  Is there a similar way to set up nested tests using CodeceptJS?  For example, something vaguely like:
Feature('Test1');

Before((I) => { // or Background
  I.amOnPage('/');
});

Scenario('Interact with the login page ', (I) => {
  Feature("Test 1 - Part 1");

  Scenario("Filling in login form shows consent banner", () => {
    I.see('Username');
    I.dontSee("You are accessing");
    I.fillField("httpd_username", "user1");
    I.fillField("httpd_password", "pw1");
    I.see("You are accessing");
  });

  Feature("Test 1 - Part 2");

  Scenario('Can log in successfully', () => {
    I.see('Username');
    I.fillField("httpd_username", "user1");
    I.fillField("httpd_password", "pw1");
    I.click('Agree and Log In');
    I.wait(1);
    I.dontSee("Username");
  });
});

Right now we don't provide any kind of nesting.
And there is no something like that in nearest plans. One feature per file for now.

Hmm.  That's kind of disappointing, particularly since Mocha does support nesting suites.
Here's my use case.  Right now, with that I.amOnPage('/'); in Before(), Codecept appears to be bringing up a separate browser instance for every test.  That's taking around 15s or so to execute a test.
I'd really like to be able to use a single Webdriver / browser instance for a series of tests.  Beyond that, I'd like to be able to, say, run an initial test verifying that logging in works, then run additional tests after that that require having successfully logged in.
Again, I'm very new to actual automated testing and to Codecept, but that seems like a pretty useful scenario to support.

Here's my use case. Right now, with that I.amOnPage('/'); in Before(), Codecept appears to be bringing up a separate browser instance for every test. That's taking around 15s or so to execute a test.

Thanks for the idea. We will add option to reuse instance of a browser.

Beyond that, I'd like to be able to, say, run an initial test verifying that logging in works, then run additional tests after that that require having successfully logged in.

This concept is somehow harder to implement. As you will  probably have LOTS of tests where user is logged in (and probably in different files) and one test for a login. Probably this will require something like dependency tree for tests.
But in the end, I think that you don't need nested structures for this kind of tests. Yes, mocha support them, but CodeceptJS is about scenario-driven testing so it's better to keep it linear.

Hello markerikson
I had the same issue, I hate waiting for the browser to open and close. What I did was that I created a script that concatenates many files into one and puts all my different file test into a single test all contained in the same Scenario(), this way I can test memory leaks in my app on the browser.
So far it works great. I can share you my script if you want.

Would be nice to see your script. I wonder how much time you're saving doing it this way?

@markerikson That may interest you https://github.com/Codeception/CodeceptJS/pull/167

I think this can be closed as all helpers have restart: false option which can be used to reuse browser session


Unable to change database environment for query development purpose

Expected behavior
In Dev:
profiles.yml: I have profiles.yml target set to dev
models: a random model file with query select current_database()
result: Database_Dev
In QA:
profiles.yml: I have profiles.yml target set to QA
models: a random model file with query select current_database()
result: Database_QA
Actual behavior
In Dev:
profiles.yml: I have profiles.yml target set to dev
models: a random model file with query select current_database()
result: Database_Dev
In QA:
profiles.yml: I have profiles.yml target set to QA
models: a random model file with query select current_database()
result: Database_Dev
Steps To Reproduce
In Dev:
profiles.yml: I have profiles.yml target set to dev
models: a random model file with query select current_database()
result: Database_Dev
In QA:
profiles.yml: I have profiles.yml target set to dev
models: a random model file with query select current_database()
result: Database_Dev
(But if you switch the virtual environment or restart vscode, it picks up right database)
Log output/Screenshots
No response
Operating System
windows 10
dbt version
1.6.0
dbt Adapter
snowflake
dbt Power User version
v0.18.0
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Could you also describe how you change the target?

From slack: by changing the target in profiles.yml

yes, thats right, by changing target value from profiles.yml

hey @mdesmet, experiencing the same bug so I'll share some more meaningful context:
Note: I am using devcontainers
I am authenticating with externalbrowser. I can confirm with dbt debug and dbt build that I can run dbt commands. yet when try out the query results tab it results in the error 251006: Password is empty
{
  "code": -1,
  "message": "Database Error\n  251006: Password is empty",
  "data": "\"Error: Traceback (most recent call last):\\n  File \\\"/usr/local/lib/python3.10/site-packages/dbt/adapters/base/connections.py\\\", line 241, in retry_connection\\n    connection.handle = connect()\\n  File \\\"/usr/local/lib/python3.10/site-packages/dbt/adapters/snowflake/connections.py\\\", line 332, in connect\\n    handle = snowflake.connector.connect(\\n  File \\\"/usr/local/lib/python3.10/site-packages/snowflake/connector/__init__.py\\\", line 54, in Connect\\n    return SnowflakeConnection(**kwargs)\\n  File \\\"/usr/local/lib/python3.10/site-packages/snowflake/connector/connection.py\\\", line 372, in __init__\\n    self.connect(**kwargs)\\n  File \\\"/usr/local/lib/python3.10/site-packages/snowflake/connector/connection.py\\\", line 616, in connect\\n    self.__config(**kwargs)\\n  File \\\"/usr/local/lib/python3.10/site-packages/snowflake/connector/connection.py\\\", line 1051, in __config\\n    Error.errorhandler_wrapper(\\n  File \\\"/usr/local/lib/python3.10/site-packages/snowflake/connector/errors.py\\\", line 290, in errorhandler_wrapper\\n    handed_over = Error.hand_to_other_handler(\\n  File \\\"/usr/local/lib/python3.10/site-packages/snowflake/connector/errors.py\\\", line 348, in hand_to_other_handler\\n    connection.errorhandler(connection, cursor, error_class, error_value)\\n  File \\\"/usr/local/lib/python3.10/site-packages/snowflake/connector/errors.py\\\", line 221, in default_errorhandler\\n    raise error_class(\\nsnowflake.connector.errors.ProgrammingError: 251006: Password is empty\\n\\nDuring handling of the above exception, another exception occurred:\\n\\nTraceback (most recent call last):\\n  File \\\"/root/.vscode-server/extensions/innoverio.vscode-dbt-power-user-0.20.0/dist/node_python_bridge.py\\\", line 104, in <module>\\n    value = eval(_compile(data['code'], '<input>', 'eval'), _locals)\\n  File \\\"<input>\\\", line 1, in <module>\\n  File \\\"/root/.vscode-server/extensions/innoverio.vscode-dbt-power-user-0.20.0/dist/dbt_integration.py\\\", line 434, in execute_sql\\n    *self.adapter_execute(compiled_sql, fetch=True),\\n  File \\\"/root/.vscode-server/extensions/innoverio.vscode-dbt-power-user-0.20.0/dist/dbt_integration.py\\\", line 413, in adapter_execute\\n    return self.adapter.execute(sql, auto_begin, fetch)\\n  File \\\"/usr/local/lib/python3.10/site-packages/dbt/adapters/base/impl.py\\\", line 290, in execute\\n    return self.connections.execute(sql=sql, auto_begin=auto_begin, fetch=fetch, limit=limit)\\n  File \\\"/usr/local/lib/python3.10/site-packages/dbt/adapters/snowflake/connections.py\\\", line 457, in execute\\n    _, cursor = self.add_query(sql, auto_begin)\\n  File \\\"/usr/local/lib/python3.10/site-packages/dbt/adapters/snowflake/connections.py\\\", line 492, in add_query\\n    connection, cursor = self._add_standard_queries(\\n  File \\\"/usr/local/lib/python3.10/site-packages/dbt/adapters/snowflake/connections.py\\\", line 548, in _add_standard_queries\\n    connection, cursor = self.add_standard_query(query, **kwargs)\\n  File \\\"/usr/local/lib/python3.10/site-packages/dbt/adapters/snowflake/connections.py\\\", line 468, in add_standard_query\\n    return super().add_query(self._add_query_comment(sql), **kwargs)\\n  File \\\"/usr/local/lib/python3.10/site-packages/dbt/adapters/sql/connections.py\\\", line 79, in add_query\\n    cursor = connection.handle.cursor()\\n  File \\\"/usr/local/lib/python3.10/site-packages/dbt/contracts/connection.py\\\", line 94, in handle\\n    self._handle.resolve(self)\\n  File \\\"/usr/local/lib/python3.10/site-packages/dbt/contracts/connection.py\\\", line 118, in resolve\\n    return self.opener(connection)\\n  File \\\"/usr/local/lib/python3.10/site-packages/dbt/adapters/snowflake/connections.py\\\", line 368, in open\\n    return cls.retry_connection(\\n  File \\\"/usr/local/lib/python3.10/site-packages/dbt/adapters/base/connections.py\\\", line 271, in retry_connection\\n    raise dbt.exceptions.FailedToConnectError(str(e))\\ndbt.exceptions.FailedToConnectError: Database Error\\n  251006: Password is empty\\n\\n\\tat ChildProcess.onMessage (/root/.vscode-server/extensions/innoverio.vscode-dbt-power-user-0.20.0/dist/extension.js:26181:184)\\n\\tat Object.onceWrapper (node:events:628:26)\\n\\tat ChildProcess.emit (node:events:513:28)\\n\\tat emit (node:internal/child_process:937:14)\\n\\tat process.processTicksAndRejections (node:internal/process/task_queues:83:21)\""
}```

I have also tried out a different target (one with a username and password). Again, confirming i can `dbt build` etc. successfully yet when I try out the query results tab it results in the same error (password missing).

I guess the broader question: **where does query results read the `profiles.yml` from and how does one modify this?** i.e. if i want to run query results with one target and then a different one?


Add upload progress bar

Such as:
https://www.programcreek.com/python/example/106103/requests_toolbelt.MultipartEncoderMonitor
Ideally its nested (e.g. file progress + overall progress)

Closed with #46


Auto/Protolathe should print steel in stacks OR stacks should automatically union upon colliding

Telling auto/protolathe to produce X amount of steel/glass/whatever sheets results in them being dropped out one by one, it takes a lot of time to collect them back. Just make it print out all at once
Reported by @"Herbert Falsevor#3037"

It was done recently, should be closed I guess


Textarea auto resize props

Hello, please add the ability to throw the autoresize prop

Hi, thank you for reporting, hope it works for you,
Greetings,
Tom


isolate only works if isolate is copied into #

To reproduce:
 )ns ns1
 )cs ns1
 )copy isolate isolate
 is←isolate.New''
 is.(2+2)

FUTURE ERROR: 86: COMMUNICATIONS FAILURE 1119  ERR_CLOSED : Socket closed whilst receiving data

This is a duplicate of #1. It is fixed in v19.0 but should be back-ported to the isolate workspace used by 18.2.


allow for credentials when loading

See https://github.com/iterative/dvc/issues/9154
Maybe something like:
zntrack.from_rev(..., **repo_kwargs)

Also support zntrack.get_nodes()


conda or docker ?!

@BioinfoTongLI
Why are there both conda and docker?

theoretically you need to declare all the different containerisations that you want to use there in the process definition.
It is only at runtime you decide which method you want to use.
You can do that by either editing the nextflow.config file
docker.enabled = true
or by adding flags in the CLI -with-docker.
In either of these case, conda will be ommitted.


Large delay between server connect and first read in session reuse case

Noticed increased miss times between our existing production ATS and the 7.1 version.  It looks like a large TS_MILESTONE_SERVER_FIRST_READ-TS_MILESTONE_SERVER_CONNECT time.  And it appears that this is occurring in a server session reuse case.  We are using the global pool.  Will dig into this.  Posting in case other people have also seen this.

Looking into this more closely the delay is between server_sent and server first_read, which is entirely reasonable if the origin is slow or far away.  Will dig into further why the existing production version is behaving differently.  But the session pool does not seem to be the bottle neck, so I am closing this issue for now.


OpenAPI 3.0 Support

Is there any interest in supporting OpenAPI 3.0?

I currently don't have a use case beyond 2.0/swagger, wasn't too happy about openapi 3.0 libraries for some reason (I do forget why), and would not accept a PR adding this functionality. If you're willing and able, I'd suggest you fork and add openapi 3.0 outputs, and then support that fork indefinitely on your own. I could look at implementing it myself and then support it going forward, if you're in a position to sponsor that. Let me know :)


To the Moon and Beyond with Julia | Helge Eichhorn | JuliaCon2021

To the Moon and Beyond with Julia, https://www.youtube.com/watch?v=wDRphj69eh0
It is maybe unreasonable for making timestamps for video that is not even 3 minutes long, but since it shown "Help us add time stamps for this video! See the description for details." on progress bar I did it.
So we either do some timestamp for them or we should just remove current one. In either case, I want to help.
00:00 Welcome!
00:17 Luna Communication And Navigation Service (LCNS)
01:10 Luna Service Volume Simulator (LSVS)
01:32 Julia in LCNS
02:02 Open source packages that we use

Added these, thank you!


[RFC] Image management proposal for hosting sharing and peer pods

Recently there are several proposals about image management for CoCo from the community, such as:

[RFC] Shared Image on Host with Integrity Only for CoCo
[RFC] Proposal for Image Management on CoCo
[RFC] WIP: Proxyless Image-pull on guest proposal for peer pods
Image pulling on the host

This is a refined version of [RFC] Proposal for Image Management on CoCo, aims to cover both host sharing and peer pods.
Scenarios

Confidentiality for manifest/config
Confidentiality for blob data
Solutions

No
No
This proposal

No
Yes
This proposal

Yes
Yes
CRI-proxy or containerd transfer service

Design
The core idea is to simplify the design by using kubelet/containerd Mount.Option field, instead of building new communication channel such as CRI-proxy or - [RFC] WIP: Proxyless Image-pull on guest proposal for peer pods
We add an extraoption field to Mount.Info by existing the existing mechanism from ExtraOption as follow:
// It's very expensive to build direct communication channel for extra information between the nydus snapshotter and
// kata-runtime/kata-agent/image-rs. So an extra mount option is used to pass information from nydus snapshotter to
// those components through containerd.
//
// The `Type` field determines the way to interpret other fields as below:
// Type: "nydus-image-fs"/""
// - Source: path the image meta blob
// - Config: nydusd configuration information
// - Snapshotdir: snapshot data directory
// - Version: RAFS filesystem version
// - Verity: unused
// Type: "nydus-image-block":
// - Source: path to the image meta blob
// - Config: nydusd configuration information
// - Snapshotdir: snapshot data directory
// - Version: unused
// - Verity: data verity information
// Type: "nydus-layer-block":
// - Source: path to the image layer blob
// - Config: nydusd configuration information
// - Snapshotdir: snapshot data directory
// - Version: unused
// - Verity: data verity information
// Type: "raw-image-block":
// - Source: path to the raw block image for the whole container image
// - Config: unsued
// - Snapshotdir: unused
// - Version: unused
// - Verity: data verity information
// Type: "raw-layer-block":
// - Source: path to the raw block image for a specific layer
// - Config: unused
// - Snapshotdir: unused
// - Version: unused
// - Verity: data verity information
// Type: "runtime-agent-pull"
// - Source: unused
// - Config: labels associated with the images, containing all labels from containerd
// - Snapshotdir: unused
// - Version: unused
// - Verity: unused
type ExtraOption struct {
	Type        string `json:"type"`
	Source      string `json:"source"`
	Config      string `json:"config"`
	Snapshotdir string `json:"snapshotdir"`
	Version     string `json:"fs_version"`
	Verity      string `json:"verity"`
}

The overall architecture looks like:

The above architecture works for both Kata and Coco as:

kubelet issue pull image requests to containerd
containerd downloads image manifest/config and then call remote snapshotter to process image layers
remote snapshotter optionally download and prepare data by itself, or relay the task to kata-agent, and return Mount array to  containerd with the ExtraOption field.
containerd call kata-runtime to create containers, with the Mount array returned by the remote snapshotter
kata-runtime calls hypervisor plugin to process the Mount array. Different hypervisor plugin may have different capabilities. For example, qemu may only supports raw-image-block and raw-layer-block, Dragonball may support all of them. Hypervisor  may share data from host to guest through virtio-blk/pmem/fs.
kata-runtime send creating container requests to kata-agent
kata agent may handle the ExtraOption itself, or call image-rs to handle it.

Proposal for Peer Pods

We need to introduce a remote snapshotter and enhance kata-runtime for Peer Pods.
Proposal for Host sharing through block device

Cooperation
This proposal can be combined with Image pulling on the host to define a generic protocol for Kata Containers, with support of virtio-blk/mem/fs and Kata 2.x/3.x.

I like the idea of not adding additional communication channels.
What kind of things do you expect to be hypervisor-specific that led you to propose a hypervisor plugin in step 5? At a first glance, it seems like the generic fs/block-device sharing would suffice; I'm curious to hear what else would be needed.

FYI, there were effects to extend containerd Mount structure:
https://github.com/containerd/containerd/issues/7055
https://github.com/containerd/containerd/pull/6746

FYI, there were effects to extend containerd Mount structure: containerd/containerd#7055 containerd/containerd#6746

As my understanding, the requirements for containerd is not necessary for PeerPod case because, we can specify runc pod use normal snapshotter and PeerPod use remote-snapshotter if we don't use remote-snapshotter for runc pod on host and any kata pod on host.

I drew the flow of the case for containerd and cri-o as below after discuss with @stevenhorsman @magowan and @jiangliu:

Regarding the cri-o case: I think it can actually be closer to the containerd workflow.
The fact is that we already have kata-specific code in cri-o itself to manage the kata runtime. Changing this code to add some extra options to the CreateContainer request is pretty easy, and would probably be accepted by the cri-o community as it would not change the behaviour of any other containers - only kata ones.
The proposal we are working on, suggested by the cri-o maintainers, is to let cri-o pull the image in a separate volume, then share this volume to the remote VM that can do attestation on the container image, and use it.
We could use this ExtraOption mechanism to provide the needed information for mounting this remote volume.
It would require limited change to cri-o and/or the kata runtime to setup the volume share and add the ExtraOptions, but then I think we can use the current proposal pretty much as is.
Here is what it would look like - please share any comment

I like the idea of not adding additional communication channels.
What kind of things do you expect to be hypervisor-specific that led you to propose a hypervisor plugin in step 5? At a first glance, it seems like the generic fs/block-device sharing would suffice; I'm curious to hear what else would be needed.

For  example, we implement image data lazy loading in virtio-fs/blk backend drivers.
Or encrypt/decrypt cached image data in virtio backend drivers.

Regarding the cri-o case: I think it can actually be closer to the containerd workflow. The fact is that we already have kata-specific code in cri-o itself to manage the kata runtime. Changing this code to add some extra options to the CreateContainer request is pretty easy, and would probably be accepted by the cri-o community as it would not change the behaviour of any other containers - only kata ones.
The proposal we are working on, suggested by the cri-o maintainers, is to let cri-o pull the image in a separate volume, then share this volume to the remote VM that can do attestation on the container image, and use it. We could use this ExtraOption mechanism to provide the needed information for mounting this remote volume. It would require limited change to cri-o and/or the kata runtime to setup the volume share and add the ExtraOptions, but then I think we can use the current proposal pretty much as is.
Here is what it would look like - please share any comment

That's almost the same way for containerd + nydus-snapshotter case. The nydus-snapshotter actually executes three commands to generate a raw disk image from image layer tar files as:
Create a erofs filesystem from each layer tar file
nydus-image create --type tar-tarfs --bootstrap /var/lib/containerd-nydus/snapshots/7/fs/image/layer.boot.tarfs.tmp --blob-id 4a85ce26214d83c77b5464631a67c71e1c2793b655261befe52ba0e20ffc3bd1 --blob-dir /var/lib/containerd-nydus/cache /var/lib/containerd-nydus/snapshots/7/fs/layer_7_tar.fifo

Merge multiple erofs instance for layers into final erofs instane for whole image
nydus-image merge --bootstrap /var/lib/containerd-nydus/snapshots/7/fs/image/image.boot.tarfs.tmp /var/lib/containerd-nydus/snapshots/1/fs/image/layer.boot /var/lib/containerd-nydus/snapshots/2/fs/image/layer.boot /var/lib/containerd-nydus/snapshots/3/fs/image/layer.boot /var/lib/containerd-nydus/snapshots/4/fs/image/layer.boot /var/lib/containerd-nydus/snapshots/5/fs/image/layer.boot /var/lib/containerd-nydus/snapshots/6/fs/image/layer.boot /var/lib/containerd-nydus/snapshots/7/fs/image/layer.boot

Export the final erofs filesystem as a raw disk image with dm-verity info
nydus-image export --block --localfs-dir /var/lib/containerd-nydus/cache --bootstrap /var/lib/containerd-nydus/snapshots/7/fs/image/image.boot --output /var/lib/containerd-nydus/cache/4a85ce26214d83c77b5464631a67c71e1c2793b655261befe52ba0e20ffc3bd1.image.disk.tarfs.tmp --verity
nydus image export command, stdout: dm-verity options: --no-superblock --format=1 -s \"\" --hash=sha256 --data-block-size=512 --hash-block-size=4096 --data-blocks 379918 --hash-offset 194519040 5676d0482c2128e1ae1f59d4b1f253de57158856471b7b5a1bfc0501823bd632

That's one way to generate a seperate volume:)

Hey @jiangliu - thanks for this proposal - if I understand it correctly then it looks good. I guess my initial concerns are:

Is there a dependency on the containerd issue & PR you linked as they look quite old and I don't want to swap one containerd fork for another one!
No, it doesn't depend on those two issues.
That's only one more step to formalize the ExtraOptions in containerd community .

Cri-o support as they don't have the remote snapshotter

On the cri-o support I might have a workaround that we can use in peer pods: If I understand correctly then the 'image-offload' approach works by adding optional ExtraOption message to the CreateContainer request. I'm assuming that these are pretty similar information wise to the PullImageRequest we currently have as a separate endpoint and will do some pretty similar logic to the current image pull in CCv0. Assuming this is correct then it seems like the only thing extra that the remote snapshotter would do would result in appending those ExtraOption for image offload to the CreateContainerRequest body. This makes we wonder if, (similar to the proxyless proposal) in the cloud-api-adaptor's logic, before we send the CreateContainer request to the kata-agent we could look at it and check if it had the ExtraOption set and if not append it and send it on the kata-agent and in this way the remote-snapshotter and cloud-api-adaptor without snapshotter would result in the same message to the kata-agent.
I feel we have a solution for it now:)

Does that make sense, or have I got something wrong?

@jiangliu, @arronwy,
I really would like to have this clear as crystal, does this solution, for the local case, depends on virtio-fs / virtio-9p?
If so, why?
Depending on virtio-fs / virtio-9p would be a no-go for us, as it'd generate issues with:

all the current TEE approaches, as virtio-fs is not supported;
using Cloud Hypervisor, as 9p support will never ever be implemented there;

and, realistically speaking, should not even be considered to be used as a solution as modern distros have been dropping it, and it's always been a security nightmare

I just would like to make sure this is well known, and this is taken into consideration when deciding on the path we'll be taking.

Regarding the cri-o case: I think it can actually be closer to the containerd workflow. The fact is that we already have kata-specific code in cri-o itself to manage the kata runtime. Changing this code to add some extra options to the CreateContainer request is pretty easy, and would probably be accepted by the cri-o community as it would not change the behaviour of any other containers - only kata ones.
The proposal we are working on, suggested by the cri-o maintainers, is to let cri-o pull the image in a separate volume, then share this volume to the remote VM that can do attestation on the container image, and use it. We could use this ExtraOption mechanism to provide the needed information for mounting this remote volume. It would require limited change to cri-o and/or the kata runtime to setup the volume share and add the ExtraOptions, but then I think we can use the current proposal pretty much as is.
Here is what it would look like - please share any comment

If you're going to pull from the host in cri-o, you may as well do the same in containerd. This looks very similar to what I proposed in slack (https://cloud-native.slack.com/archives/C050S70D9SR/p1686914484876879?thread_ts=1682361194.716389&cid=C050S70D9SR) for the remote-snapshotter.
Once there's a way to expose a disk to a remote VM, the snapshotter can use this functionality as well and the two workflows will be almost identical.

I think share volume on host to nested VM is more easier than remote VM, what about we set it as an enhancement direction for CRI-O case for remote VM, and target the 1st goal as below: @jiangliu @stevenhorsman @littlejawa @wedsonaf @fidencio

@jiangliu, @arronwy,
I really would like to have this clear as crystal, does this solution, for the local case, depends on virtio-fs / virtio-9p? If so, why?
Depending on virtio-fs / virtio-9p would be a no-go for us, as it'd generate issues with:

all the current TEE approaches, as virtio-fs is not supported;

using Cloud Hypervisor, as 9p support will never ever be implemented there;

and, realistically speaking, should not even be considered to be used as a solution as modern distros have been dropping it, and it's always been a security nightmare

I just would like to make sure this is well known, and this is taken into consideration when deciding on the path we'll be taking.

We have two cases here:

for Coco, it does not depend on virtio-fs/9p.
for Kata, all of virtio-fs/virtio-blk/virtio-pmem will be supported. And from other side, we prefer virtio-fs/virtio-pmem for Kata.

I think share volume on host to nested VM is more easier than remote VM, what about we set it as an enhancement direction for CRI-O case for remote VM, and target the 1st goal as below: @jiangliu @stevenhorsman @littlejawa @wedsonaf @fidencio

Yeah, creating a volume for peer pods may need to invoke cloud OpenAPI with a complex flow or multi-attach capable cloud storage.

Another point I'd like clarify: none of this should be specific to Nydus as the comments in the ExtraOption snippet seem to suggest.
I think we should have generic options prefixed with io.katacontainers like in https://github.com/kata-containers/kata-containers/pull/7106 -- this allows for a generic implementation without the need for snapshotter-specific code sprinkled throughout the codebase.

Another point I'd like clarify: none of this should be specific to Nydus as the comments in the ExtraOption snippet seem to suggest.
I think we should have generic options prefixed with io.katacontainers like in kata-containers/kata-containers#7106 -- this allows for a generic implementation without the need for snapshotter-specific code sprinkled throughout the codebase.

I feel that's not a blocking issue. Currently the extension is nydus specific, we should cooperate to make it an extension to Kata, with neutral prefix, if we can make the extension generic enough.


Add support for nested Schema namespaces.

Fixes #168 Enhanced the schema attribute in Table to support multiple levels of depth for the schema. Now schema can be defined as either a string, or a tuple/list of strings, and the quotes will be applied properly.
The schema attribute on Table now accepts both string and list/tuple arguments:
Query.from_(Table('abc', ['schema1', 'schema2'])).select('*')

Coverage increased (+0.06%) to 97.915% when pulling 0c687540397834f069dad9de4e4d88dce158e9e8 on fix_table_to_support_multiple_schema_levels into 3049c464924d77a381d7fc896ad296c9f84cfaa0 on master.

Coverage increased (+0.06%) to 97.915% when pulling 0c687540397834f069dad9de4e4d88dce158e9e8 on fix_table_to_support_multiple_schema_levels into 3049c464924d77a381d7fc896ad296c9f84cfaa0 on master.


PinboardItem allows Tags to be pinned

Pinnable check is broken somewhere.

Removed this possibility from UI, closing for now.


App Service Snapshot Restore Issue, This should be fixed. I have seen the below bug already raised but no solution yet.

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az webapp config snapshot restore
Errors:
The command failed with an unexpected error. Here is the traceback:
'WebAppsOperations' object has no attribute 'restore_snapshot'
Traceback (most recent call last):
  File "/home/nikhil/.local/lib/python3.7/site-packages/knack/cli.py", line 231, in invoke
    cmd_result = self.invocation.execute(args)
  File "/home/nikhil/.local/lib/python3.7/site-packages/azure/cli/core/commands/__init__.py", line 657, in execute
    raise ex
  File "/home/nikhil/.local/lib/python3.7/site-packages/azure/cli/core/commands/__init__.py", line 720, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/home/nikhil/.local/lib/python3.7/site-packages/azure/cli/core/commands/__init__.py", line 691, in _run_job
    result = cmd_copy(params)
  File "/home/nikhil/.local/lib/python3.7/site-packages/azure/cli/core/commands/__init__.py", line 328, in __call__
    return self.handler(*args, **kwargs)
  File "/home/nikhil/.local/lib/python3.7/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
    return op(**command_args)
  File "/home/nikhil/.local/lib/python3.7/site-packages/azure/cli/command_modules/appservice/custom.py", line 1894, in restore_snapshot
    return client.web_apps.restore_snapshot(resource_group_name, name, request)
AttributeError: 'WebAppsOperations' object has no attribute 'restore_snapshot'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az webapp config snapshot restore -g {} -n {} --time {}

Expected Behavior
Environment Summary
Linux-5.4.0-1063-azure-x86_64-with-debian-10.2 (Cloud Shell), Common Base Linux Delridge (quinault)
Python 3.7.3
Installer: PIP

azure-cli 2.30.0

Additional Context

https://github.com/Azure/azure-cli/issues/19492

route to service team

@yonzhan  any update on the above?

webapp service team should take a look

@nik0811 Apologies for the late reply. Could you please try running the same command using the most recent version of the AzCLI and check if you still face this issue? Awaiting your reply.


Ly can't start, After login only blinking cursor appear

OS: Fedora 36
I'm having problem when trying to login with ly. After successfull login, ly only show blinking cursor. I've tried for Gnome on Xorg session and i3 session (same result: blinking cursor). I've added shebang and make .xinitrc executable.
When blinking cursor appear, I checked running programs (on another tty) with ps aux | grep X and Xorg not running
After some trial and error. I found that executing startx in another tty solve the problem. But, i want ly automatically start X instead manually
~/.xinitrc file
#!/bin/sh

exec i3

Could you try to execute ly as sudo? If that works, it's a duplicate of #433.

This issue could also be caused by SELinux permission issues, as reported in #494.


Preview CSV Text with Peek

Description of the new feature / enhancement
I would like the PowerToys Peek utility to provide a preview for CSV files.
Scenario when this would be used?
CSV text is a common data format and I often (OFTEN) which to preview it without Excel™ violating the data in some weird way, so it would be really helpful to me to be able to preview it with Peek.
Supporting information
CSV is simply text, and renaming the CSV file to .txt indeed shows that Peek can preview the content without issue (it even shows line numbers 🥇 ). I just need it to do so when the file name is .CSV

/dup #26210

Changes are coming in 0.75 to preview more file types. If the new viewer does not work well for your csv files please reopen this issue.

This util doesn't work on my PC running Windows 11. The version of PowerToys is 0.78.0. 🤡

This util doesn't work on my PC running Windows 11. The version of PowerToys is 0.78.0. 🤡

Please open a new issue with more details.


Can't get and to build the project.

When attempting to build the project, build always fails. I'm not sure how to resolve this issue. Seems to be due to the following:
[ivy:resolve] :: problems summary ::
[ivy:resolve] :::: WARNINGS
[ivy:resolve]   problem while downloading module descriptor: http://repo1.maven.
org/maven2/com/thoughtworks/xstream/xstream/1.4.4/xstream-1.4.4.pom: invalid sha
1: expected=9e88db04254ffc7b513471405a97a5c57d732a9c computed=e00eebf36780667926
e3daf3d67d2a88422ffbef (234ms)
[ivy:resolve]           module not found: com.thoughtworks.xstream#xstream;1.4.4
[ivy:resolve]   ==== local: tried
[ivy:resolve]     C:\Users\Raymond.ivy2\local\com.thoughtworks.xstream\xstream
1.4.4\ivys\ivy.xml
[ivy:resolve]     -- artifact com.thoughtworks.xstream#xstream;1.4.4!xstream.jar
:
[ivy:resolve]     C:\Users\Raymond.ivy2\local\com.thoughtworks.xstream\xstream
1.4.4\jars\xstream.jar
[ivy:resolve]   ==== shared: tried
[ivy:resolve]     C:\Users\Raymond.ivy2\shared\com.thoughtworks.xstream\xstream
\1.4.4\ivys\ivy.xml
[ivy:resolve]     -- artifact com.thoughtworks.xstream#xstream;1.4.4!xstream.jar
:
[ivy:resolve]     C:\Users\Raymond.ivy2\shared\com.thoughtworks.xstream\xstream
\1.4.4\jars\xstream.jar
[ivy:resolve]   ==== public: tried
[ivy:resolve]     http://repo1.maven.org/maven2/com/thoughtworks/xstream/xstream
/1.4.4/xstream-1.4.4.pom
[ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:resolve]           ::          UNRESOLVED DEPENDENCIES         ::
[ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:resolve]           :: com.thoughtworks.xstream#xstream;1.4.4: not found
[ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:resolve]
[ivy:resolve]
[ivy:resolve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
BUILD FAILED
C:\Users\Raymond\Documents\JMeter-Rabbit-AMQP-master\build.xml:55: impossible to
resolve dependencies:

It seems that I have exactly the same problem.

I removed my ivy cache and was able to build the project no problem.
The error you show is a problem with xstream-1.4.4 on repo1.maven.org.  Presumably the issue has been fixed.  If not, it's not a problem with this project, but with the artifact on repo1.maven.org.


Increase the difficulty of Stage 2 Step 1 decoding

I would propose since the project is based on cryptography, we should replace simple decoding by some king of crypto related cipher.

I would like to take this up and work on it. I already have some ideas.


Unable to Create project and default org

Issue Type: Bug
Hi, I am unable to create project and default org  through palatte, it is showing some error
Command 'SFDX: Create Project' resulted in an error (command 'sfdx.force.project.create' not found)
VS Code version: Code 1.52.0 (940b5f4bb5fa47866a54529ed759d95d09ee80be, 2020-12-10T22:45:11.850Z)
OS version: Windows_NT x64 10.0.17134

/causedByExtension


Fix #2491: Consider all exported properties as externs for GCC.

The name clashes were caused by GCC renaming some Scala methods or fields to a name that was also exported. Hence, a Scala class could have, as instance member, both a (renamed) Scala method/field and a (non-renamed) exported method or property.
To prevent this, we list all exported methods and properties in the linking unit, and we feed them as externs to GCC. This forces GCC to avoid those names when renaming Scala methods and fields.

Review by @gzm0.
Note that this is basically untestable, since the bug only manifests itself in very specific combinations of code that cause GCC to, unfortunately, cause a clash.
I have however locally tested that this fixes the repo mentioned in the issue.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3323/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/4322/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3322/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/4321/
Test PASSed.

That's all.

Updated.

LGTM

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3326/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/4327/
Test PASSed.


Pipeline for creating data container with repo contents

Changes

Added pipeline and docker files for creating data container that can be consumed in k8s environment to bootstrap a service that consumes openapi specs
The pipeline requires two variables at runtime

ACR registry name (service connection)
ACR repository name prefix

The pipeline is configured to run on push (trigger) and scheduled for a nightly build
The ACR repository name will be of the format 'repoName-branch' (ex: azure-rest-api-specs-master)
The image name will be of the format 'major.minor.datetime.build' (ex: 1.0.21320200622.6)

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.

adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.


How can I decrease the draw distance?

Hi, my computer isn't too good, but I would like to use 2dfx anyways. What I've noticed is the bigger draw distance, that I would like to decrease, but in-game options don't really give a good effect.

Before I've used 2dfx objects like trees, poles from a far distance couldn't be seen, but it was compensated by the timecyc I use, it has a higher farclip than the original one. I would like to have the lights around the city, but still have the old draw distance of everything like it was before installing 2dfx.

Unfortunately the default values are too demanding for most PCs so you can try
MaxNumberOfLodLights = 1000
DrawDistance = 3.0

Unfortunately the default values are too demanding for most PCs so you can try

Not true, recently replayed III era games with default values at first, then increased draw distance from 800.0 to 8000.0, no issues at all.

pffff right


Determine best method for support container versions

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Feature request
Information:
There is no way to specify nginx/mysql container versions except via the command line. It'd be nice to be able to commit this config so that it could be shared across a team. There's also no way to control templating for docker-compose.
Prior art:
https://github.com/docksal/drupal8/blob/master/.docksal/docksal.env#L11
http://docs.kalabox.io/en/v2.1/users/started/#kalabox-apps
Related Issues
This is a part of larger site configuration concerns, alongside #7 and #5. It feels like a single config file/format that could accommodate them all could be in order.
Deliverable:
A proposal outlining a configuration method for containers and application templates, including a sample configuration.

@beeradb Given that .ddev/config.yml contains these, I'm assuming this can be marked duplicate/closed?

Yes, this should be good at this point.


Callback fired before all files are written

I looked a bit into the source code and noticed that the callback function is called before all files are written. I also noticed that in my case there are 4 workers left, that aren't ready and are not killed before callback() is called.
Also the last few console logs are:
"Finished converting CityGML"
Saved: ../../CityGML/OBJ/DEBY_LOD2_21643111.obj
Saved: ../../CityGML/OBJ/DEBY_LOD2_721486.obj
Saved: ../../CityGML/OBJ/DEBY_LOD2_721487.obj
Saved: ../../CityGML/OBJ/DEBY_LOD2_721488.obj

so the workers haven't finished the saving before callback() is fired.

I've pushed 0.1.25 which now waits for all the workers to finish writing files before firing the callback. This has little to no effect on #10 so I'm going to continue digging in that issue. Happy to re-open this one if you find the callback order still isn't correct.


Fixed unbind of getDocumentKeyUp in destroy function

Fixed unbind of getDocumentKeyUp in destroy function

Thank you for this fix!


ECS Cluster Role not longer authorized to run cfn scripts

Ok, I don't know what happened, but I am planning a service based on this reference infrastructure and as of yesterday it worked like a charm.
But today the Initialization via CloudFormation stopped working at all. The Autoscaling Instances that make up the ECS Cluster seem not longer be authorized to send signals to CloudFormation. So instead of adding itself to the cluster they remain in the "default" cluster and the stack creation fails/times out. The managed role

AmazonEC2ContainerServiceforEC2Role

seem no longer be able to perform the necessary actions.
Dont know how to quickly fix that, just wanted to leave it here. The system log of the instances look like this

AccessDenied: User: arn:aws:sts::$AccountId:assumed-role/ecs-cluster-ECSRole-1U3Z9R13GFRX6/$InstanceId is not authorized to perform: cloudformation:DescribeStackResource on resource: arn:aws:cloudformation:eu-west-1:$AccountID:stack/ecs-cluster/*
AccessDenied: User: arn:aws:sts::$AccountId:assumed-role/ecs-cluster-ECSRole-1U3Z9R13GFRX6/$InstanceId is not authorized to perform: cloudformation:SignalResource on resource: arn:aws:cloudformation:eu-west-1:$AccountID:stack/ecs-cluster/*

Ok, just fyi I fixed it for now by adding an explicit access policy to cloudformation to the ECSRole with this configuration. Thats probably not following the "minimal permissions" policy but it works for now. I read the docs like that cfn-init and co would have automatic access to their respective stacks.
cloudformationAccessRole:
Type: AWS::IAM::Policy
Properties:
PolicyName: !Sub "${AWS::StackName}-cfn"
PolicyDocument:
Version: "2012-10-17"
Statement:
-
Effect: "Allow"
Action:
- "cloudformation:DescribeStackResource"
- "cloudformation:SignalResource"
Resource:
- "*"
Roles:
- !Ref ECSRole

Hmm, I'm a little confused, are you using that ECS role in your CodePipeline pipeline?


Update note about Edge avif support

https://github.com/Fyrd/caniuse/pull/6756#issuecomment-1693473623

You may want to use a new flag #7 instead of the note.

Thanks!


[Feat]: Add Hover Effect to Main Heading for Dynamic Appearance

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Feature Description
I would like to request the addition of a hover effect to the main heading on the website's homepage. While the website is well-built and dynamic, the static main heading does not align with the rest of the site's interactive elements. Adding a hover effect will make the heading more engaging and consistent with the dynamic design of the website.
The main heading should have a smooth hover effect that changes its appearance when the user hovers over it. The hover effect can include a slight color change and scaling to make it more visually appealing.
Please assign this issue to me, and I would be happy to implement this feature.
Use Case
This feature would enhance the user experience by adding a modern, interactive feel to the main heading. Users are more likely to be drawn to a dynamic element, especially when it's the main focus of the page.
Benefits

Improved User Engagement: The hover effect will grab users' attention and encourage interaction with the page.
Consistent Design: Adding a hover effect to the main heading aligns it with the rest of the website’s dynamic design elements.
Modern Look: It will give the website a more polished, modern appearance.

Priority
High
Agreements

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC contributor
[X] I'm a Hacktoberfest contributor
[X] I want to work on this issue
[X] I'm willing to provide further clarification or assistance if needed.

assign me the task under GSSOC AND HACKTOBERFEST .

Proceed!