Error occurred in update_chart_lines: Can only use .str accessor with string values!

Question
I am struggling to get the .update to work on my line objects. I am pretty sure I have the correct format for the pd.Series and have followed the docs to the best of my ability.
terminal output states:
Received avg_series_high: 2024-03-05    3693.797625
dtype: float64
Error occurred in update_chart_lines: Can only use .str accessor with string values!
I have never seen this error before whilst use pd and all examples of this error i have found online seem to indicate that the name of the series may not automatically be being treated as a string?
Any help or pointers would be greatly appreciated.
Code example
async def update_chart_lines(self, avg_line_high, avg_line_low, avg_line_high2, avg_line_low2, queue):
        print("Starting update_chart_lines function")
        avg_data = None

        while True:
            try:
                avg_data = await queue.get()

                if avg_data is not None and 'date' in avg_data:

                    avg_data['date'] = pd.to_datetime(avg_data['date'], unit='ms')
                    # Create a pandas Series for each line
                    avg_series_high_data = pd.Series([avg_data['avg_last_candles_high']], index=[avg_data['date']])
                    avg_series_low_data = pd.Series([avg_data['avg_last_candles_low']], index=[avg_data['date']])
                    avg_series_high2_data = pd.Series([avg_data['avg_last_candles_high2']], index=[avg_data['date']])
                    avg_series_low2_data = pd.Series([avg_data['avg_last_candles_low2']], index=[avg_data['date']])

                    print(f"Received avg_series_high: {avg_series_high_data}")

                    # Update each line with the corresponding pandas Series
                    avg_line_high.update(avg_series_high_data)
                    avg_line_low.update(avg_series_low_data)
                    avg_line_high2.update(avg_series_high2_data)
                    avg_line_low2.update(avg_series_low2_data)
                else:
                    print("No avg candle ticks to process.")
                    continue
            except Exception as e:
                print(f"Error occurred in update_chart_lines: {e}")

import pandas as pd
import os
import sys
import asyncio
from asyncio import Queue

async def last_candles_cont(df, n, timeframe, queue):

  timeframe = timeframe

  """ print(f"Calculating average of last {n} candles for {timeframe} timeframe") """

  multipliers = {
    '1d': 1.025,
    '4h': 1.015,
    '1h': 1.01,
    '15m': 1.005,
    '5m': 1.001,
    '1m': 1.00
  }

  while True:
    try:

      avg_data = None

      tick= await queue.get()

      print(f"Received tick: {tick}")

      tick_df = pd.DataFrame(tick, index=[0])

      df = pd.concat([df, tick_df], ignore_index=True)

      """ df['diff'] = df['close'] - df['close'].shift(1)
      print (df['diff'])

      # Calculate the rate of change as a percentage
      df['roc'] = df['diff'] / df['close'].shift(1) * 100
      print (df['roc']) """

      multiplier = multipliers[timeframe]

      df['avg_last_candles_high'] = (df['high']*multiplier).shift(1).rolling(n).mean()
      df['avg_last_candles_low'] = (df['low']/multiplier).shift(1).rolling(n).mean()

      df['avg_last_candles_high2'] = (df['high']*multiplier).rolling(n).mean()
      df['avg_last_candles_low2'] = (df['low']/multiplier).rolling(n).mean()

      avg_data = pd.DataFrame({
              'date': (df['date']),
              'avg_last_candles_high': df['avg_last_candles_high'],
              'avg_last_candles_low': df['avg_last_candles_low'],
              'avg_last_candles_high2': df['avg_last_candles_high2'],
              'avg_last_candles_low2': df['avg_last_candles_low2'],
          }).dropna()

      current_candle = avg_data.tail(1).squeeze()
      print(f"Current candle: {current_candle}")
      # Put the current candle into the queue
      await queue.put(current_candle)

      await asyncio.sleep(1)

      """ return avg_data """

    except Exception as e:
      print(f"Error in avg candle function: {e}")
      return pd.DataFrame()  # Return an empty DataFrame in case of error

What should my series look like? 'time' & 'value'. Anything else?


Launch Issues with 4.2.1 and Big Sur

Problem Description
I just installed Spyder 4.1.5 through Anaconda in a new ARM MacBook Pro with Big Sur, I had some problems at the beginning with high latency problems, but  I updated QT to v5.12.5 and problems gone.
The point is that Spyder notify me that I could update to 4.2 so I did that, and Spyder never launch again, then I tested to update to v4.2.1 that perfectly launch, so I'm at the point that I have Spyder 4.2.1 and Qt 5.12.5 and everything works.
But, and here is where I need help, all times I launch Spyder I get an Issue Reporter that tells me: "Spyder has encountered an internal problem", you can se the paste of problem detail below:
  File "/Users/vicentegt/anaconda3/lib/python3.8/site-packages/spyder/plugins/editor/widgets/status.py", line 113, in process_git_data
    branches, branch, files_modified = output
TypeError: cannot unpack non-iterable NoneType object

That happen every time when I launch Spyder, if I close that everything works, but it's a bit annoying and im worried that some complex task could go wrong. It also open in the script editor a script called "spyder" that I never created or opened:
#!/bin/bash /Users/vicentegt/anaconda3/bin/pythonw

# -*- coding: utf-8 -*-
import re
import sys

from spyder.app.start import main

if __name__ == '__main__':
    sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0])
    sys.exit(main())

and when I run ti I get:
Spyder is already running. If you want to open a new
instance, please pass to it the --new-instance option
What steps reproduce the problem?

Take an Apple Silicon, ARM M1 MacBook Pro with macOS Big Sur
Install Anaconda
Update Spyder by conda forge channel to v4.2.1
Update Qt by conda forge channel to 5.12.5
Launch spyder

What is the expected output? What do you see instead?
The expected output is to don't get and Issue Report window.
 You said:

so I'm at the point that I have Spyder 4.2.1 and Qt 5.12.5 and everything works.

That's the right combination to make Spyder work in Big Sur, so you need to stay with it.

But, and here is where I need help, all times I launch Spyder I get an Issue Reporter that tells me: "Spyder has encountered an internal problem"

Question about this problem: do you have git installed in your system?

That happen every time when I launch Spyder, if I close that everything works, but it's a bit annoying and im worried that some complex task could go wrong

It's safe to ignore it for now. We'll try to fix it in our next version (4.2.2), to be released in mid February.

It also open in the script editor a script called "spyder" that I never created or opened

This seems another problem with Big Sur. It's the script used to open Spyder, so you don't need to run it or do anything with it. We'll also try to fix this problem for 4.2.2.

If you want to have a Spyder installation without these problems, please use our  DMG installer in the meantime.
By following the instructions we wrote here, you'll be able to connect our app to your current conda envs.

I'm having similar issues with Spyder 4.2.1 on Mojave.
If launched from the terminal or gui pointing to the conda install, it works fine but opens the spyder script as mentioned above.
If launched from the new dmg install, it crashes straight away (this didn't happen with the previous dmg version).

Thanks for your complete answer @ccordoba12 , related to that:

Question about this problem: do you have git installed in your system?
I don't have git installed neither at my Mac or Anaconda.

If you want to have a Spyder installation without these problems, please use our DMG installer in the meantime.
I just did that but I didn't know how to use my conda packages with Spyder if it's installed "out" of Anaconda or miniforge. So what u send me here:
By following the instructions we wrote here, you'll be able to connect our app to your current conda envs.
Seems to be the solution of my problems while I wait for some future updates. Thank you so much! That was just what I needed because Spyder "out" of conda work perfectly fine for me.

Thanks again,
Vicente.

I'm having a similar issue after updated to Big Sur with both anaconda-spyder and spyder4.2.1 stand alone unable to launch. The icon will pop up at the dock, but nothing happens, and indicating program/python 3.7 not responding. Tried to uninstall and reinstall, but the commands for un/reinstall doesn't working either....
Any suggestions? @ccordoba12

Please open Terminal and run there
spyder --debug-info verbose --debug-output file

and upload the file called spyder-debug.log, which should be created in the directory where you ran that command.

I have to say that what @ccordoba12 suggested me work perfectly. I have a standalone Spyder install that picks my python env and pkgs from Anaconda. I had a bit of troubles with spyder-kernels but its solved just updating them.
Thanks again, that setup works while I wait Anaconda to update.

I am having the exact same issues as OP. Spyder works, but the startup messages and automatic opening of the spyder script (descibed in OP) is an annoyance.
It looks like no one has uploaded the spyder-debug.log
Here is mine:
spyder-debug.log

Same problem here. If there's any more data needed to debug, feel free to ping me!
Error:
  File "/opt/anaconda3/envs/lambda-analyse-articles/lib/python3.8/site-packages/spyder/plugins/editor/widgets/status.py", line 113, in process_git_data
    branches, branch, files_modified = output
TypeError: cannot unpack non-iterable NoneType object

Also, I have git installed and am using it.

I'll write down here the configuration that works for me. Maybe it's useful for you @robbwh @BastianZim .
As anaconda isn't still ARM native I downloaded mambaforge (which is ARM compatible). Then I installed standalone spyder from here. Once I have mambaforge and Spyder the way to link them is: Spyder > Preferences > Python Interpreter > Select the following python interpreter: /Users/your_user/mambaforge/bin/python3.9
After that you will have an issue when Spyder open, something about spyder-kernels is missing in your selected python eviroment. Solve that is really easy, just go to Applications Folder on your Mac, find Spyder.app then control+click and show package content, then go to: Contents/Resources/lib/python3.9/ there find "spyder_kernels" folder and copy it to your ~/ (home directory).
Once you have that folder there, just start spyder and it will find by default the kerners that you just set in your home directory. And everything should work perfectly. At least it work for me with MacBook Pro M1 with Big Sur 11.1.
Hope that helps you while we wait for future updates.

I'll write down here the configuration that works for me. Maybe it's useful for you @robbwh @BastianZim .
As anaconda isn't still ARM native I downloaded mambaforge (which is ARM compatible). Then I installed standalone spyder from here. Once I have mambaforge and Spyder the way to link them is: Spyder > Preferences > Python Interpreter > Select the following python interpreter: /Users/your_user/mambaforge/bin/python3.9
After that you will have an issue when Spyder open, something about spyder-kernels is missing in your selected python eviroment. Solve that is really easy, just go to Applications Folder on your Mac, find Spyder.app then control+click and show package content, then go to: Contents/Resources/lib/python3.9/ there find "spyder_kernels" folder and copy it to your ~/ (home directory).
Once you have that folder there, just start spyder and it will find by default the kerners that you just set in your home directory. And everything should work perfectly. At least it work for me with MacBook Pro M1 with Big Sur 11.1.
Hope that helps you while we wait for future updates.

After that you will have an issue when Spyder open, something about spyder-kernels is missing in your selected python eviroment. Solve that is really easy, just go to Applications Folder on your Mac, find Spyder.app then control+click and show package content, then go to: Contents/Resources/lib/python3.9/ there find "spyder_kernels" folder and copy it to your ~/ (home directory).

Thanks for your help @vivito51. Although possible, this is not the right way to install spyder-kernels. What you need to do is running in your conda env this command:
mamba install spyder-kernels=1.10.1

After that you will have an issue when Spyder open, something about spyder-kernels is missing in your selected python eviroment. Solve that is really easy, just go to Applications Folder on your Mac, find Spyder.app then control+click and show package content, then go to: Contents/Resources/lib/python3.9/ there find "spyder_kernels" folder and copy it to your ~/ (home directory).

Thanks for your help @vivito51. Although possible, this is not the right way to install spyder-kernels. What you need to do is running in your conda env this command:
mamba install spyder-kernels=1.10.1

Thanks for your help @vivito51. Although possible, this is not the right way to install spyder-kernels. What you need to do is running in your conda env this command:
mamba install spyder-kernels=1.10.1

Thanks @ccordoba12 I actually try to do that but I get the following error:
(base) vicentegt@arm64-apple-darwin20 ~ % mamba install spyder-kernels=1.10.1
Looking for: ['spyder-kernels=1.10.1']
conda-forge/osx-arm64    Using cache
conda-forge/noarch       Using cache
Encountered problems while solving.
Problem: nothing provides requested spyder-kernels 1.10.1**

That's why I ended up copy-pasting the kernels from original Spyder.app folder to home directory. Do you know how to solve that error?

Thanks for your help @vivito51. Although possible, this is not the right way to install spyder-kernels. What you need to do is running in your conda env this command:
mamba install spyder-kernels=1.10.1

Thanks @ccordoba12 I actually try to do that but I get the following error:
(base) vicentegt@arm64-apple-darwin20 ~ % mamba install spyder-kernels=1.10.1
Looking for: ['spyder-kernels=1.10.1']
conda-forge/osx-arm64    Using cache
conda-forge/noarch       Using cache
Encountered problems while solving.
Problem: nothing provides requested spyder-kernels 1.10.1**

That's why I ended up copy-pasting the kernels from original Spyder.app folder to home directory. Do you know how to solve that error?

Ok, then I guess you need to run
mamba install -c conda-forge spyder-kernels=1.10.1

(I thought Mamba used conda-forge by default).

Ok, then I guess you need to run
mamba install -c conda-forge spyder-kernels=1.10.1

(I thought Mamba used conda-forge by default).

It still doesn't work @ccordoba12 :
(base) vicentegt@arm64-apple-darwin20 ~ % mamba install -c conda-forge spyder-kernels=1.10.1
Looking for: ['spyder-kernels=1.10.1']
pkgs/main/osx-arm64      [====================] (00m:00s) Done
pkgs/r/osx-arm64         [====================] (00m:00s) 404 Failed
conda-forge/osx-arm64    [====================] (00m:00s) Done
pkgs/main/noarch         [====================] (00m:03s) Done
pkgs/r/noarch            [====================] (00m:03s) Done
conda-forge/noarch       [====================] (00m:05s) Done
Encountered problems while solving.
Problem: nothing provides requested spyder-kernels 1.10.1**

It still doesn't work @ccordoba12 :
(base) vicentegt@arm64-apple-darwin20 ~ % mamba install -c conda-forge spyder-kernels=1.10.1
Looking for: ['spyder-kernels=1.10.1']
pkgs/main/osx-arm64      [====================] (00m:00s) Done
pkgs/r/osx-arm64         [====================] (00m:00s) 404 Failed
conda-forge/osx-arm64    [====================] (00m:00s) Done
pkgs/main/noarch         [====================] (00m:03s) Done
pkgs/r/noarch            [====================] (00m:03s) Done
conda-forge/noarch       [====================] (00m:05s) Done
Encountered problems while solving.
Problem: nothing provides requested spyder-kernels 1.10.1**

Ok, I understand what happens now: the problem is that spyder-kernels is not available for the new arm64 architecture of M1 chips. I opened this pull request to see what we can do about it:
https://github.com/conda-forge/spyder-kernels-feedstock/pull/60

Ok, I understand what happens now: the problem is that spyder-kernels is not available for the new arm64 architecture of M1 chips. I opened this pull request to see what we can do about it:
https://github.com/conda-forge/spyder-kernels-feedstock/pull/60

@ccordoba12 thank you! I see that they said we should wait about 1 week from now. At least we can manually take spyder-kernels from spyder.app/contents folder just copying it to home directory. It works for my by now even if it's not the correct way to install it.
Thank you for all your help!

@ccordoba12 thank you! I see that they said we should wait about 1 week from now. At least we can manually take spyder-kernels from spyder.app/contents folder just copying it to home directory. It works for my by now even if it's not the correct way to install it.
Thank you for all your help!

To everyone subscribed to this issue: all problems reported here are fixed now. I included their fixes in a new build of 4.2.1 in conda-forge, so to get them you need to run
conda remove --force spyder
conda install -c conda-forge spyder=4.2.1

To everyone subscribed to this issue: all problems reported here are fixed now. I included their fixes in a new build of 4.2.1 in conda-forge, so to get them you need to run
conda remove --force spyder
conda install -c conda-forge spyder=4.2.1

@vivito51, spyder-kernels packages for M1 will be ready tomorrow (hopefully).

@vivito51, spyder-kernels packages for M1 will be ready tomorrow (hopefully).


Add StreamBufferCapacity configuration for SignalR

We added a new configuration option that we need to document, see https://github.com/aspnet/AspNetCore/issues/4399

This can just be added to https://docs.microsoft.com/en-us/aspnet/core/signalr/configuration?view=aspnetcore-2.2&tabs=dotnet


feat(antigravity): update to 3.11

Hey guys, first time contributing, so sorry in advance if I'm missing something.

Moved from here: https://github.com/python/cpython/blob/3.11/Lib/antigravity.py
Found no tests, but I tested it manually, and it seems ok.

I'm surprised there isn't a test for the geohashing algorithm.

welcome, and thank you for contributing!


Read and set parameters

Add functionality that makes it possible to read and write parameters to a node. That`s done with the "Configuration" command class.

I could use this so i could change philio PAN04-1B to be controlled by pulse rather than edge node. config parameter 4:
1.Edge mode
2.Pulse mode
3.Edge-Toggle mode


Can you have multiple different instituition?

Can you have a credit card from Bofa, Roth IRA from Fidelity, savings from another... and multiple others.... Is that possible or is it only allowed to have a singular institution?

Yes its possible!!! Thanks for creating this amazing tool. I was frustrated a lot of similar tools online cost money or sells your data.


CATS OG PASS NOT RECEIVED

Sent 1 ton not received og pass on cats refund my ton
UQDJwAYLI1etZWNNWg_6mKmiE6r9FNOJSDSFLDFuVAR3tCHu

@AatifOp121 Thanks for posting the issue.
Your query would be best dealt with by the support team.
Please see the link below to our dedicated support line:
Support : Help Center
Note: Click on the live chat icon at the bottom corner of the page to start a conversation


Improved view ergonomics

This PR improves some of the ergonomics of view code:

The Fill, FillPortion, and Shrink variants of Length are re-exported by the root crate. Effectively, this means we can now import these directly:

use iced::widget::container;
use iced::Fill;

container("Yay!").width(Fill)

The Center, Left, Right, Top, and Bottom variants of the different alignment enums are also re-exported. Thus, we can now write:

use iced::widget::text;
use iced::{Center, Fill};

text("I am centered!").width(Fill).align_x(Center)

align_items in Column and Row have been renamed to align_x and align_y respectively.
horizontal_alignment and vertical_alignment in Text have been renamed to align_x and align_y.
The padding module exposes free functions to build Padding values and the type has methods of the same name that work as setters. Thus, we can write:

use iced::widget::container;
use iced::padding;

container("I have a padding of 10 all around, except my right side!")
    .padding(padding::all(10).right(0))

The border module has received a similar treatment to padding:

use iced::widget::container;
use iced::border;

container("My top right corner isn't rounded!")
    .style(|theme: &Theme| container::Style {
        border: border::rounded(border::radius(10).top_right(0)).color(Color::BLACK).width(2),
        ..container::Style::default()
    })

Closes #2260.

I don't think those are that common, since they are only used for images.


Disliked songs or songs removed from recent don't disappear automatically from the list

you have to go to another screen and come back for it to be refreshed

This has been fixed.


fix: prefetch to preconnect

fix preconnect

Duplicate https://github.com/nuxt-community/google-fonts-module/pull/52


Random Error Output on Version

[project:sm]
C:\Users\super3\Desktop\storjnode-0.0.7.win32>storjnode.exe version
v0.0.7
Traceback (most recent call last):
  File "storjnode", line 10, in <module>
  File "storjnode\cli.pyo", line 168, in main
NameError: global name 'exit' is not defined

Uploaded a new v0.0.7 with local hotfix. Its only a hotfix. If we have to build v0.0.7 again the bug can come again.
Final bugfix will be in the next version.


client did not complete upgrade - closing transport

From: https://github.com/mrniko/netty-socketio/blob/master/src/main/java/com/corundumstudio/socketio/transport/WebSocketTransport.java#L196
I don't know why but this is happening to me randomly, no apparent reason.
This happens on my production server (using nginx as proxy) and also on my local environment (connecting directly to the netty-socketio server). It's pretty much random and I cant identify a pattern on it. For example, if I continuously keep refreshing the client app on the browser (with a 5 seconds interval), at some point this error will happen, and for the subsequent tries it will work normal again (until it happens another time).
Any thoughts on this are really appreciated.
Thanks!

@josuelima see https://github.com/mrniko/netty-socketio/issues/327 , should be the same issue.

you should update your socket io script version to 1.5.0 or higher.download page is here https://github.com/socketio/socket.io-client/releases. you also can use cdn from http://www.bootcdn.cn/socket.io/   .that will fix your problem.

Today in 2018 I am facing same issue with my nodejs+socketio app on local as well as Heroku server. I am on 2.1.1 version which is latest as of now and I face the exact same issue. I am still researching to find a solution, hoping to solve it.


Data Science with Python : Exploratory Data Analysis using Python

Description 📜
Created Video on Exploratory Data Analysis using Superstore Dataset.
Issue Title: Data Science with Python: Exploratory Data Analysis using Python
Fixes: #348

Type of change 📝

[x] Video (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)

Domain of Contribution 📊

[x] Datascience with Python

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Please review @prathimacode-hub

I've made the requested changes, Please review @prathimacode-hub


Updated text from "jQuery Funhouse" to "jQuery Playground"

Changed text for line 549 in jquery.json file, from "jQuery Funhouse" to "jQuery Playground".
Closes #5032.

Thanks! :+1:


[shortfin] Teach setup.py to build using cmake

Looking for an initial review. This setup works, the only thing I don't like is hardcoding clang/clang++, because libshortfin doesn't compile with GCC (right now, due to some comparisons between data types)


remove deleted bin files from package.json

fixes https://github.com/beaugunderson/ip-address/issues/44

Current coverage is 100% (diff: 100%)

Merging #45 into master will not change coverage

@@           master   #45   diff @@
===================================
  Files          10    10
  Lines         607   607
  Methods        97    97
  Messages        0     0
  Branches       93    93
===================================
  Hits          607   607
  Misses          0     0
  Partials        0     0

Powered by Codecov. Last update c31b48e...0f677ad

+1, this is breaking libnmap as well. For anyone depending on this library, you can use npm install ---no-bin-links as a workaround in the meantime.

merged and released 5.8.4 thank you both and sorry for the trouble!

Thank you @beaugunderson !!

@gavinmcdermott this is fixed now :)


Verify permissions on /etc/opensearch/root-ca.pem for upgraded host

Raul had host where the permissions for /etc/opensearch/root-ca.pem were only readable by opensearch, which was a problem for elmond. He had a nightly->staging upgrade path that may have caused this. I did not see this on my upgraded host, but want to verify we are good. This may end up being a no-op.

Actually on a bunch of my test hosts that just had staging, opensearch also started complaining about permission of things under /etc/opensearch. We probably should run a chown -R opensearch:opensearch /etc/opensearch/ in setup scripts.


angular-meteor app fails on startup with "unknown provider $$asyncCallbackProvider"

I haven't changed any app code but I did do 'meteor update' after which my app ceased to startup.
Here's the browser console output:
app.ng.js?e999ad7257a2d60cd9fc4de2b25e2b6e9dfe322a:13 non-cordova init
app.ng.js?e999ad7257a2d60cd9fc4de2b25e2b6e9dfe322a:4 initalizing angular
angular.js:68 Uncaught Error: [$injector:unpr] Unknown provider: $$asyncCallbackProvider <- $$asyncCallback <- $animate <- $compile
http://errors.angularjs.org/1.4.4/$injector/unpr?p0=%24%24asyncCallbackProvider <- %24%24asyncCallback <- %24animate <- %24compile
This is my entire app.ng.js file (located in client/lib per the tutorial)
 angular.module('ionicApp', ['angular-meteor', 'ui.router','ionic'])

 function onReady() {
   console.log("initalizing angular");
   angular.bootstrap(document, ['ionicApp']);
   console.log("initalized");
 }
 if (Meteor.isCordova) {
   console.log("cordova init");
   angular.element(document).on("deviceready", onReady);
 }
 else {
   console.log("non-cordova init");
   angular.element(document).ready(onReady);
 }

And my index.ng.html (note - no ngApp per the tutorial)
 <head>
   <title>makerActive</title>
 </head>

 <body>

 <ion-nav-bar class="bar-positive">
   <ion-nav-back-button>
   </ion-nav-back-button>

 </ion-nav-bar>

   <ion-nav-view>

   </ion-nav-view>
 </body>

These are all the packages I've got loaded:
$ meteor list
accounts-password            1.1.1  Password support for accounts
accounts-ui                  1.1.5  Simple templates to add login widgets to an app
aldeed:collection2           2.3.3  Automatic validation of insert and update operations on the client and server.
angularui:angular-ui-router  0.2.15  angular-ui-router (official): Flexible routing with nested views in AngularJS
autopublish                  1.0.3  Publish the entire database to all clients
insecure                     1.0.3  Allow all database writes by default
lepozepo:s3                  5.1.1  Upload files to S3. Allows use of Knox Server-Side.
meteor-platform              1.2.2  Include a standard set of Meteor packages in your app
urigo:angular                0.9.3  The simplest no-conflict way to use AngularJS with Meteor, Meteorite and Atmosphere Smart Packages.
urigo:ionic                  0.4.0* Ionic framework packaged for Meteor.

The latest angular:angular-mocks package does not work with<EMAIL_ADDRESS>I fixed it in pull request #587 by specifying  angular:angular-mocks version.

I had a very similar error with<EMAIL_ADDRESS>after adding<EMAIL_ADDRESS>I also got the familiar 'You've tried to launch Angular twice' error. It resolved after removing angular-animate.
I guess I'll wait until angular-animate is supported to fancy up my project with some animations.

@dotansimha I think it might be that not all of our dependencies are updated to the latest Angular version?  (angular-mocks)?

So, should I attempt to merge #587 locally or assume it's going to be merged into mainline soon?

No, please try to current master branch

sorry, I'm really confused here.  So I should check out angular-meteor master, merge PR 587, build my own package locally, uninstall the angular-meteor package from atmosphere then install my local package so I can have the correct angular version to run my angular meteor app?

no no, just take the current master and run it locally.  without PR 587.
You can see instruction here: https://github.com/urigo/angular-meteor#user-content-run-local-urigoangular-in-your-project

Followed instructions in the link to fork and use local package; on startup I'm still getting the same problem - Uncaught Error: [$injector:unpr] Unknown provider: $$asyncCallbackProvider <- $$asyncCallback <- $animate <- $compile

I'm at wits end - I rolled back to a previous version and angular launches with no problem; the angular launcher in app.js is exactly the same between this version and my old vesion.  Uri, if you're interested I've added you as a collaborator, the app in question is called 'makerActive'.

+1

Fixed in<EMAIL_ADDRESS>Please let me know if that's not the case


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1054

Questions ?
Please refer to the Backport tool documentation


Update option B: Include parts of Bootstrap

By following the current instructions I was unable to add new colors to the $theme-colors variable. To make it work, I had to import variables first.
This won't work (as in "it doesn't result in the creation of bg-<color> classes"):
@import "../node_modules/bootstrap/scss/functions";

$my-theme: (
  "blackhole": #111111,
  "onion": #59316b
);

$theme-colors: map-merge($theme-colors, $my-theme);

@import "../node_modules/bootstrap/scss/variables";
@import "../node_modules/bootstrap/scss/mixins";

This will work:
@import "../node_modules/bootstrap/scss/functions";
@import "../node_modules/bootstrap/scss/variables";

$my-theme: (
  "blackhole": #111111,
  "onion": #59316b
);

$theme-colors: map-merge($theme-colors, $my-theme);

@import "../node_modules/bootstrap/scss/mixins";

I'm not very experienced with Sass, though. Maybe I did something wrong. Please check if you can reproduce this.
I'm using Dart Sass 1.33.0.

That's not the solution indeed. The docs are right but are incomplete: variables overrides have to come before the variable file, but maps modification should come after since they need to exist to be customizable.

Docs in main should be good to go compared to this PR, so closing out.


Created calendar file and added it to feature1

Description
Created calendar feature and new route for it in the navbar. Motivation to create it was for the mentor/mentee dashboards. Will add another commit for underdog devs color scheme.
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have removed unnecessary comments/console logs from my code
[x] I have made corresponding changes to the documentation if necessary (optional)
[x] My changes generate no new warnings
[x] I have checked my code and corrected any misspellings
[x] No duplicate code left within changed files
[x] Size of pull request kept to a minimum
[x] Pull request description clearly describes changes made & motivations for said changes

https://user-images.githubusercontent.com/81526595/141348031-98de173a-df1f-45c6-9902-439ef35be8f2.mp4

Nice! it is good you are using Ant Design library. This is an important piece of the application. Good job.


Security JWT: basic auth with account API

Add account API to basic auth

Closed by https://github.com/jhipster/jhipster-lite/pull/362


Add Jest configuration for snapshotresolver

As I understand, right now CRA only supports a handful of Jest configuration overrides, either by adding them to package.json or adding a jest.config.js to your project.
First question would be, why are you not allowing to just add a jest.config.js and read all of the configuration variables that Jest provides usually, why add just a few of them?
And the more important suggestion, can you add snapshotresolver to this list of allowed customizations? https://jestjs.io/docs/en/configuration#snapshotresolver-string
It has been added with Jest 24 and would really help clean up the codebase a bit, since I don't think it's necessary to have generated code right next to my .tsx, .scss and .test.ts files.. If not, could you at least explain, how the decision was made to not just check for a jest.config.js and then give it to the test runner, so the dev can decide what they want to override or not.

This functionality would be really useful.

I'd really like to have a reaction to this.

Was about to open this issue, but was happy to find it here already! Similar to #3116, this could be a pretty simple fix.

I just checked the source code and this shouldn't be hard to implement. I will try to put together a pull request for this, should be a no brainer.

Bumping to avoid staleness; still very much looking forward to a solution!

Still interested!

Hopefully I did everything right, this is my first PR into any large repository.

Is there any opposition from the CRA team to allowing all options specified in a jest.config.js file to be used and override the defaults? I don't see the harm.

any news about this?

Nobody seems to look at the Merge Request.

Is there any work around for getting this to work with CRA (without the PR)?

didnt it go ahead?

Still interested in this - any update on when it will be added?

It seems like the PR hasn't being viewed :(

I was going to do the same PR until I stumbled on this, it really should be merged, a nice feature to add, and a well-needed one to make folders structure neater.

Any maintainer feedback on this on?

any support in the future for this feature request?


Data is null when a number value is higher than i32

Expected Behavior
We should be able to use "SimpleObject" with a struct that has a field of the type i64
Actual Behavior
When the value of a field of the type i64 exceeds the limit of i32, queries always return null. This is even when we do not include this field in our selected fields
Steps to Reproduce the Problem

Define a struct that uses the "#[derive(SimpleObject)]". This struct must have a field of the type i64.
Define a gql query that has a return type of the simple struct you defined. Make it return an instance of this struct, and make sure to set a high i64 value. Please note that this bug does not appear when the value is low.
Make GQL query that includes the i64 field.
The returning data value is always null.

Specifications

Version:
async-graphql = { version = "4.0.4", features = ["apollo_tracing"] }

Platform:
Windows 11

The GraphQL spec doesn't support int64, I recommend using StringNumber instead.
https://spec.graphql.org/October2021/#sec-Int

The Int scalar type represents a signed 32-bit numeric non-fractional value. Response formats that support a 32-bit integer or a number type should use that type to represent this scalar.

I see. Does this mean that the field of my struct should be a "String"? Or there is another type to use as a part of this limitation?

I recommend using string, StringNumber can help you.
#[derive(SimpleObject)]
struct Obj {
    int64_value: StringNumber<i64>,
}

Thanks, will try  it.

How to import it?
use async_graphql::types::StringNumber;
or
use async_graphql::StringNumber;
Both did not work.

Got it. Needed to add string_number to the features
async-graphql = { version = "4.0.4", features = ["apollo_tracing", "string_number"] }

Cool StringNumber works fine, and it returns a string value. The only thing that I noticed that it does not implement the Default trait, which forces avoiding using the Default trait with the struct that uses it.  Should we have a separate issue for this?

Great idea, I've added it.


Vehicles

How do I spawn vehicles? I've tried everything.

I wouldn't be so sure. Make sure your siding is at least 26 blocks long, inside a depot area and follow the wiki.

What is siding?

What is siding?

You should Watch Jona's Tutorials

https://www.youtube.com/watch?v=KIsuRxNW3Lc&t=480s
The link for the MTR Tutorial


make it possible to print the svg

It is possible to do saveSvg(). It would be great, if one could do printSvg() as well, so one has the option to append the svg to some already existing svg file.

I'm curious, what is the use case for appending an SVG?

I have a map to which I want to add arrows. My workaround was to write to an svg file to see the syntax and then append to the map svg.

OK.  Simply appending the output won't work because everything has to be between the original pair of <svg></svg> tags.
It sounds like you might be doing this manually, so print(d.asSvg()) may do what you want.  Make sure none of the element ids conflict with the original SVG though.  You can use the idPrefix argument of Drawing to prevent conflicts.
If you instead want to cleanly embed the map in a drawSvg drawing, it's a bit involved but you can parse and embed it something like this: https://github.com/cduck/latextools/blob/e12c3bb3a58e03179623a544e289734157db3d77/latextools/convert.py#L208


Light from above ?

Sorry if it's a dumb question but why not having a light from above ?

above ? like everything is white ?

hum more black no ?

Maybe :) but no it's not implemented we only implemented light from a side

I don't know it it's usefull to implement this :/

I close if for now, it's not really useful for neumorphic, and it breaks all the maths inside decorations 😅


[Refactor] Fix min_cumulative_compaction_failure_interval_sec misspell

Signed-off-by: meegoo<EMAIL_ADDRESS>What type of PR is this：

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

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

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

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

Bugfix cherry-pick branch check:

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

[x] 2.5
[ ] 2.4
[ ] 2.3
[ ] 2.2

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.meegoo seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

run starrocks_admit_test

run starrocks_clang-format

@mergify backport branch-2.5


update table statistics after batch write

What problem does this PR solve?
using batch write cannot trigger auto table analyze
What is changed and how it works?
update table statistics after batch write
Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Code changes

Has exported function/method change
Has exported variable/fields change
Has interface methods change
Has persistent data change

Side effects

Possible performance regression
Increased code complexity
Breaking backward compatibility

Related changes

Need to cherry-pick to the release branch
Need to update the documentation
Need to update the tidb-ansible repository
Need to be included in the release note

/run-all-tests

/run-all-tests

/run-all-tests


implement the prominent style for labelLarge and labelMedium in the TextTheme - Material Design 3

Use case
As described in the documentation, in Material Design 3 there are three Label styles:

Label Large
Label Medium
Label Small.

For the Large and the Medium, Material Design provides two different type of weightness: normal and prominent.
But in the text_theme.dart there are only labelLarge and labelMedium, without the prominent style.
Proposal
Implement the prominent style in the TextTheme for the labelLarge and labelMedium.

Hi @alessandrovolpi-puntozero, it seems like on the material site, the weight for prominent is 700, does using fontWeight: FontWeight.w700 not suite your use-case?

Yes, but I think it’s better to have this style directly in the TextScheme instead of manual coding every times.
For example, when I customize the textScheme I write:
textTheme = TextTheme(
  labelLarge: const TextStyle(fontSize: 16.0, fontWeight: FontWeight.w400),
  labelSmall: const TextStyle(fontSize: 12.0, fontWeight: FontWeight.w400)
);

My proposal is something like this:
textTheme = TextTheme(
  labelLarge: const TextStyle(fontSize: 16.0, fontWeight: FontWeight.w400),
  labelLargeProminent: const TextStyle(fontSize: 16.0, fontWeight: FontWeight.w700),
  labelSmall: const TextStyle(fontSize: 12.0, fontWeight: FontWeight.w400)
);

In this way when I want to use this style I can use textScheme.labelLargeProminent


Add user agent header to all requests

Currently the user agent is only being used on the initial resolve request, then switching to the default user agent. This ensures the correct user agent is always used. There is a larger fix in progress which does this is a cleaner way, but the scope of this change is fixing the user agent issue.

Codecov Report

Merging #3335 into master will increase coverage by 0.01%.
The diff coverage is 72.72%.

@@            Coverage Diff             @@
##           master    #3335      +/-   ##
==========================================
+ Coverage   44.83%   44.85%   +0.01%
==========================================
  Files         113      113
  Lines       12346    12361      +15
==========================================
+ Hits         5535     5544       +9
- Misses       5961     5964       +3
- Partials      850      853       +3

Flag
Coverage Δ

#linux
48.77% <73.68%> (+0.01%)
:arrow_up:

#windows
40.25% <72.72%> (+0.02%)
:arrow_up:

Impacted Files
Coverage Δ

remotes/docker/resolver.go
54.54% <66.66%> (+0.06%)
:arrow_up:

remotes/docker/authorizer.go
67.98% <76.92%> (-0.23%)
:arrow_down:

Continue to review full report at Codecov.

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

LGTM


Webpack watch mode causes stacking of callbacks

Hello,
I'm using this plugin on my project and I noticed a weird thing happening, when I run my code in watch mode webpack --watch I noticed that callback function as second argument to this plugin is being called more and more times every time changes are detected and everything is recompiled.
I.e. if I just started in watch mode, then it will be run once, if I then make a change it will be ran twice, and so on... so if I keep working in watch mode it will just keep growing and executing same thing over and over again increasing with each recompile.
I managed to narrow it down to this line - my guess is that compiler.hooks.thisCompilation.tap will keep binding and not releasing previously bound events so they just keep stacking.
If I remove this line and modify following lines like this:
if (compiler.hooks.processAssets) {
  compiler.hooks.processAssets.tapAsync({
    name: plugin.name,
    stage: Compilation.PROCESS_ASSETS_STAGE_ADDITIONAL,
  },
  (_, callback) => this.run(compilation, callback));
} else {
  compiler.hooks.emit.tapAsync(plugin.name, this.run.bind(this));
}

It seems to be working as I expect - it only runs once per compilation. I couldn't understand why compiler.hooks.thisCompilation.tap was needed and would such change continue to work as expected?
I'm happy to open PR with this change but I'm not sure if I understand everything correctly.
Thank you

@bytasv i copied webpack 5 adjustments from https://github.com/FormidableLabs/webpack-stats-plugin/blob/main/lib/stats-writer-plugin.js#L78 together with compiler.hooks.thisCompilation.tap without understanding in depth,
but the example of writing plugins for WP5 also includes that line:
https://webpack.js.org/contribute/writing-a-plugin/
i cant not reproduce this if i run it locally on example inside the plugin doing node_modules/.bin/webpack --watch, maybe you have a different webpack version?

@bytasv i have a feeling that changing it to tapPromise indtead of tapAsync will solve the issue since promise is called only once compared to async, will provide a test code soon

@bytasv can you try using this chamge?
compiler.hooks.thisCompilation.tap(
        plugin.name,
        (compilation) => {
          if (compilation.hooks.processAssets) {
            compilation.hooks.processAssets.tapPromise(
              {
                name: plugin.name,
                stage: Compilation.PROCESS_ASSETS_STAGE_ADDITIONAL,
              },
              () => new Promise((resolve, reject) => this.run(compilation, resolve))
            );
          } else {
            compiler.hooks.emit.tapAsync(plugin.name, this.run.bind(this));
          }
        },
      );

@bytasv your code change is giving me this warning: BREAKING CHANGE: No more changes should happen to Compilation.assets after sealing the Compilation.         Do changes to assets earlier, e. g. in Compilation.hooks.processAssets.         Make sure to select an appropriate stage from Compilation.PROCESS_ASSETS_STAGE_*.
can you check if this code will fix it for you? (using promise instead of async, maybe promise will make it call once)
compiler.hooks.thisCompilation.tap(
        plugin.name,
        (compilation) => {
            compilation.hooks.processAssets.tapPromise(
              {
                name: plugin.name,
                stage: Compilation.PROCESS_ASSETS_STAGE_ADDITIONAL,
              },
              () => new Promise((resolve, reject) => this.run(compilation, resolve))
            );
        },
      );

if not then ill go with your code


[GLUTEN-4917][VL] Refactor CI to build spark.test.home when running UTs

What changes were proposed in this pull request?
spark unit tests requires to set spark.test.home. in fact it only needs several resource files
How was this patch tested?
pass GHA

@JkSelf could you please help to take a look on this?
thanks,
-yuan


Extension should be quiet in workspaces without jest

Describe the bug
When the Jest Test Explorer extension is installed, it tries to discover tests even in a workspace that doesn't use jest. As a result, I see an error in the Test Explorer:

This leads me to disable the Jest Test Explorer extension for these workspaces, which is a pain and doesn't support well when I've switched to jest in a workspace in some branches but other branches still use jasmine.
Can the extension look just once for jest to be installed (perhaps by checking package.json or under node_modules) and quietly no-op if it isn't there?
Tip: The "Jest" extension itself seems to key off of the presence of a jest.config.js file in the workspace. Maybe the extension can do the same thing.
Repro steps
After VS Code has the Jest Test Explorer extension installed:
yarn init -y
code .

Navigate to Test Explorer to see it's already showing an error.
Desktop (please complete the following information):

OS: Windows

Ah, I notice that only the top-left error comes from the Jest Test Explorer. The bottom two come from the Jest extension. I'll file another issue to track those.

I think the offending code is this:
// StandardParser.ts

const isStandard = async (workspaceRoot: string): Promise<boolean> => {
  const packageJsonPath = path.resolve(workspaceRoot, "package.json");
  // TODO we should also check that the jest package is installed, or that we are using a globally installed one.
  // Otherwise, this may not be a Jest project.
  return await exists(packageJsonPath);
};

So I probably should ensure that jest exists in the package.json file (as per my TODO 😉).  I also need to handle the case where users have installed globally and hence it won't be in their package file.  But that is probably a separate issue.

This is hopefully fixed by the latest release (0.7.3).  I'll close this issue, but if you find that the issue persists, please reopen.

Thanks.


[question] How does it compare to postcss-color-function?

Hi,
I've been using postcss/postcss-color-function for long time but it seems a bit stale regarding the standard draft.
I would like to know how does this project compare to postcss-color-function? Any suggestions about migration?
Thanks ♥

Hi @stefanmaric,
There are two things to watch for when switching to this project:

The function is named color-mod and not color, so update those function names accordingly.
CSS Variables cannot be fully supported, so they will attempt to resolve from :root.

Does this help?

@stefanmaric, good news; this plugin won’t run into issues with postcss-custom-properties (which I’ve also been maintaining). As for postcss-color-function, I do hope they can resolve those issues, along with the name (it was changed years ago). Those were the reasons I had to create this project.
I’d be open to a PR for documentation changes, only because I can’t think of what I’d say, and I don’t presently know how people are migrating to this plugin outside of postcss-preset-env. I hope that doesn’t sound too lazy, but if it does and the documentation seems pretty important, then I really would still appreciate a PR. 😄
Also, let me know if you think your original issue has been resolved. If not, of course feel free to keep pinging me and I’ll answer you when a break appears.

Also, let me know if you think your original issue has been resolved. If not, of course feel free to keep pinging me and I’ll answer you when a break appears.

I gave it a shot and migrated a fairly big project in a snap; as you said, just a matter of swapping the plugins and rename color() -> color-mod(). I haven't found any issues so far. :tada:

I don’t presently know how people are migrating to this plugin outside of postcss-preset-env.

Indeed. Probably few people cherry pick postcss plugins and use cssnext or postcss-preset-env instead.


Fix unreleased-commits missing from New Repository Overview

Describe

Closes #6851

Test URLs

Repo with no tags (no button)
https://github.com/refined-github/yolo

Repo with too many unreleased commits
https://github.com/refined-github/sandbox

Repo with some unreleased commits (If no button, check if is latest tag)
https://github.com/refined-github/refined-github

Screenshot


Update morph-date filter

Change morph-date to morph-date-format to be able to use more momentjs features in the future like fromNow(), from(), toNow(), to() and more display functions

I will close this task because I replaced moment with date-fns and I will create a different issue for the new future features of morph-date.


training/train.txt'

Could u please tell us how u solve this problem? I countered with this too.

The training folder is created once you preprocess the data. make sure you run the preprocessing command first.

The training folder is created once you preprocess the data. make sure you run the preprocessing command first.

Thank u for ur warmhearted reply . I solved this problem days ago by change the Numpy 1.16.* to 1.15.4 . It's all the fault of that .
Thank u again sincerely .


BUG: Incorrect total being calculated

I make an offer for 0.01 ETH

Expected:
Total cost with royalty should be 0.011 and displayed offer should be 0.01
Actual:
Top offer is appearing as 0.0099

The issue here is how you are calculating the total amount(offer + royalty).
Instead of 0.01 + (0.01 * 0.1)
it should be 0.01 / 1.1

@rorygeoghegan I'm confused. This value should be correct when coming from the API. When I'm creating the order I pass that calculated value of 0.011. @georgeroman Are we supposed to display a value that is higher the one returned in the API? See this example:
https://mainnet-api-v4.reservoir.tools/tokens?attributes[Shirt]=swat&limit=20&offset=0&collection=crazy-babies-official&sortBy=floorSellValue&sortDirection=asc
Here's how I'm calculating the total cost:
https://github.com/reservoirprotocol/sample-marketplace/blob/dev/lib/calculateOffer.ts#L17-L18
Which is input + ((input * bps)/10000)

@diegoramosxyz This is how the value is computed on the backend: https://github.com/reservoirprotocol/indexer-v3/blob/169687750ce5a4972434be3e3c4ea1e6ebe8e7e7/src/orders/wyvern-v2/save.ts#L525-L532.

@ptrwtts @rorygeoghegan I think the issue is caused by using javascript numbers instead of BigNumbers at the API level. Somewhere in the conversions between BigNumber and number we are losing precision. I believe on my end, the calculations are correct. See equation.

Change this
let fee = userInput.mul(BigNumber.from(bps)).div(BigNumber.from('10000'))
let total = userInput.add(fee)

to
let feePercent = BigNumber.from(bps).div(BigNumber.from('10000'))
let total = userInput.div( BigNumber.from('1').minus(feePercent) )

Fixed here: https://github.com/reservoirprotocol/sample-marketplace/commit/099688c6c751d3d3d8ee3ca2b50b12a35d1facde


add hover text css variable

Is your feature request related to a problem? Please describe.
no
Describe the solution you'd like
add new css variable for on hover text color

Will add in the next version

Will add in the next version

thanks!

Added in version 2.3.4


Bundle all headers and swift files for multi-crate UniFFI setups

In workspaces where UniFFI types are declared in multiple separate crates, UniFFI bindgen generates a set of Swift files, headers and a header map for each Rust crate that declares UniFFI types.
Currently, only the files corresponding to the main crate (from where cargo swift was called) are added. This PR copies all the files to the resulting xcode project.

Due to #53 being merged, the code for accessing the Swift config should be altered slightly. I think this is how we can do it:
for output in uniffi_outputs {
        let config = output.bindings.swift;
        let file_name = config.module_name();
        fs::copy(
            out_dir.join(format!("{file_name}.swift")),
            sources.join(format!("{file_name}.swift")),
        )?;

        fs::copy(
            out_dir.join(config.header_filename()),
            headers.join(config.header_filename()),
        )?;
        fs::copy(
            out_dir.join(config.modulemap_filename()),
            headers.join(config.modulemap_filename()),
        )?;
    }

Please update the code in bindings.rs accordingly for this PR to be merged.
Thank you for your contribution! :)

Unfortunately the swift property is crate-private in the bindings struct. :/
I guess we could just continue to use the old approach for generating the filenames, just with all the different crate names.

Due to #53 being merged, the code for accessing the Swift config should be altered slightly. I think this is how we can do it:
for output in uniffi_outputs {
        let config = output.bindings.swift;
        let file_name = config.module_name();
        fs::copy(
            out_dir.join(format!("{file_name}.swift")),
            sources.join(format!("{file_name}.swift")),
        )?;

        fs::copy(
            out_dir.join(config.header_filename()),
            headers.join(config.header_filename()),
        )?;
        fs::copy(
            out_dir.join(config.modulemap_filename()),
            headers.join(config.modulemap_filename()),
        )?;
    }

Please update the code in bindings.rs accordingly for this PR to be merged.
Thank you for your contribution! :)

Unfortunately the swift property is crate-private in the bindings struct. :/
I guess we could just continue to use the old approach for generating the filenames, just with all the different crate names.

Due to #53 being merged, the code for accessing the Swift config should be altered slightly. I think this is how we can do it:
for output in uniffi_outputs {
        let config = output.bindings.swift;
        let file_name = config.module_name();
        fs::copy(
            out_dir.join(format!("{file_name}.swift")),
            sources.join(format!("{file_name}.swift")),
        )?;

        fs::copy(
            out_dir.join(config.header_filename()),
            headers.join(config.header_filename()),
        )?;
        fs::copy(
            out_dir.join(config.modulemap_filename()),
            headers.join(config.modulemap_filename()),
        )?;
    }

Please update the code in bindings.rs accordingly for this PR to be merged.
Thank you for your contribution! :)

Unfortunately the swift property is crate-private in the bindings struct. :/
I guess we could just continue to use the old approach for generating the filenames, just with all the different crate names.

Ah, you are right. That was an oversight on my side.
Thanks providing an alternative solution!

Thank you so much for creating an end-to-end test project for this feature as well. Great contribution!


Want to use "#" symbol to input in the password field using Robot Framework - However it is considering "#" as comment.

Want to use "#" symbol to input in the password field using Robot Framework - However it is considering "#" as the comment.
I am using Eclipse IDE to develop my robot test.
For all my test passwords starts with "#".
*** Variables ***
${User_Pass}  //input[@type="password" and contains(@name ,"p")]
${Login_Pass}		#123456789
*** Keywords ***
input text    ${User_Pass}    ${Login_Pass}
It is not entering anything inside the password text field. Kindly suggest.

Just add a backward slash( \ ) before your password.
${Login_Pass}    #123456789

Yeah, # starts a comment but it can be escaped with a backslash. For details see the User Guide:
http://robotframework.org/robotframework/latest/RobotFrameworkUserGuide.html#comment

Just add a backward slash( \ ) before your password.
${Login_Pass}    \#123456789

Thank you so much. It worked like a charm.

Yeah, # starts a comment but it can be escaped with a backslash. For details see the User Guide:
http://robotframework.org/robotframework/latest/RobotFrameworkUserGuide.html#comment

Thank you.


Remove RenderObject.rotate

Replace this paragraph with a description of what this PR is changing or adding, and why. Consider including before/after screenshots.
List which issues are fixed by this PR. You must list at least one issue.
If you had to change anything in the flutter/tests repo, include a link to the migration guide as per the breaking change policy.
Pre-launch Checklist

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read the Tree Hygiene wiki page, which explains my responsibilities.
[ ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ ] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

(when submitting a PR like this please either update the PR description, or just delete the template, i'd rather we didn't commit code whose commit description was the template verbatim)

Manual TGP run passed but frob won't let me set the status

@CaseyHillers Is this good enough to manually submit the PR ignoring the Google Testing check?

In future cases, feel free to link the TGP run and submit.


remove unnecessary variable to be mutable

code:after pull origin master
ide:vscode
message:warning: variable does not need to be mutable
image:

Thank you for your attention to RMQTT, this problem will be fixed in the next version.
thank you!
---- Replied Message ----
| From | @.> |
| Date | 08/14/2023 09:49 |
| To | @.> |
| Cc | @.***> |
| Subject | [rmqtt/rmqtt] remove unnecessary variable to be mutable (Issue #31) |
code:after pull origin master
ide:vscode
message⚠ variable does not need to be mutable
image:
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


execve() Failed

Anytime I try to assemble or edit current line, I get a dialog that says execve() Failed. Binary ninja will not save or edit any binaries that I open. There are no errors about it when I run --debug --stderr-log or in the binary ninja gui log. Happens on both the stable and development versions of the personal edition.

Hmm. what platform are you running on?
We shell out to yasm for x86 shellcode (if you try it on any other architecture I suspect it would work). Can you try manually running it on the command-line? (Check in the install path)

Linux archdesktop 4.10.13-1-ARCH #1 SMP PREEMPT Thu Apr 27 12:15:09 CEST 2017 x86_64 GNU/Linux
Just as a note, it does work inside my windows virtual box. I will test this later on my desktop tonight when I get some time. Thanks! Awesome app by the way.

Yasm wasn't installed on my system, after installing it however, it still happens.
✘ desktop@archdesktop  ~/binaryninja  yasm --version
yasm 1.3.0
Compiled on Aug 11 2014.
Copyright (c) 2001-2014 Peter Johnson and other Yasm developers.
Run yasm --license for licensing overview and summary.
desktop@archdesktop  ~/binaryninja  file binaryninja
binaryninja: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.24, BuildID[sha1]=51d67fc12fdc7ef977acf185172181a840c2e7c3, not stripped, with debug_info
desktop@archdesktop  ~/binaryninja  uname -a
Linux archdesktop 4.10.13-1-ARCH #1 SMP PREEMPT Thu Apr 27 12:15:09 CEST 2017 x86_64 GNU/Linux
desktop@archdesktop  ~/binaryninja 

FWIW, you don't need yasm installed. We ship our own. So if it's not finding the one we ship there's something else wrong with permissions or rpath.


First Implementation

📑 Description
First implementation of the Goravel installer
✅ Checks

[ ] My pull request adheres to the code style of this project
[ ] My code requires changes to the documentation
[ ] I have updated the documentation as required
[ ] All the tests have passed

ℹ Additional Information
It's not perfect , still needs some improvements .

Hey ,
Thanks for the review , I'll restyle the UI and implement the sugested comments . Thank you :)

I added all the wanted changes beside the UI. I'll need a little bit more time for it ... :D

I added all the wanted changes beside the UI and cd ** && go run . I'll need a little bit more time for it ... :D

We only need to append the words to print, like: fmt.Println("You can cd into your project and start developing: cd ** && go run .")

Could you please attach the latest UI image here?

I tried to get also the output of cloning the repo and so on but run into errors. I may need some help with that .

The UI looks better! 👍  Please pin me when it's ready to be reviewed again.

@hwbrzzl Well I think it is kinda ready . I tried to improve the UI as much as I could , I added error handling with log.Fatalf and fixed some typos .
The UI of the new command looks like this :

The UI looks like this when an error happens :

I am aware that there may be a lot to improve but at the moment I am not sure if I am capable to do it in a short time.
Thank you very much !


Setting back LOGITECH control

Hi, you made me lose sometime until I realized you made this commit:
862fd9c7df6bf3b57f9895f94e59003bcc460426
How do I set back the controller, I'm not being able to set the environment variable.
thank you

teleop node just like this:

 <!--Teleop -->
    <include file="$(find husky_control)/launch/teleop.launch" />

the husky nodes in general like this:
<arg name="port" default="$(optenv HUSKY_PORT /dev/HUSKY)" />
  <arg name="robot_namespace" default="/"/>
  <arg name="laser_enabled" default="$(optenv HUSKY_LMS1XX_ENABLED true)"/>
  <arg name="kinect_enabled" default="$(optenv HUSKY_KINECT_ENABLED false)"/>
  <arg name="urdf_extras" default="$(optenv HUSKY_URDF_EXTRAS)"/>

  <param name="robot_description" command="$(find xacro)/xacro '$(find husky_description)/urdf/husky.urdf.xacro'
    --inorder
    robot_namespace:=$(arg robot_namespace)
    laser_enabled:=$(arg laser_enabled)
    kinect_enabled:=$(arg kinect_enabled)
    urdf_extras:=$(arg urdf_extras)
    " />

	<node name="robot_state_publisher" pkg="robot_state_publisher" type="robot_state_publisher" />

	<!-- Laser LMS 151 -->
	<arg name="host" default="<IP_ADDRESS>" />
	<node pkg="lms1xx" name="lms1xx" type="LMS1xx_node" output="screen">
	<param name="host" value="$(arg host)" />
	</node>
        <node pkg="tf" type="static_transform_publisher" name="laser_base_link" args="0.39 0 0.36 0 0 0  /base_link /laser 10"/>
    <!-- Husky harware driver -->
    <node pkg="husky_base" type="husky_node" name="husky_node">
        <rosparam subst_value="true">
            port: $(arg port)

            control_frequency: 10.0
            diagnostic_frequency: 1.0

            max_acceleration: 0.5
            max_speed: 0.5
            wheel_diameter: 0.3555
            polling_timeout: 10.0
        </rosparam>
    </node>

Where do you do export HUSKY_LOGITECH=1?  Is teleop.launch started by robot_upstart or in the foreground?

As Tony said, you should be able to re-enable the Logitech if you are using Kinetic by exporting HUSKY_LOGITECH=1 (as stated above).  You will want to do this in /etc/ros/setup.bash.  If you've done this you can tell if it started up properly by running "rosparam get /joy_teleop/joy_node/dev".  If this says "/dev/input/js0", then it is trying to use the Logitech properly.
If that is the case, you will need to make sure the controller is connected and showing up as js0.  If you have python-ds4drv installed at the same time, it will usually take js0, which moves the Logitech controller to js1.  Try uninstalling python-ds4drv if it is installed.

Please let us know if you have resolved the issue and we can close this ticket.

As we have not heard back and there is an environment variable to solve this issue, we will be closing this ticket.  If you are still having issues after following the steps above, please open another ticket.


Improve or allow customization of the Electron LoopbackWebServer response pages

The pages presented to the user for successful sign-in and error authentication error are plain white pages that contrast with the iTwin UI standards and/or authenticating application.

Please allow for a way to customize the look of this page or make it adhere to iTwin UI standards.

@RaphaelMelancon I definitely agree with the need to change this log-out page as it doesn't look great. However, it is driven by IMS (Bentley's IdP) so this won't be a simple change within the library. We will need to raise this internally.

@RaphaelMelancon I definitely agree with the need to change this log-out page as it doesn't look great. However, it is driven by IMS (Bentley's IdP) so this won't be a simple change within the library. We will need to raise this internally.

We actually control the "signed in, now return to your app" page in both node and electron packages. Look at the snazzy page fly.io presents - something like this would be awesome:


Middle relays

I just found this repo and the Reddit post. I hope there is still interest in this project.
One of the key features of Tor is that it routes the traffic through random nodes, for better security. Those nodes require open ports, as the Tor network is baesd on TCP.
However, wireguard uses UDP and can run behind firewalls. This unlocks the possibility of allowing virtually anyone to run such a node at home.
There is this project that implements P2P connectivity using wireguard: https://github.com/jwhited/wgsd
So, probably a wireguard-based alternative to Tor is possible, with even better performance, and the added benefit of supporting UDP traffic (Tor does not support UDP traffic to pass through it).
Edit: Forgot to mention that Tor also has the Snowflake service, which allows middle nodes to use WebRTC and run behind firewall.
Edit2: I think Tailscale uses a similar approach to wgsd for P2P connectivity.

Thank you for the input. I have some ideas on how it could be done without the need of a custom protocol. But there are some points that need some more research. I will probably open a discussion in r/tor about this, as I really believe that there will be performance gains switching to UDP. While writing this, I found this article from Tor showing with plans to switch to UDP in 2011: https://blog.torproject.org/moving-tor-datagram-transport/


Suggestion: Add pilers

Suggestion: Include the new pilers and belt sprayers into this mod so they can be dropped inline onto a belt the same way splitters are.

please?

I can't promise that it will be ready soon, as the current implementation is biased toward Splitter.

I applied Splitter's code directly to Plier and it seemed to work somehow, so I tried to support Plier in version 1.1.1

Those are wonderful news, thanks!!!


Chatdown Designer

Tool
Chatdown
Currently, we have to write down all the chatdown scripts manually.
Suggestion
I think it would enhance the tool if we can have ChatDown Designer similar to what we have in AdaptiveCards now.

We are working on design tooling that will aid in visually designing conversations and bots.  There will be some functionality in that tool that will start to address this feature request.


API Access: 404 on group search url

On the Community Translation Options page:
API Access:

Retrieve statistical data
Download translations
Import translations from packages
Update package translations

gives a 404 (/index.php/ccm/dialogs/group/search). Shouldn't that url rather be: /index.php/dashboard/users/groups?

The whole stuff related to API is going to be revisited, it's not yet ready

Addressed by #21


Updated node-cache-manager-ioredis

Hi,
I went ahead and did a Typescript rewrite of https://github.com/dabroek/node-cache-manager-ioredis here https://github.com/Tirke/node-cache-manager-ioredis and it is published here https://www.npmjs.com/package/@tirke/node-cache-manager-ioredis. If you want to replace the README link to this package instead of the old one, feel free.

Closed by #200


Adding celerybeat.pid to gitignore

Just a quick PR to clean up the local git arena.

@mjstealey Can you look at this small change and see if you can +1?


Fixing issue #34, naming validation and general refactoring on the bicep codebase (new region deployment)

Included naming module to validate names, included tagging mechanism, refactored a few files to consolidate required parameters, parameterized the numeric suffix, minor changes to support optionally creating the subnet for CICD agent, modularize private DNS zone creation and related VNET links and A records, parameterized setting availability zone for created VMs.

Finally, all checks were successful (there are a couple of minor issues we should probably take care on the CI/CD process). Please note I had to switch the configured region to be EastUS for the deployment to go through and delete existing deployments from WestUS2.

@nianton I had a few questions, but nothing major.

@petemessina did you have a chance to connect with @nianton ?

closes #34


Update default Elemental version to 0.85

The makefile comments as well as instructions seemed to indicate the default version should be 0.85, rather than 0.84-p1

Hello Thomas,
Thanks for the catch. I edited the Makefile directly before noticing that you issued a pull
request. So the change has been made.
Thanks!
Barry

From: Thomas Shields<EMAIL_ADDRESS>Sent: Saturday, August 20, 2016 9:03 PM
To: smallk/smallk
Subject: [smallk/smallk] Update default Elemental version to 0.85 (#6)
The makefile comments as well as instructions seemed to indicate the default version should be 0.85, rather than 0.84-p1

You can view, comment on, or merge this pull request online at:
https://github.com/smallk/smallk/pull/6
[https://avatars1.githubusercontent.com/u/821920?v=3&s=400]https://github.com/smallk/smallk/pull/6
Update default Elemental version to 0.85 by thomas4g · Pull Request #6 · smallk/smallkhttps://github.com/smallk/smallk/pull/6
github.com
The makefile comments as well as instructions seemed to indicate the default version should be 0.85, rather than 0.84-p1
Commit Summary

Update default Elemental version to 0.85

File Changes

M Makefilehttps://github.com/smallk/smallk/pull/6/files#diff-0 (2)

Patch Links:

https://github.com/smallk/smallk/pull/6.patch
https://github.com/smallk/smallk/pull/6.diff

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/smallk/smallk/pull/6, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACnQaBNwaMHnn3fvNLpOsWYR7Ys1fD1_ks5qh6PGgaJpZM4JpMx1.


Pin memory thread exited unexpectedly

hi！
When I wanted to test my picture, this problem occurred,
the demo.sh is：
python main.py --data_test Demo --scale 4 --pre_train ../experiment/model/EDSR_baseline_x4.pt --test_only --save_results
When I want to test my picture, I have this problem, I hope to get your answer,
thank you very much
@thstkdgus35

Sorry, the problem has been solved, the memory is over.


Move hard-coded Coronavirus pages content from controllers and views to locale file

Trello: https://trello.com/c/Zf13e2Wy
What?
Whilst the locale file card was being worked on, more content was added to views and controllers.
This change moves does another audit of controllers, views etc, for sub-sections, announcements, and timeline entries and makes sure all of the content has been moved to the locale file.
Content moved

[x] Summary page views
[x] Announcements controller
[x] Announcements views
[x] Reorder Announcements controller
[x] Reorder Announcements views
[x] Timeline entries controller
[x] Timeline entries views
[x] Reorder Timeline entries controller
[x] Reorder Timeline entries views
[x] Subsections controller
[x] Subsections views
[x] Reorder Subsections controller
[x] Reorder Subsections views
[x] Livestream controller
[x] Livestream views
[x] Pages controller
[x] Feature tests

⚠ This repo is Continuously Deployed: make sure you follow the guidance ⚠

As per our discussion I had a play around with moving the translation keys so the key always mapped logically back to the place it was used (view or controller).
The commit is here with more details in the commit message: https://github.com/alphagov/collections-publisher/commit/5a377ece92fc8ff1dfb4fcf341161a1bce26b3ec
Main thing I'm looking for with the change above is to see if we can establish agreement on a) a logical mapping is beneficial and scalable and b) is the one I've proposed good. It doesn't have to go in with this PR.

@kevindew Thanks for your review. I've had a look at restructuring the content in the locale file. What I've found out is that a lot of the confusion comes from how the content for "Edit something else" page (i.e. the "prepare" page) and the index page was spread throughout the file. I also found out that none of the view partials in the "shared" folder were actually being shared. So as the view and controller structure is still a bit all over the place, I've tried structuring the content by "screen". i.e. the page that the user sees. So for example,  the content is grouped under:

index page
summary page
new timeline entry page
edit announcement page
reorder sub-sections page
livestream page
edit something else page
etc

Hopefully this will make it easy to go straight from the page needing to be updated to the section in the locale page that contains the content.
This means that there are a few places where content is duplicated. For example, the button text for "Publish" appears in three places, but I thought that it was preferable to keep the livestream, prepare and summary pages separate from each other so that the content is easier to find, rather than trying to DRY them up and making a mess.
Also, the only partials that are being shared are the forms for the new and edit pages for announcements, timeline entries and sub-sections. I've put them in as their own entry for now as this seemed like the tidiest option.

Thanks for this @leenagupte and great job spotting the shared folder isn't actually used for any sharing. Nice one on the helpers.t too.
I've been trying to understand the screen organisation system you've introduced. There are a few bits that have confused me:

if things are screens then what is a form? should all shared things have their own keys?
it seems to mix internal terminology with external terminology - for example we have a keys for sub_sections (which are known externally as accordions) but then renames to prepare to something_else_from_github - and introduce new terminology such as coronavirus.summary
I don't really understand the logic behind the flash message organisation, some seem to be defined based on the screen they'll be seen on, others not, some seem to be embedded in actions keys

I do wonder if it might have been better to put together a quick proposal of this new approach and discuss before applying it everywhere, as I feel pretty lousy about asking questions on the fundamentals when there are 16 commits of implementation - nor can I imagine that you want to be questioned after doing all that. I'm also assuming, given you've taken a new approach, that you didn't like the idea of doing this in an approach that was consistent with Content Publisher?

This means that there are a few places where content is duplicated. For example, the button text for "Publish" appears in three places, but I thought that it was preferable to keep the livestream, prepare and summary pages separate from each other so that the content is easier to find, rather than trying to DRY them up and making a mess.

Yup, repeating is fine. It seems much less dangerous than having the same key used in multiple places and having someone think they're only editing it in one place.

I didn't follow the content-publisher of naming keys after controllers (is that right?) as that assumes that the controller/view patterns make sense, and I don't think that's true for coronavirus pages.  Also I had a look at your example commit, but couldn't see that pattern replicated (using "controller" and "view" in the key names) in content-publisher. Also it tightly couples content to code rather than where it's seen, which I don't think is a good idea for coronavirus pages.
As I mentioned previously, I find PagesController confusing. From looking at it I can't tell what each action really does, so I didn't want to perpetuate that confusion in the locale file. For example, the PagesController contains actions for the index page, summary pages, and "something else" page, but not the live-stream page or the sub-section pages (I'm excluding announcements and timeline entries from this as they follow the pattern established for sub-sections). I believe that PagesController needs to be broken up and the "something else" stuff should be moved out into their own controller etc. However, I think that should be done in a separate PR as the content changes in this one have already snowballed at bit.
The aim is group content by what the user sees and what they were doing. i.e. what page does the content appear on? Which action errored etc. So the "delete subsection" action happens on the summary page, so it and it's associated messages (success, failed) appear there. Edit subsection has it's own page, so everything associated with what the user is doing on that page is grouped together, even the success message even though that's shown on the summary page.
For complex pages like summary pages, the content is grouped by the section it appears on the page, hence the "actions" key.
To fully understand what bits of the code the content related to, I had to pull apart the locale file. I resaved it in 16 commits, because saving it way that was easier for me. I need a visual to understand what the restructure would look like, hence the restructuring of the file before pushing it up for a discussion.
The original scope of this PR was just to make sure all of the announcements, sub-sections and timeline entries content was moved to the locale file, but these changes have now far exceeded that.
I think rather than continuing with this PR, the changes should be broken up into separate pieces. So rather than doing this, I think for example, the "prepare"/"something else" page should be renamed and split out from the PagesController, and it's content and views consolidated (I don't think it needs to be split into 5 partials). Ditto the live_stream changes, as these seem to be the least contentious. Then the announcements, timeline entries and sub-sections can be updated in their own individual PRs rather than in one go. It will be easier to focus on these sections once the noise of the  "prepare"/"something else" and live stream fixes have been removed.

I didn't follow the content-publisher of naming keys after controllers (is that right?) as that assumes that the controller/view patterns make sense, and I don't think that's true for coronavirus pages. Also I had a look at your example commit, but couldn't see that pattern replicated (using "controller" and "view" in the key names) in content-publisher. Also it tightly couples content to code rather than where it's seen, which I don't think is a good idea for coronavirus pages.

Yeah, the content publisher approach is to have the keys correlate with the view structure. If you have a view of app/views/image/edit.html.erb then you have locale keys prefixed with "en.image.edit" and that correlates to a file stored at config/locales/view/edit.yml.
The key -> view naming structure is a common Rails convention, in fact (In googling this) I just learnt that they actually have a shorthand functionality that makes use of this: https://guides.rubyonrails.org/i18n.html#lazy-lookup. It actually seems to be that we initially followed that convention in this app with the initial commit adding it but looks like the subsequent commits lost it.
I think there are always going to be scenarios where locale file mapping is challenging to understand and I think the key advantage you get with doing it based on file structures is that there isn't ambiguity to this organisation (which I see is how we got into this problem in the first place).

As I mentioned previously, I find PagesController confusing. From looking at it I can't tell what each action really does, so I didn't want to perpetuate that confusion in the locale file. For example, the PagesController contains actions for the index page, summary pages, and "something else" page, but not the live-stream page or the sub-section pages (I'm excluding announcements and timeline entries from this as they follow the pattern established for sub-sections). I believe that PagesController needs to be broken up and the "something else" stuff should be moved out into their own controller etc. However, I think that should be done in a separate PR as the content changes in this one have already snowballed at bit.
The aim is to group content by what the user sees and what they were doing. i.e. what page does the content appear on? Which action errored etc. So the "delete subsection" action happens on the summary page, so it and it's associated messages (success, failed) appear there. Edit subsection has it's own page, so everything associated with what the user is doing on that page is grouped together, even the success message even though that's shown on the summary page.
For complex pages like summary pages, the content is grouped by the section it appears on the page, hence the "actions" key.
To fully understand what bits of the code the content related to, I had to pull apart the locale file. I resaved it in 16 commits, because saving it way that was easier for me. I need a visual to understand what the restructure would look like, hence the restructuring of the file before pushing it up for a discussion.

Thanks, that all makes sense. The situation I'm a bit worried about is that this new structure is that it's somewhat arbitrary organisation so it may just slip back into the same problems of before. Maybe it won't?

The original scope of this PR was just to make sure all of the announcements, sub-sections and timeline entries content was moved to the locale file, but these changes have now far exceeded that.
I think rather than continuing with this PR, the changes should be broken up into separate pieces. So rather than doing this, I think for example, the "prepare"/"something else" page should be renamed and split out from the PagesController, and it's content and views consolidated (I don't think it needs to be split into 5 partials). Ditto the live_stream changes, as these seem to be the least contentious. Then the announcements, timeline entries and sub-sections can be updated in their own individual PRs rather than in one go. It will be easier to focus on these sections once the noise of the "prepare"/"something else" and live stream fixes have been removed.

Cool, that sounds good 👍

Closing as this PR is going to be broken up into smaller chunks.


Document that client-go is not yet compatible with dep

@sttts could you proof read this? Thank you.

This change is

cc @rickypai @danderson

/lgtm

Thank you both for the review.


[Yarn workspaces] Unable to use a pre-built workspace package

Describe the bug
I have yarn workspaces set up and I want to include one of my packages within my SvelteKit application. My svelte.config.js contains the following Vite configuration:
vite: () => ({
    esbuild: {
	 exclude: ['my-package']
    },
    ssr: {
         external: ['my-package']
    }
})

my-package generates  Commonjs code and uses a normal Typescript compiler based on the following tsconfig.json file:
{
    "compilerOptions": {
      "target": "ES6",
      "module": "commonjs",
      "declaration": true,
      "declarationMap": true,
      "removeComments": true,
      "experimentalDecorators": true,
      "emitDecoratorMetadata": true,
      "inlineSourceMap": true,
      "outDir": "./dist",
      "baseUrl": "./",
      "incremental": true,
      "importsNotUsedAsValues": "error",
      "lib": [
        "es2019"
      ],

    },
    "include": ["src/**/*.ts"],
    "exclude": ["node_modules", "dist"]
  }

my-package contains also the following package.json file:
{
  "name": "my-package",
  "version": "0.0.0",
  "main": "./dist/index.js",
  "types": "./dist/index.d.ts",
  "typings": "./dist/index.d.ts",
  "svelte": "./src/index.ts",
  "scripts": {
    "build": "nest build",
    "dev": "ENV=development nest build --watch"
  },
  "dependencies": {
    "@nestjs/common": "^7.4.4",
    "@nestjs/core": "^7.4.4",
    "@nestjs/swagger": "^4.8.0",
    "typeorm": "^0.2.28",
    "typescript": "^4.0.3"
  },
  "devDependencies": {
    "@nestjs/cli": "^7.6.0",
    "class-validator": "^0.12.2"
  },
  "private": true,
  "license": "UNLICENSED"
}

The current behaviour is that Vite is ignoring strangely this configuration and keeps treating my-package as a local dependency by including it into the build process made by esbuild (which is used by Vite and does not support the Typescript emitDecoratorMetadata feature). As a result, the Typescript files of my-package loaded on the browser do not contain the metadata tags.
The expected behaviour is that my-package should be treated as an external dependency and thus should not be built by esbuild. So that I can get the metadata tags in the Typescript files of my-package when they are loaded on the browser.
Reproduction
I have the following login.ts file in my-package:
import {IsEmail, IsNotEmpty} from 'class-validator'

export class Login {
    @IsNotEmpty() @IsEmail()
    mail: string

    @IsNotEmpty()
    password: string

    constructor(init?: Partial<Login>) {
        Object.assign(this, init)
    }
}

The pre-built login.js file that should be loaded on the browser containing the metadata tags is :
"use strict";
var __decorate = (this && this.__decorate) || function (decorators, target, key, desc) {
    var c = arguments.length, r = c < 3 ? target : desc === null ? desc = Object.getOwnPropertyDescriptor(target, key) : desc, d;
    if (typeof Reflect === "object" && typeof Reflect.decorate === "function") r = Reflect.decorate(decorators, target, key, desc);
    else for (var i = decorators.length - 1; i >= 0; i--) if (d = decorators[i]) r = (c < 3 ? d(r) : c > 3 ? d(target, key, r) : d(target, key)) || r;
    return c > 3 && r && Object.defineProperty(target, key, r), r;
};
var __metadata = (this && this.__metadata) || function (k, v) {
    if (typeof Reflect === "object" && typeof Reflect.metadata === "function") return Reflect.metadata(k, v);
};
Object.defineProperty(exports, "__esModule", { value: true });
exports.Login = void 0;
const class_validator_1 = require("class-validator");
let Login = class Login {
    constructor(init) {
        Object.assign(this, init);
    }
};
__decorate([
    class_validator_1.IsNotEmpty(),
    class_validator_1.IsEmail(),
    __metadata("design:type", String)
], Login.prototype, "mail", void 0);
__decorate([
    class_validator_1.IsNotEmpty(),
    __metadata("design:type", String)
], Login.prototype, "password", void 0);
Login = __decorate([
    __metadata("design:paramtypes", [Object])
], Login);
exports.Login = Login;

What currently is being loaded on the browser is : (which was included in the esbuild process by Vite)
var __defProp = Object.defineProperty;
var __getOwnPropDesc = Object.getOwnPropertyDescriptor;
var __decorateClass = (decorators, target, key, kind) => {
  var result = kind > 1 ? void 0 : kind ? __getOwnPropDesc(target, key) : target;
  for (var i = decorators.length - 1, decorator; i >= 0; i--)
    if (decorator = decorators[i])
      result = (kind ? decorator(target, key, result) : decorator(result)) || result;
  if (kind && result)
    __defProp(target, key, result);
  return result;
};
import { IsEmail, IsNotEmpty } from "/node_modules/.vite/class-validator.js?v=4f041318";
export let Login = class {
  constructor(init) {
    Object.assign(this, init);
  }
};
__decorateClass([
  IsNotEmpty(),
  IsEmail()
], Login.prototype, "mail", 2);
__decorateClass([
  IsNotEmpty()
], Login.prototype, "password", 2);

System Info
node 14
yarn 1.18

Used Package Manager
yarn
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

Also encountered this problem, have you solved it now?

Also encountered this problem, have you solved it now?

Unfortunately, not yet. I did not receive any support about the topic as you can see.

Please provide a repro repo/stackblitz to showcase the issue. Currently the code blocks alone is hard to setup for one to look into it. Though for this specific issue, it looks like you need to apply the pattern as noted in https://vitejs.dev/guide/dep-pre-bundling.html#monorepos-and-linked-dependencies recently. Let us know if that works for you, if it does we can close this without a repro.


Can't open files when there are multiple folders in workspace

When I have several folders in the workspace (File->Add folder to workspace), the extension still searches correctly in the terminal, but it can't open the selected file when pressing enter. Strangely enough, clicking on the path+line link in the terminal works as intended.

I'm running on OSX VS Code Version: 1.63.2, FindItFaster v0.0.16.
The list folders command correctly displays all folders.
This happens when using "find within files". The path is show relative to one of the working dirs. When using find files, paths show absolute path and they work.

Hi bisho, thanks for reporting! I've played around with this a bit and can't reproduce. You definitely shouldn't be seeing a relative path in there when you have a multi-root workspace (thanks for mentioning that!), so that's a bug indeed. Would you mind sharing:

the output of your workspace configuration; that is, any (anonymized / redacted) paths under folders? I'd like to understand if maybe there's something there that stands out to me like spaces, relative paths, etc.
if you have any paths added to find-it-faster.general.additionalSearchLocations that would be good to know.
if you could also share the (anonymized) output of the "list search locations" command, that would be super helpful.

Thanks so much!

I tried to repro, but now the "find within files" doesn't show one of the folders added.

I didn't have any paths in find-it-faster.general.additionalSearchLocations
The list search locations produces:

----------
The following files are on your search path:
- /Users/bisho/Work/coding/test/project_a
- /Users/bisho/Work/coding/test/project_b

Paths added because they're the working directory:
- <none>
Paths added because they're defined in the workspace:
- /Users/bisho/Work/coding/test/project_a
- /Users/bisho/Work/coding/test/project_b
Paths added because they're the specified in the settings:
- <none>
----------

Repro steps:

I have created two project folders, with foo and bar files that contain foo and bar:

./project_b
./project_b/b
./project_b/b/foo
./project_b/b/bar
./project_a
./project_a/a
./project_a/a/foo
./project_a/a/bar

I open project_a folder in vscode.
I add project_b folder to workspace
Search files by name shows both folders.
Search within files only shows files in project_a

If I add them in different order, first open folder project_b, then add folder project_a, then search within files only shows from project_b.

More info on this. When I have a single folder open, both search files / search within files display relative paths. As soon as another folder is added to the workspace, the search files correctly switches to absolute paths, but search within files does not...

Changed find_within_files.sh to run with -x for debugging purposes:
The issue seems to be that . shared.sh fails, pwd is not the current folder.
::: Terminal allocated for FindItFaster. Do not use. ::: /Users/bisho/.vscode/extensions/tomrijndorp.find-it-faster-0.0.16/find_within_files.sh  '/Users/bisho/Work/coding/test/project_a' '/Users/bisho/Work/coding/test/project_b'
+ set -uo pipefail
+ . shared.sh
/Users/bisho/.vscode/extensions/tomrijndorp.find-it-faster-0.0.16/find_within_files.sh: line 4: shared.sh: No such file or directory

That causes array_join to fail later.

Hi bisho, this is awesome, thanks for looking into it in so much detail! I'm having a bit of a crazy week this week, but next week I should have some time to look into it address this. Thank you!

Note I suggested a PR https://github.com/tomrijndorp/vscode-finditfaster/pull/13 to fix this :) It is working for me locally!

Hah, that's a great catch! I now realize that the reason shared.sh would load for me was that generally when I'm working on the extension, the folder that contains shared.sh is my PWD 🤦. I somehow didn't catch this when I was testing my latest release, so thanks!
I think your solution makes sense, but I'm going to have to do some testing before I can merge. For one, realpath is not available by default on Mac OS. Thanks for your patience :)

Alright, version 0.0.17 is now released! Thanks again, and do please let me know if things don't work as you'd expect!

Thanks to you!!! I can't live without this extension :)


Different SMT files over executions of Verus - different trigger ordering, different number of check-sat

This GC example( f78bfcb81caaf1db6712ac52de905085f749d628 ) is about using a 32-bit integer as an array of 16 elements. When I uncomment lines from 147 to 152, the verification result becomes unstable. Yi and I were looking into this example and found that Verus generates two different SMT files over separate runs. These SMT files have some different ordering of triggers and a different number of check-sat.
To be specific, in log_fail.smt file, when I manually flip the order of these two triggers(to make the ordering the same as in log_success.smt), Z3 suddenly returns unsat instead of unknown.
:pattern ((get_bit.? (I bv2@) loc2$))      ;; line 1971
:pattern ((get_bit.? (I bv@) loc2$))

Also, log_fail.smt has one more check-sat. Here is the diff of that part.
<   (get-model)                                        ;; line 2303
<   (assert
<    (not %%location_label%%0)
<   )
<   (assert
<    %%query%%
<   )
<   (set-option :rlimit 0)
<   (check-sat)
<   (set-option :rlimit 0)

Unmodified SMT files are log_success.smt and log_fail.smt
log_fail.txt
log_success.txt
I will try to make small examples that reproduce these two issues(different trigger ordering and a different number of check-sat) separately.

Does https://github.com/secure-foundations/verus/commit/b95fff1cd3c2af6386a172098a1f9055b0e77ead eliminate the different trigger orderings?

Yes, the above example now produces the same SMT file every time(over 50 runs). Thanks!

If I remember correctly, the different number of check-sat was due to the Verus' additional effort when it faces verification failure. In the above example, a particular trigger ordering made verification fail, and the failure lead to a different number of check-sat.