Proposal: Enable multi-zonal control plane component spread by default

We anticipate multi-zonal spread of control plane components to be a common requirement (e.g. https://github.com/openshift/hypershift/issues/227).
One approach that we think may satisfy the majority use case is to define multi-zonal in terms of anti-affinity rules based on the kubernetes.io/hostname and topology.kubernetes.io/zone topology keys for pod anti-affinity. This proposal is to set default anti-affinity rules for control plane components deployments like:
podAntiAffinity:
  requiredDuringSchedulingIgnoredDuringExecution:
    - labelSelector:
        matchExpressions:
          - key: app
            operator: In
            values: [...]
      topologyKey: "kubernetes.io/hostname"
    - labelSelector:
        matchExpressions:
          - key: app
            operator: In
            values: [...]
      topologyKey: "topology.kubernetes.io/zone"

These defaults would apply regardless of HA mode on the hostedcluster and would ensure that basic multi-zone spreading is implemented by default. If this satisfies the known use cases, we don't need any generic configuration API for anti-affinity at this time.
TODO: Define the exhaustive list of control plane components which to which these defaults will be applied.

Key components that need these defined:
ignition-server
cloud-controller-manager
cluster-policy-controller
kube-apiserver
kube-controller-manager
kube-scheduler
oauth-openshift
openshift-apiserver
openshift-controller-manager
openshift-oauth-apiserver

/assign @csrwng

Tracked in https://issues.redhat.com/browse/HOSTEDCP-195


Rendered manifests contain a resource that already exists. Unable to continue with insta

Hi Team , Could someone please help on the following issue.
I am trying to install helm-chart but facing issue as below:
Type     Reason             Age                  From           Message

Warning  FailedReleaseSync  4m22s (x7 over 58m)  helm-operator  synchronization of release '' in namespace '' failed: installation failed: rendered manifests contain a resource that already exists. Unable to continue with install: existing resource conflict: namespace: name_space, name: helm_name, existing_kind: /v1, Kind=Service, new_kind: /v1, Kind=Service
helm version : version.BuildInfo{Version:"v3.9.0", GitCommit:"7ceeda6c585217a19a1131663d8cd1f7d641b2a7", GitTreeState:"clean", GoVersion:"go1.18.2"}
kubectl version: Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.3", GitCommit:"816c97ab8cff8a1c72eccca1026f7820e93e0d25", GitTreeState:"clean", BuildDate:"2022-01-25T21:17:57Z", GoVersion:"go1.17.6", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.7", GitCommit:"392a7e3e62996d05ada2157090ee6ed616af1a8c", GitTreeState:"clean", BuildDate:"2021-11-15T08:35:15Z", GoVersion:"go1.15.12", Compiler:"gc", Platform:"linux/amd64"}

Thankyou , was able to resolve this .


Typing is extremely slow

Type: Performance Issue
Performance issue happens when running Transformers code file, and occurs once the code chunks are run. Nothing can be done to stop the typing lag, even with only 30-40% CPU and 50% GPU util.
VS Code version: Code 1.88.1 (e170252f762678dec6ca2cc69aba1570769a5d39, 2024-04-10T17:41:02.734Z)
OS version: Windows_NT x64 10.0.22631
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-10980HK CPU @ 2.40GHz (16 x 3096)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
31.77GB (16.26GB free)

Process Argv
--crash-reporter-id d094dff2-1d1a-49ea-874d-c9170f7890f7

Screen Reader
no

VM
0%

Process Info
CPU %	Mem MB	   PID	Process
    0	   125	 18900	code main
    2	  1095	  1244	   window
    0	   108	  2640	   utility-process
    0	    83	  6252	fileWatcher [2]
    0	    26	 19120	   crashpad-handler
    0	   147	 19220	   gpu-process
    0	    40	 19332	   utility-network-service
    0	   444	 19496	window [1] (● [1_1]_Transformer_from_Scratch_(exercises).ipynb - Visual Studio Code)
    0	   153	 19712	extensionHost [1]
    0	    80	  1400	     "C:\Users\Khang\AppData\Local\Programs\Microsoft VS Code\Code.exe" "c:\Users\Khang\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\json-language-features\server\dist\node\jsonServerMain" --node-ipc --clientProcessId=19712
    0	  1442	  7152	     c:\Users\Khang\anaconda3\envs\ARENA\python.exe -m ipykernel_launcher --f=c:\Users\Khang\AppData\Roaming\jupyter\runtime\kernel-v2-19712ubGp71rPtnK0.json
    0	     6	  7188	       C:\WINDOWS\system32\conhost.exe 0x4
    0	    84	  8760	     electron-nodejs (server.js )
    0	     8	 20644	     c:\Users\Khang\anaconda3\envs\ARENA\python.exe c:\Users\Khang\.vscode\extensions\ms-toolsai.jupyter-2024.3.1-win32-x64\pythonFiles\vscode_datascience_helpers\kernel_interrupt_daemon.py --ppid 19712
    0	     6	 20208	       C:\WINDOWS\system32\conhost.exe 0x4
    0	   523	 21140	     electron-nodejs (bundle.js )
    0	    15	 27164	     c:\Users\Khang\AppData\Local\Programs\Python\Python310\python.exe c:\Users\Khang\.vscode\extensions\ms-python.isort-2023.10.1\bundled\tool\lsp_server.py
    0	     6	 15536	       C:\WINDOWS\system32\conhost.exe 0x4
    0	   312	 20000	   window
    0	   106	 20252	shared-process
    0	    77	 20308	fileWatcher [1]
    0	    79	 20500	ptyHost
    0	     7	 20672	     conpty-agent
    0	    73	 20820	     C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -noexit -command "try { . \"c:\Users\Khang\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\contrib\terminal\browser\media\shellIntegration.ps1\" } catch {}"
    0	     7	 26952	     conpty-agent
    0	    73	 29336	     C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -noexit -command "try { . \"c:\Users\Khang\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\contrib\terminal\browser\media\shellIntegration.ps1\" } catch {}"
    0	   158	 20960	window [2] ([1_1]_Transformer_from_Scratch_(exercises).ipynb - Visual Studio Code)
    0	   112	 24348	window [3] (Issue Reporter)
    0	   104	 28636	extensionHost [2]
    0	    82	 24896	     electron-nodejs (bundle.js )

Workspace Info
;

Extensions (34)

Extension
Author (truncated)
Version

vscode-django
bat
1.15.0

doxdocgen
csc
1.4.0

python-environment-manager
don
1.2.4

python-extension-pack
don
1.7.0

vsc-material-theme
Equ
34.3.1

vsc-material-theme-icons
equ
3.6.0

prettier-vscode
esb
10.4.0

better-cpp-syntax
jef
1.17.2

vsc-python-indent
Kev
1.18.0

vscode-latex
mat
1.3.0

r
Mik
0.0.32

debugpy
ms-
2024.4.0

isort
ms-
2023.10.1

python
ms-
2024.4.1

vscode-pylance
ms-
2024.4.1

jupyter
ms-
2024.3.1

jupyter-keymap
ms-
1.1.2

jupyter-renderers
ms-
1.0.17

vscode-jupyter-cell-tags
ms-
0.1.9

vscode-jupyter-slideshow
ms-
0.1.6

remote-containers
ms-
0.354.0

remote-ssh
ms-
0.110.1

remote-ssh-edit
ms-
0.86.0

remote-wsl
ms-
0.88.0

cmake-tools
ms-
1.17.17

cpptools
ms-
1.19.9

cpptools-extension-pack
ms-
1.3.0

remote-explorer
ms-
0.4.3

autodocstring
njp
0.6.1

r
REd
2.8.2

cmake
twx
0.0.17

intellicode-api-usage-examples
Vis
0.2.8

vscodeintellicode
Vis
1.3.1

jinja
who
0.0.8

(4 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:30899288
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
2e7ec940:31000449
pythontbext0:30879054
accentitlementst:30995554
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
d34g3935:30971562
fegfb526:30981948
bg6jg535:30979843
ccp2r3:30993541
dsvsc020:30976470
pythonait:31006305
gee8j676:31009558
dsvsc021:30996838
gd77d436:30999572
da93g388:31013173

Trace-20240414T224244.json
Trace file above.

@Steve6378
Do you have steps to reproduce this.
And the attached trace file is empty. Can you please provide one with a valid performance trace.

Not really sure since the signs are pretty benign, but I just ran a Jupyter code file and everything type-related lags out.
I did recall logging the performance test, I'll check again and reupload soon!

So I ran the perf test and saved but the terminal printed this: "Failed to save timeline: The request is not allowed by the user agent or the platform in the current context. (NotAllowedError)" Any fixes for this?

What kind of per test are you running. We would need a performance trace of VS Code itself to understand why typing is slow.
Could you create a screen cast so that we better understand what you are doing?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


[Battletower] Gui Outdated

The battle tower gui shows pre nerf values
Steps to reproduce the behavior:

Do /battletower
Read gui
see $5,000 a floor and $140,000 total
See error

For it to display $1,250 a floor and $42,500 total

Orion, likely all

Updated config to reflect changes on all servers and verified changes.

Closing ticket as resolved.

Thanks for the detailed report!


You cannot place tiles on plating that has wires

Steps to reproduce:

Crowbar tile
Place wire on plating
Try to place tile back

seems like this may have something to do with tiles not being as "real" as everything else

The problem is that wire click boxes are the whole tile, so clicking the plating with a wire on it only clicks the wire.

We'll have to programmatically vary the bounding/click box based on direction.

Two things need to happen.
Wires and auto-connecting things like that need a programmatically changed click box.
Other things like chairs need to have their click boxes changed in their prototype.
We most likely also need to remove collision boxes from the stationstation.yml file too so that the things already on the station have the correct collision boxes. #647

Fixel by #1133


fix drawer issue

Fixes # .
fixed drawer navitem icons not aligning

Changes proposed in this Pull Request:

Screenshots / Screen Recording (if applicable)

To Test:

Any specific feedback you are looking for?

can you link the issue for this

Can you provide before and after screen shots for this. This is what I see in dev and I can't see the difference

We don't need to fix anything. For center align we need to pass like this https://github.com/etn-ccis/blui-react-native-showcase-demo/blob/dev/router/NavigationDrawer.tsx#L69

We don't need to fix anything. For center align we need to pass like this https://github.com/etn-ccis/blui-react-native-showcase-demo/blob/dev/router/NavigationDrawer.tsx#L69

That's not correct — the iconAlign property of the InfoListItem is for horizontal alignment of the icon in it's 40px wide container. It is NOT for the vertical alignment (there is no case I can think of where we would actually want to have anything other than center alignment vertically).

I did fresh clone and see the difference now.

dev branch

This branch


Add parameters to the Norse case

For now the esdl input for the Norse case only contains the grid information (assets/ports) but no parameters (asset and not properties, profiles). Actual values do not matter but the idea is to figure out wich parameters are needed for the model.

assets.csv
profiles.csv
@datejada I created two files with dummy data, could you check and let me know if this can work? Thanks.

assets.csv
profiles.csv
Thanks for the comments. The required changes are incorporated.

I'll close it for now, and we can create a new issue to add this data into ESDL and translate it into Tulipa's CSV files.

Thanks for the data. I think I can add it to ESDL.


feat: Base implementation for Grid

Grid
This API proposal is for creating a minimal base implementation of a Grid component.  I propose this is done using CSS Grid syntax, respecting IE 11 shortcomings (no gap, no template areas).
Helpful resource: https://learncssgrid.com
API Proposal
columns (quantity)
A Grid can define an arbitrary number of columns of equal width.
<Grid columns='3'>  //=> { display: grid; grid-template-columns: 1fr 1fr 1fr; }
  <Box>1</Box>
  <Box>2</Box>
  <Box>3</Box>
</Grid>

A string or a number should be accepted.

columns (explicit)
A Grid can explicitly define columns and their sizes.
For now, this is simply using the grid-template-columns value syntax.  Proposing we consider more useful abstractions later.
<Grid columns='90px 50px 120px'> //=> { display: grid; grid-template-columns: 90px 50px 120px; }
  <Box>1</Box>
  <Box>2</Box>
  <Box>3</Box>
  <Box>4</Box>
  <Box>5</Box>
  <Box>6</Box>
</Grid>

rows (quantity)
Note, unlike the columns I'm not proposing a way of defining an arbitrary number of rows.  Rows are created automatically when columns wrap.  Therefore, it makes no sense to say a Grid will have X rows ahead of time.
It may prove useful to be able to say "assign this value to all rows", however, I'm leaving this out of the base implementation proposal.
rows (explicit)
A Grid can explicitly define the sizes of its rows.
For now, this is simply using the grid-template-rows value syntax.  Proposing we consider more useful abstractions later.
<Grid rows='50px 100px'> //=> { display: grid; grid-template-rows: 50px 100px; }
  <Box>1</Box>
  <Box>2</Box>
  <Box>3</Box>
  <Box>4</Box>
  <Box>5</Box>
  <Box>6</Box>
</Grid>

@levithomason
I started working on this and got a few questions for the first version:
1. Is this the complete API? It looks a bit limiting to have only these props (I extracted them in an interface):
interface IGridProps {
  as?: string
  children?: ReactNode
  className?: string
  columns?: string | number
  content?: ReactNode
  rows?: string
}

2. Shouldn't we add a sub-component for children (GridItem)? On CSS Tricks for Grid there are plenty of examples on how to style individual items; maybe add orientation (justify-self, align-self, place-self, etc)? or should we keep that for v2?
3. Related to 2; how do we align items?

Do we add any props to the Grid component?
Do we add GridItem sub-component to make it more visible or other options?
Do we create some default alignment (everything centered let's say) and iterate from there?


Getting issues with React Development?

I am facing issues in react development like not getting intelligence, unable to format code (shift+alt+f). So can anyone tell me what all extension should I use for the react, I have searched in extension manager but there are so many, don't know what to use.

The lastest VSCode release does appear to have caused issues with React Native development
https://github.com/Microsoft/vscode/issues/30995

Please try VScode 1.14.2 which was just released. It includes TS 2.4.2 which fixes a number of issues that could be causing this

Yep looks fixed after a restart, thanks for quick turn around and heads up.

Thanks yeah looks good


Hugo v0.134.0 has broken the .Process method

What version of Hugo are you using (hugo version)?

$ hugo version
0.134.0

Does this issue reproduce with the latest release?
YES
Error returned below
 error calling Process: this feature is not available in your current Hugo version, see https://goo.gl/YMrWcn for more information

Test site. Check the image partial and the list file where it is called.
$ hugo env
hugo v0.134.0-77df7bbbff8ce6b56ed693270088de973a87d5ce linux/amd64 BuildDate=2024-09-03T09:54:22Z VendorInfo=gohugoio
GOOS="linux"
GOARCH="amd64"
GOVERSION="go1.23.0"

https://gohugo.io/troubleshooting/faq/#i-get-this-feature-is-not-available-in-your-current-hugo-version

The error message could be better, but I'm guessing that you try to produce webp, and then you need the extended version of Hugo; follow the URL above and it's all explained.


[5.1] [Should be 5.0] Add symlink/copy command for assets

This is a implementation of #7147 and a simplified version of Symfony AssetsInstallCommand, based on the VendorPublish command.
This add the possibility for packages to register directories that should be copied to the public folder, so that they are accessible from the web, like javascript/css files. When possible, the files are symlinked to preserve space. On windows the files are mirrored.
The main difference with the VendorPublisher is that this command always overwrites the existing folders (deletes them first). This command would be run on a new install to make sure that assets are always in sync with the vendor folder.
Difference with L4: packages are copied to public/vendor/<package name> instead of public/vendor/<vendor name>/<package name>, in line with the publisher.
Example usage in the register() method of a package provider:
   $this->assets([
        __DIR__.'/../resources/assets' => 'foobar',
    ]);

Would copy the folder to public/vendor/foobar. This is used instead of a full path for consistency and prevent accidental deleting of the wrong folder ;) (misusage)

And yes, the publish command now has a 'overwrite' argument, but they still should be 2 different things, because this command would always overwrite all the asset directories. And symlinking prevents duplicate files.
Extra option would be relative symlinks instead of full path?

@GrahamCampbell What does the title mean now? Is this considered for L5.0? Would be helpful for package upgrades and would be nice if it is supported in L5.0, otherwise a fallback would be needed for 5.0 anyways..

What does the title mean now?

It means this has been sent to the 5.1 branch but should now be targeted to the 5.0 branch. I haven't retargeted it at 5.0 incase it doesn't make it into 5.0, in which case we'd only have to retarget it again.

Okay I've rebased this so it can be merged. But I guess it could be solved by creating a group 'assets'
php artisan vendor:publish assets --overwrite
(If the package developers agree on the same group tag)
Don't know if that's the direction Taylor wants to go. A different option could be to add a --symlink option to the other command.
php artisan vendor:publish assets --symlink

You need to rebase without a merge commit.

Okay sorry, fixed

Made this PR also relative, and also created a PR for an alternative approach, like I described above.

Going to hold off on this for now since we can publish by tag or provider.

@taylorotwell could you add a section to the docs about asset publishing and a recommendation for a tag + folder to store them? So the package devs can follow the same guidelines.
For example, a tag 'assets' to public_path('vendor/courier')? Or a tag 'public'?
Or if you have a preference, let me know and I can write the docs.

Old I know, but annoying how you guys just write this off as "not important".  I can see 3 separate  github issues by @barryvdh on the same issue that gets pushed off.  I think most people struggle and with live package assets and just hack stuff together.
Since publish does no overwrite, you have to rm public/vendor/mreschke then artisan vendor:publish constantly.  Or of course hack it with a symlink.  My approach is to write my own asset manager.  I check url for /package/ right inside bootstrap/autoload.php FIRST THING before laravel framework boots.  If URL is found, it loads my own asset.php file which can then open the file from any location, forget the public folder, and stream the file with cache headers.  This avoids the framework and the webserver public dir all together and access times are < 1ms since no laravel.
@barryvdh where did you leave off on this?  Seems your attempt to at least have a publish command that OVERRIDES is completely ignored.  Laravel is not very kind to package devs...but getting closer now that @taylorotwell is actually writing packages himself now (spark)...so we get better dynamic control like pushMiddleware etc...but still no proper asset management solution.
@taylorotwell what do you think about building your own asset streamer right into laravel, at the start in bootstrap/autoload.php, without laravel fireing up at all?  I would think you yourself would want this by now, course spark only has one asset (the logo)...maybe when you build more packages you'll realize how important it is to have live access to package assets.
@barryvdh if you don't have a solution already, ill build a laravel package for it, but will require you to add one line to bootstrap/autoload.php to check for url and skip laravel if found.  I actually have one I've been using for years which I can wrap up into a package.

For the debugbar, I'm adding a route that serves the js /css. And for elfinder I'm suggesting people to publish on every composer update, but this still creates some issues when people forget this (assets out of sync)


Failed unpacking rock file

While trying to make Lapis work on Windows.
luarocks install lapis
gives
Error: Failed unpacking rock file
This should not happen.
I am using Windows 7 64 bit
Lua was installed with LuaForWindows_v5.1.4-46.exe (includes luarocks 2.0,2)
FYI for the interested: http://pan.baidu.com/s/1eR1bR9o (to download Openresty_For_Windows_<IP_ADDRESS>1_32Bit.zip) should allow running openresty (and then lapis) on MS Windows systems. I'll check this as soon as possible, when lapis will be installed.

2.0.2 is rather old, and a lot has improved in recent releases regarding the Windows platform. Can you try again after installing 2.3.0 ?

I already tried to install latest (2.3.0) luarocks, but scripts failed.
Should I open another issue for this errors I got? (one case was successful install BUT without version advancement and another was errors in installation with recursive opening of shells!)

Should I open another issue for this errors I got?

Please do, if you get 2.3.0 to work most likely this bug will go away, too.


Set up API calls to update local database

Need to link ApiGetter class to the Rooms database. Should be able to communicate using the Elephant and Location classes

Functionality should be wrapped into the class spec'd by #24


change: task visibility improvements and changes to admin tasks

Checklist

[ ] Affected Issues have been mentioned in the Closing issues section
[ ] Documentation has been written/updated
[ ] PR title is ready for inclusion in changelog

The current showUi implementation processes what can be seen in the UI, it only hides the options from the dropdown menu, but doesn't prevent them from being shown elsewhere. It also doesn't prevent the logs for these tasks being hidden.
This moves all the hiding functionality to behind RBAC in the API.
It removes showUi and creates adminOnlyView instead. These are used by resolvers to check if the user is admin or not, and will filter out tasks in resolvers if these are set to true.
Setting adminOnlyView to true on a task will hide this task from the drop down menu, and also hide the item in the task view thus preventing access to the logs for non-admin users.
adminTask is split into:

deployTokenInjection, as this is used as an identifier to inject the lagoon-deployer token into tasks. Only admins can set this flag.
projectKeyInjection as a second option, this can be used to control the injection of the projects ssh key used for tasks etc.

It leaves showUi and adminTask, but these reflect the value of the replacements to an extent.

showUi is the inversted value of adminViewOnly
adminTask is the same as deployTokenInjection

Closing issues
closes #3392

Noting that as the current released UI has showUi support still, admin view only tasks will be hidden by the UI even for admins until the showUi stuff is reverted. I built in the showUi backwards compatability support only because of the UI
Once the UI is reverted, showUi will be ignored, and the admin view only tasks will be visible to admins only.
I've updated this PR with the PR image for the UI in the docker-compose stack only for local checking.


endless reloads, weird clash with eslint-import-resolver-webpack

Version
v2.8.1
Reproduction link
https://github.com/simllll/nuxt-monorepo-test
Steps to reproduce
Hi all,
I was looking into a super weird issue where nuxt does endless reloads. I was able to break it down to one depdendency: "eslint-import-resolver-webpack" which seems to cause this issue, but now I'm kinda stuck as I have no idea what exactly is causing it and why this results into something that weird.
My demo setup:

super slim monorepo with lerna.js
one package with a nuxt creater template
root package.json has a "eslint-import-resolver-webpack" in it, if you remove this and run "npm run clean && npm run install && npm run bootstrap" it starts working, if you add it back again and rerun "npm run clean && .." (it's important to run clean because otherwiese package-lock is not removed) it breaks again.

The strange thing is: I do not use any eslint specific things in the nuxt project.
Besides this, I really want to know why the reload is happening. I guess there is some hidden error, maybe we can even improve this for other related bugs too.
Regards
Simon
What is expected ?
Just start the demo page, no endless reloads
What is actually happening?
The demo start page (or actually all sub pages) are reloading endless. It looks like the server is still sending the nuxt loading page with a progerss of 100%,the client tires to reload the page afterwards but the server still sends the loading page.. therefore it causes an endless loop?

This bug report is available on Nuxt community (#c9593)

The error is a combined effect of learn hoist and eslint-import-resolver-webpack.
Because eslint-import-resolver-webpack depends on<EMAIL_ADDRESS>which is far behind current wepback dependency<EMAIL_ADDRESS>and learn hoisted<EMAIL_ADDRESS>to root node_modules, so webpack used old version enhanced-resolve and lead to missing resources and endless reloading error.
You can fix or verify by adding "enhanced-resolve": "^4.1.0" manually in your package.json.
I suggesting not using lerna hoist, if you have to use lerna, please use yarn workspaces together with lerna for implementing your hoisting requirement.

Thanks for looking into it and your response,
I found the same root cause and could easily "fix" it by moving the dev dependency to the lerna sub package.
Regarding yarn, unfortunately we cannot move from npm to yarn due to our deployment environment and some other issues with yarn.
Anyway, what I was hoping that we can maybe find the cause of this to improve the error logging / behaviour. Endless reloads are just very hard to debug ;)
Regards


Remove tao VERSION file. It no longer exists.

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Solved via #232


Question related to state-constraint satisfication of SCPO?

In the paper https://arxiv.org/pdf/2306.12594.pdf, it claimed the SCPO provides guarantees for state-wise constraint satisfaction in expectation, after convergence of training.

But Proposition 1 in the paper can only prove that J_{Di} is smaller or equal to w_i, and I guess w_i is from Right-hand-side of Eqn (13). (see below screenshot)

In my opinion, to prove the state-wise constraint satisfaction in expection, we also need to prove RHS of Eqn (13) converges to 0 after training. But I didn't find the related proof in the paper regarding this matter in Appendix.

Therefore, I would appreciate any clarification on this matter!

Also I would like to confirm that: The above guarantee is only after training is converged, but not throughout each step of the training, correct?

Another observation is that: for all the experimental tests that I conducted, there still exists constraint violation even after convergence (see below videos for example). I guess it is expected because the above guarantee is only "in expectation", which means I need to run infinite number of tests, in order to see majority of them do not have constraint violation, correct?

https://github.com/intelligent-control-lab/guard/assets/33006435/cd88cb56-0d54-4798-b354-b39f6f568773
https://github.com/intelligent-control-lab/guard/assets/33006435/590d80aa-8c6a-48cd-953b-b230be3d08ee

Hi Haihan, your question is insightful! In our paper, we establish that, during policy optimization, by constraining the right-hand side (RHS) of equation (13) to be smaller than $w_i$, the state-wise cost $J_{D_i}$ of the new policy will be consistently smaller than $w_i$ at each iteration during training. It's crucial to note that there's no need to prove the RHS of (13) converges to 0.
It's important to understand that the computation of the RHS of (13) involves the advantage term $A_D^\pi$. Theoretically, with the ground-truth value of $A_D^\pi$ for the current policy, the constrained policy optimization ensures that the new policy's state-wise cost $J_{D_i} \leq w_i$.
However, in practical implementation, the advantage is approximated by a neural network, learned from limited experience, introducing a gap between the learned $A_D^\pi$ and the ground truth. Additionally, we linearize the objective and constraints during policy optimization, forming it as a Linear Quadratic Constrained Linear Program (LQCLP) (Section 10.2 in CPO: https://arxiv.org/abs/1705.10528) and apply backtracking to balance reward improvement and cost reduction (code lines 433 to 555 in SCPO: https://github.com/intelligent-control-lab/StateWise_Constrained_Policy_Optimization).
In summary: (i) The guarantee holds at each training iteration, not just after convergence. (ii) Violation is attributed to the inherent learning error of the advantage function and solving the LQCLP form of equation (11) during practical implementation. (iii) SCPO ensures state-wise cost satisfaction in expectation, and we are actively working on a much stronger theoretical result called Absolute SCPO (ASCPO), which guarantees high-probability state-wise cost satisfaction. You might find our side project, APO, interesting; it originates from the theoretical result of ASCPO and is a basic RL algorithm ensuring monotonic improvement of the lower probability bound of performance (https://arxiv.org/abs/2310.13230).


fix: ios snap behaviour

On iOS, onMomentumEnd is not called unless the user is scrolling with momentum.
This ensures that the snap logic is called properly when momentum scrolling is not in use.
Additionally, it reenables overscroll/bouncing the scroll view.
Fixes #59

Note that I didn't test Android at all, so please test before merging.
Also in the DiffClamp + Snap Example, it seems to snap over the article tab covering it. But I'm not sure if this is a bug introduced by this PR or not. It works fine on the last tab where there's more content:
Recording: https://streamable.com/gqfbbd

Note that I didn't test Android at all, so please test before merging.
Also in the DiffClamp + Snap Example, it seems to snap over the article tab covering it. But I'm not sure if this is a bug introduced by this PR or not. It works fine on the last tab where there's more content:
Recording: https://streamable.com/gqfbbd

Longer video that shows things working (besides #66):
https://streamable.com/nez289

Longer video that shows things working (besides #66):
https://streamable.com/nez289

A comment on 05ea6af (#65):
https://docs.swmansion.com/react-native-reanimated/docs/next/api/useAnimatedReaction/
I believe using the empty array fixed some small jittering in the diffclamp demo.
I noticed there are other usages of useAnimatedReaction that don't define a dependency array. Those may need optimizing too (in a separate PR)

A comment on 05ea6af (#65):
https://docs.swmansion.com/react-native-reanimated/docs/next/api/useAnimatedReaction/
I believe using the empty array fixed some small jittering in the diffclamp demo.
I noticed there are other usages of useAnimatedReaction that don't define a dependency array. Those may need optimizing too (in a separate PR)

Also in the DiffClamp + Snap Example, it seems to snap over the article tab covering it. But I'm not sure if this is a bug introduced by this PR or not. It works fine on the last tab where there's more content:

I saw it in other recordings, it's weird, here is fine

Also in the DiffClamp + Snap Example, it seems to snap over the article tab covering it. But I'm not sure if this is a bug introduced by this PR or not. It works fine on the last tab where there's more content:

I saw it in other recordings, it's weird, here is fine

Hi, @andreialecu and @PedroBern. I've just pulled this and ran as per https://github.com/PedroBern/react-native-collapsible-tab-view/issues/59#issuecomment-770209467 I can confirm that the Snap is fixed.

Hi, @andreialecu and @PedroBern. I've just pulled this and ran as per https://github.com/PedroBern/react-native-collapsible-tab-view/issues/59#issuecomment-770209467 I can confirm that the Snap is fixed.

closed in favor of #67

closed in favor of #67


[Android] Multiple issues in the documentation

We now have the Android documentation (Javadocs) live at http://dl.windowsazure.com/androiddocs/, and while browsing it we can notice many issues with them. I'm listing many around here which I found in the package page alone, but we should perform a thorough scrubbing in the comments to make sure we have a good documentation for the SDK.
Package overview (http://dl.windowsazure.com/androiddocs/overview-summary.html)

No descriptions

Package com.microsoft.windowsazure.mobileservices:

Class / interface / enum definitions:

Missing documentation:

BuildConfig
Registration
MobileServiceException
MobileServicePreconditionFailedException
MobileServicePreconditionFailedExceptionBase

Wrong / bad descriptions:

MobileServicePush: "the notification hub client" --> not really
MobileServiceTable<E> and MobileServiceJsonTable - same description. The description should tell the difference between them.
QueryOrder: "Sort order values". We could reword it better as something like "The possible values to determine sort ordering." or something similar.

Grammar / typos:

MobileServiceClient: Entry-point for Windows Azure Mobile... --> remove Windows, remove - (hyphen) between "entry" and "point"
Missing articles (many places): for example: GcmNativeRegistration: "Represents GCM native registration". It would be better as something like "Represents a native registration with GCM" or at least "Represents a GCM native registration"

@marianosz Let's hold off on this item until @RickSaling investigates in android studio javadocs first. Thanks!

@RickSaling we will need to regenerate java docs for the latest android sdk and put it at http://azure.github.io/azure-mobile-services/ or a new github.io belonging to mobile apps since the zumo content got deleted from http://dl.windowsazure.com/androiddocs/ as well. I remember you were the contact for java docs, please let me know if I should redirect to someone else. Thanks!

moved to https://github.com/Azure/azure-mobile-apps-android-client/issues/28


Using baseURL breaks down website in production

I host my blog on aws s3. I had to comment baseURL in config.toml because the js and css paths would be broken in production.
The paths would be generated like this if I leave baseURL:

Without base URL the paths are generated in a relative way - THIS is working:

Please come with a more robust solution

Please come with a more robust solution

LMFAO demanding!

Please come with a more robust solution

LMFAO demanding!

Submit deez nuts

@eviscerat Can you show an example of this behaviour?
And what's the main problem - links to JS and CSS / links to posts / all of them?

Ok, just re-tested this on a fresh copy of your repo using the exampleWebsite provided, re-uploaded to s3, no changes to config, the website renders paths correctly. Apologies, I ll close this issue.


Better mobile integration (allows text input)

Before the virtual keyboard would not show up when a text field was active, now objects attempting to grabKeyboardInput will also pull up the virtual keyboard if on mobile.
This has been tested on LOVE stable OSX as well as LOVE master iOS.
The one downside I see of this change is the possibility of the user of SUIT to be using love.keyboard.setTextInput(), however I'm not sure why they would be.

Looks good, thanks!

This is useful to do on desktop as well.
@vrld would it be possible to get the x/y/w/h of the current input when grabbing keyboard? Properly dealing with textedit (composition) events depends on it.

Right now this is possible, but has to be handled by the host application, e.g.:
local x,y,w,h = layout.row()
local state = suit.Input(input, x,y,w,h)
if suit.isActive(id) and suit.hasKeyboardFocus(id) then
    -- just grabbed focus.
end

Would it if the widget reports its box (x,y,w,h) and whether it grabbed focus in the return state?
Also, I am admittedly clueless about this: Why do you need the widget area when the widget grabs the keyboard focus? I assume so you can focus a camera on the input area?

Nothing game logic related.
CJK IME's need to know where the text box (from the editing cursor to the end of the area, ideally) is on screen in order to position the candidate list appropriately. You need to tell it the region to show up in when it is focused and when the contents change in any way.
(more info here: https://wiki.libsdl.org/Tutorials/TextInput, if the basics are doable I'm more than willing to do what's needed to get the details right)

The more you know! This should be done library-side (in input.lua), then. Pull requests are very welcome ;)


Eliminate the use of unsafe block for signing

Related discussion can be found at https://github.com/FuelLabs/sway/pull/3201#discussion_r1008932356

blocked by https://github.com/FuelLabs/fuel-crypto/pull/36

@Salka1988 is this still blocked?

@Salka1988 is this still blocked?

https://github.com/FuelLabs/fuel-crypto/pull/36
This repository has been archived by the owner on Jan 4, 2023. It is now read-only.

There have been minor issues with dependencies which I am currently working on with @leviathanbeak

Will be fixed by #950 I think

fixed  by #950


Fix wavlm_large broken link

Fix my last comment on #245: link to model of wavlm_large, Can you verify @Sanyuan-Chen ?

hi @bagustris ,
I put the wrong sharing link by mistake and it has been expired by 11.27.2021. The updated link is right.
Thank you for fixing the link!

Hi @bagustris !
Thanks! The PR looks good to me. I am merging this.


merge from template-arlac77-github

.github/workflows/ci.yml

chore: add if [ ! -f /usr/bin/pacman ]
then
sudo apt-get update
sudo apt-get install ksh curl
wget https://github.com/ThePoorPilot/pacman-utils/releases/download/5.2.2-3_2.31-0/pacman-utils_5.2.2-3_amd64.deb
sudo apt-get install -f ./pacman-utils_5.2.2-3_amd64.deb
fi
(jobs.release.steps.run)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>5:
0.0%

Covered Lines:
71

Relevant Lines:
71

💛  - Coveralls


Add support for registering custom checks, statistics, strategies

Is your feature request related to a problem? Please describe.
So far, pandera has supported easily creating custom checks for dataframe/series schemas. However, with the ability to generate synthetic data #314 from a schema, it's become more important to be able to easily register checks as built-in checks so that users can:

serialize/deserialize user-defined checks
define data-generation strategies for these checks

fixed by #351


Push user to login page if accessing index while not logged in

Do the thing

Yo Brandon we already did this right? @bsimmons123

I think i did, I didn't test it though


Attachment is not rendered

Previously attachments were in urls field.
Now it is stored in attachments field.
https://github.com/RocketChat/Rocket.Chat/commit/441ae0b552340b45548b416dcbf29536ac925749
Sample message with a picture
{"msg":"result","id":"load-message145104531609419","result":{"messages":[{"_id":"nvEjt8yazc3oRJrvG","rid":"kZKjb9etwp5a6K5tt","msg":"","file":{"_id":"KL8iYtaFoSnrYEgQZ"},"groupable":false,"attachments":[{"title":"File Uploaded: twitterYI01.jpg","title_link":"/ufs/rocketchat_uploads/KL8iYtaFoSnrYEgQZ/twitterYI01.jpg","image_url":"/ufs/rocketchat_uploads/KL8iYtaFoSnrYEgQZ/twitterYI01.jpg","image_type":"image/jpeg","image_size":6105}],"ts":{"$date":1451045293172},"u":{"_id":"wffqrSXNojgMnuz8v","username":"YusukeIwaki"}}],"unreadNotLoaded":0}}

fixed by https://github.com/RocketChat/Rocket.Chat.Android.Lily/pull/12


Hide menu items when extension isn't active

Inactive extensions for the current workspace tend to make menus needlessly long, this patch add a constant sftp:enabled used to hide menus when it isn't active (no sftp.json)

This is great!  Could you please fix the tslint errors?

My apologies I did not know about tslint. All errors should be fixed now!


Integrate CodeQL to the CI pipeline

Hi
I believe codeQL is a great tool for this project as it can discover vulnerabilities and bugs that might not be so obvious to detect.
Is the team positive with integrating such tools?

@istae Hi
I forked the project and run CodeQL which shows the following possible errors:

I took a look at those errors and one of them could introduce a bug since a json struct is marshalled and the code creates a buffer based on the size of the marshalled data


Iteration Plan for May 2018

This plan captures our work in May. This is a 5-week iteration. We will ship our May Update in early June.
In this iteration, we'll provide a preview of the grid layout support for the editor as well as an alternative UI for configuring settings. We'll also look into ways to provide outline information for open documents.
Endgame

May 28th, 2018: Code freeze for the endgame
June 1st, 2018: Endgame done

The endgame details for this iteration are tracked in #50477.
Plan Items
Below is a summary of the top level plan items.
Legend of annotations:

Mark
Description

:runner:
work in progress

:hand:
blocked task

:muscle:
stretch goal for this iteration

:red_circle:
missing issue reference

:large_blue_circle:
more investigation required to remove uncertainty

:black_circle:
under discussion within the team

Workbench

[x] :runner: Preview for grid layout for editors #14909 @bpasero @joaomoreno
[ ] :runner: Continue to improve settings experience #41040 @roblourens
[ ] :runner: Quick box improvements for multi-step inputs #49340 @chrmarti
[ ] :runner: Investigate custom title bar and menus for improved accessibility on Windows #29024 @sbatten
[x] Provide command to open New Window on open workspace #49346 @isidorn
[x] Explore supporting an Outline view #5605 @jrieken
[x] Enable custom search implementations #47058 @roblourens
[x] Polish activity bar contribution support #49103 #48580 @sandy081

Editor

[x] Ship a new version of the Monaco editor @alexandrudima @rebornix

Terminal

[ ] :runner: Enable multi-plexing of terminals #46192 @tyriar
[x] Provide DOM-based rendering when GPUs are disabled #46954 @tyriar
[x] :muscle: :runner: Investigate top-level Terminal menu for better discoverability #49477 @tyriar

Languages
Language Server Protocol

[x] Support Code Action API and code actions that return workspace edits https://github.com/Microsoft/language-server-protocol/issues/389 @dbaeumer

JavaScript/TypeScript

[x] Adopt TypeScript 2.9 #49654 @mjbvz

[x] Options for quote style in generated code #49653 @mjbvz
[x] Disable suggestions at the TS server level #47617 @mjbvz
[x] Support TS trigger characters #40539, #25034 @mjbvz
[x] :runner: Support TS Move to New File refactoring #49866 @mjbvz

[x] :runner: Reasonable presentation style for 'unused variable' suggestions #15710 @mjbvz

CSS/HTML/JSON

[x] :runner: Provide support for @-keywords in SASS/SCSS #41929 @octref
[x] :runner: Debt reduction in the CSS/HTML extensions and language servers query @octref

Debug

[x] Explore improved positioning of the debug toolbar #2513 @isidorn
[x] nodemon re-attach issue #48501 @roblourens

Extension Contributions

[x] Submit PRs to extensions to suggest contributions to the built-in Test viewlet @sandy081
[x] :runner: Re-Investigate tslint running as a TypeScript server plugin Microsoft/vscode-ts-tslint#7 @egamma
Architectural improvements to the vetur extension @octref

[x] :runner: Cover Vetur's Language Features with ene-to-end tests vuejs/vetur#802
[x] Centralize all file system access in VLS vuejs/vetur#800
[ ] :runner: Decouple sub language services with top-level MetadataStore

[x] Consolidate handling of webroot and pathmapping in the Chrome Debugger #49472 @roblourens
[x] :runner: Support several forthcoming PRs against the xterm.js project xtermjs/xterm.js#1399 xtermjs/xterm.js#1327 xtermjs/xterm.js#958 @tyriar

Extensions

[x] :runner: Recommend language packs based on the locale of the OS #45663 @ramya-rao-a

API

Finalize API for

[x] Tasks #49806 @dbaeumer
[ ] :runner: Compute definition locations #10037 @mjbvz
[x] :runner: WebView persistence #49022 @mjbvz
[ ] :runner: SearchProvider #47058 @roblourens

Propose API for:

[ ] :runner: Hierachical Document Symbols #34968 @jrieken
[ ] :runner: Quick box multi-step inputs #49340 @chrmarti

Custom view API enhancements:

[x] Access the current selection #49511 @sandy081
[x] Support to listen the expand/collapse state #30535 @sandy081

Serviceability

[x] Improve the perceived speed of opening the process explorer on Windows #45163 @rmacfarlane
[x] Update performance wiki with how to use the process explorer #48970 @rmacfarlane
[x] Cosmetic changes to issue reporter #49579 @rmacfarlane

Engineering

[x] Move to the public VSTS build infrastructure @joaomoreno
[x] Address Github reported module vulnerabilities #49146 team
[ ] :muscle: Retrain issue classifier bot #49341 @chrmarti

Documentation

[x] Continue to refresh videos on the website #45924 @auchenberg

Deferred Items

Custom view: Execute command on double click #39601 @sandy081
Electron 2.0 update
Explore bread crumb support for navigation #9418 @jrieken
Support intellisense in edit boxes for watches, variables #48810 @isidorn
Adopt new VS Code APIs in the VS Code Go extension Microsoft/vscode-go#1676 @ramya-rao-a
In settings search provide a way to show matching but not-installed extensions #49474 @roblourens

Investigate custom title bar and menus for improved accessibility on Windows @sbatten

I think it is related to https://github.com/Microsoft/vscode/issues/29024

@WaiSiuKei Also, https://github.com/Microsoft/vscode/issues/17060

🔴 Investigate custom title bar and menus for improved accessibility on Windows @sbatten

Just want to mention that the latest Windows update 1803 has issues with custom title bars. See my issue telegramdesktop/tdesktop#4649 for more information.

any chance to get this one #10026 on board?

@kieferrm

Investigate custom title bar and menus for improved accessibility on Windows @sbatten

Why does it say missing issue reference the are numerous issues out there mention this. I can just list a few of them.
#39972
#32257
#29997
#17060

@guledali the people working on the features will fill in the issue references eventually 😄

Yes but that would be one of the changes. The nightly could be of the alpha such as Firefox does it, and weekly could be the beta and monthly be the stable (or however long it's needed to deem it "stable") The alpha would have auto-commits per change on dependencies (a commit to NodeJs or Electron for example would update over to here instead of manually pulling it down and pushing back up) (at least on a 12 hour increment to meet the nightly update schedule). The beta would have the tweaking optimizations that ensure that at least nothing breaks even if in a rough state while the stable would be polished out. A somewhat more Agile approach that what's currently done if I understand the release schedule correctly.

@DarthSpock but that's not all compliant to the work item planning right  in front of you.
They iterate Monthly with a focus on stabilizing at the end of each month aka "The Endgame", where they prepare the develop to be merged into master (branch names don't matter; insider / release, alpha / release all the same).
What you are asking them for is a weekly release cycle, a weekly planning cycle... which would change things on so many ends i wouldn't be able to accurately predict the impact and i would assume neither can the more active contributors...
As you can see simply through the existence of  0.X.1 Or 0.X.2 releases in the past, there already is a fast action plan in place allowing them to iterate small to hotfix something. We don't need a seperate release channel for that, especially if that potentially increases planning requirements a ton while simultaneously forcing contributors to edge down the integration process of their features to one week.
The latter is the biggest nono i see in your proposal.
When a contributor has to be able to guarantee that his/her feature is stably integrated within one week i really doubt there'd be any community contributors who'd do large features.
Just look at some of the issues in this integration plan...

I don't know where else to put this but would it be possible to close ticket on previous features that were half implemented? These 2 features have been pushed away for so long without any love

Editor Minimap (30 opened issues)
Color Picker (20 opened issues)

this one in particular #33568 (when user start changing color the picker should not easily close)

@ghiscoding thanks for the feedback we will keep it in mind for future iteration planning. For now I suggest to vote on individual feature requests.

Closing - 1.24 has been shipped.


Does not support use with lower frequencies.

E.g.
$ osmocom_fft -F -a "driver=lime,soapy=0,clock=40e6,cacheCalibrations=1" -s 5e6 -f 7e6
Results in:
LMS_StreamBoard::ConfigurePLL(tx=10MHz, rx=5MHz)
C[INFO] SoapyLMS7::setFrequency(Rx, 0, RF, 7.000000 MHz), ref 30.720000 MHz
[INFO] SoapyLMS7::setFrequency(Rx, 0, BB, -1897.655000 MHz), ref 30.720000 MHz
See also attached for FFT frequency scale displayed.

So I think SetFrequencySX() or GetFrequencySX_MHz() didn't handle 7MHz correctly.

Correct, these functions configure only Rx/Tx PLL frequencies, and they
can't be configured that low. To achieve 7 MHz frequency additional chip
configuring is required. Perhaps a higher level function should be created
to handle all that.

So I think the call to set the RF frequency needs to clip the requested frequency to the closest possible frequency. When that happens, the default tuning algorithm in SoapySDR will automatically compensate for the error using the CORDIC.
If for some reason we don't like that automatic behaviour with the clipping and cordic correction outside of the driver, then SoapySDR::setFrequency(dir, chan, freq){} can be overloaded to implement something smart as well.
Is that basically the right idea here? And what is the actual/achievable lower bound that the LO can tune?

@guruofquality are you suggesting that applications would have to do something different with this particular hardware at lower frequencies? That doesn't sound right.
@rjonaitis could you comment on LO bounds.

@guruofquality are you suggesting that applications would have to do something different with this particular hardware at lower frequencies? That doesn't sound right.

Nope, just driver related work in lms7suite. The SoapyLime::setFrequency() call will just need to clip the target frequency to a possible frequency.
It probably gets a bit hairy to tune near the lower VCO band edge, so we might need a slightly conservative lower bound, and I think it might be a function of the clock rate.

FWIW, I have been using fixed (100e3, 3.8e9) as the tunable LO range in the LMS7002M. I may have pulled that from the data sheet rather than testing edge cases. I also added this as an API call to add to the LMS700M class, so if its configurable, that can be added like getSXXRange(): https://github.com/limemicro/lms7suite/issues/15

could you comment on LO bounds.

PLLs can be tuned from around 30 MHz to 3.8 GHz

This should do the trick: https://github.com/limemicro/lms7suite/commit/27b488b75bfb55339f828f120b8617d50c57de8b


Options for install script

I found that it would be really nice to have a way to pass options to dotbot via. the install script. For example, most of the time I don't want the chatty version of dotbot, I just want to know if things failed. I'm torn over whether or not being able to override the config suffix and basedir makes any sense, but it was easy enough to add so I left it in the code for now.
Here is the version of the script I am using (along with the change elsewhere in your Issues to allow for multiple config files).
#!/usr/bin/env bash

set -e

DEFAULT_CONFIG_PREFIX="default"
CONFIG_SUFFIX=".conf.yaml"
DOTBOT_DIR="dotbot"

DOTBOT_BIN="bin/dotbot"
BASEDIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"

# Parse command line options
DOTBOTOPTS=""
VERBOSE=""
while getopts "Qqvd:c:" opt; do
    case $opt in
    v|Q|q)
        VERBOSE=$opt
        DOTBOTOPTS="$DOTBOTOPTS -$opt"
        ;;
    d)
        BASEDIR=$opt
        ;;
    c)
        CONFIG_SUFFIX=$opt
        ;;
    ?)
        exit 1
        ;;
    esac
done
# Clean up parsed options
while (( $((OPTIND--)) > 1 )); do
    shift
done

cd "${BASEDIR}"
git submodule update --init --recursive "${DOTBOT_DIR}"

for conf in ${DEFAULT_CONFIG_PREFIX} ${@}; do
    if [ $VERBOSE != "Q" ]; then
        echo -e "\nInstalling $conf..."
    fi
    "${BASEDIR}/${DOTBOT_DIR}/${DOTBOT_BIN}" ${DOTBOTOPTS} -d "${BASEDIR}" -c "${conf}${CONFIG_SUFFIX}"
done

The install script already allows this. That's what the "${@}" does on line 14:
"${BASEDIR}/${DOTBOT_DIR}/${DOTBOT_BIN}" -d "${BASEDIR}" -c "${CONFIG}" "${@}"

You can try it - do ./install -q and see what happens.

Unless you use the multi-config version of the script, then that gets parsed in the 'for conf' loop. My change above adds parsing of the non-config file options.

Ah, I see. The wiki might be a good place to put this. The current documentation on this is here: https://github.com/anishathalye/dotbot/wiki/Tips-and-Tricks

Mention of this issue added to wiki.


Ts in the wrong report

In ionic and angular

I have no idea what this stacktrace or your issue mean. Could you please post some code?

I didn't write chalk-related code, but I declared chalk errors at runtime, and I'm not really sure it's a chalk problem.

Please try deleting any lockfiles you have, remove your node_modules folder and re-install your dependencies. I've seen something like this before.

Thank you. I will try.


[SPEC] Proposals and their Contracts

Proposals
1. Anchor Update Proposal
Contract Flow: Bridge/SignatureBridge -> AnchorHandler -> Anchor
Proposal Data: (resourceId, srcChainId, latest_leaf_index, merkle_root)
2. Set/Change Wrapping Fee Proposal
Contract Flow: Bridge/SignatureBridge -> TokenWrapperHandler -> GovernedTokenWrapper
Proposal Data: (resourceId, nonce, functionSig, newFee)
3. Add Token Proposal
Contract Flow: Bridge/SignatureBridge -> TokenWrapperHandler -> GovernedTokenWrapper
Proposal Data: (resourceId, nonce, functionSig, newTokenAddress)
4. Remove Token Proposal
Contract Flow: Bridge/SignatureBridge -> TokenWrapperHandler -> GovernedTokenWrapper
Proposal Data: (resourceId, nonce, functionSig, removeTokenAddress)
5. resourceId Proposal
Contract Flow: Bridge/SignatureBridge -> AnchorHandler/TokenWrapperHandler (specifically goes to setResource within HandlerHelpers.sol)
Proposal Data: (executionChainId, nonce, functionSig, resourceId, handlerAddress, executionContextAddress)
Questions/Issues

The anchor update proposal does not contain a functionSig which means that the length of its proposal data is 96 bytes while the length of the other single parameter proposals data is 128 bytes. I currently resolve this by adding 32 bytes of dummy zeros to the anchor update proposal data, but is the better solution to just include the functionSig in the anchor update proposal data as well?
To keep things in a consistent format should we replace executionChainId in the resourceId proposal with handlerAddress + executionChainId?

I think you're missing the src_chain_id from the Anchor Update Proposal @saiakilesh. This is different than the execution_chain_id where the update is being processed on.

I think you're missing the src_chain_id from the Anchor Update Proposal @saiakilesh. This is different than the execution_chain_id where the update is being processed on.

My bad, I made the change.

I think we may still need a nonce for the anchor proposal that is different than the latest_leaf_index. What do you think @saiakilesh?

I think we may still need a nonce for the anchor proposal that is different than the latest_leaf_index. What do you think @saiakilesh?

I don't immediately understand why?

You're likely right, just thinking through differences in a standarised proposal format.


Eager load 'subject' and 'causer' on timeline activity

Prevents lazy loading errors when using eloquent in strict mode. May also improve performance of queries.
Also fixes issue with this action's modifyQueryUsing not being correctly applied.

I attempted to solve this using modifyQueryUsing which is where I discovered that the closure was executed but the result was discarded. As such, the following code should work but without 86b96344f10eafda252cbfd9fc309845f960dd92 does not.
ActivityLogTimelineTableAction::make('Activity')
    ->modifyQueryUsing(fn ($builder) => $builder->with(['subject', 'causer'])),


Check for response body when none is expected and fail tests

An increasing number of implementers are returning JSON responses for operations that don't have a response body defined in WOPI. The validator should verify that responses that should be empty actually are empty.

We are in the process of closing this GitHub repository.  This issue has been moved to the CSPP team ADO backlog list for consideration. If you would like to follow up or provide more information, please reach out to<EMAIL_ADDRESS>


Protected Routes JWT

server.js

I'd be happy to assist on this issue as part of my open source contribution


Snapshot with launch_arguments fails to copy screenshots

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I have read the Contribution Guidelines

Issue Description
When I run snapshot with launch_arguments(["-myUrl https://google.com"]), snapshot fails to copy the resulting screenshots:
[14:44:31]: Copying '/Users/MyApp/fastlane/screenshots/en-US/iPhone4s--myUrl https://google.com-0Launch.png'...
[14:44:31]: No such file or directory @ rb_sysopen - /Users/MyApp/fastlane/screenshots/en-US/iPhone4s--myUrl https://google.com-0Launch.png

Complete output when running fastlane, including the stack trace and command used

You can use: --capture_output as the last commandline argument to get that collected for you

fastlane inapp
[14:49:06]: ------------------------------
[14:49:06]: --- Step: default_platform ---
[14:49:06]: ------------------------------
[14:49:06]: Driving the lane 'ios inapp' 🚀
[14:49:06]: ----------------------
[14:49:06]: --- Step: snapshot ---
[14:49:06]: ----------------------
[14:49:07]: Successfully loaded '/Users/MyApp/fastlane/Snapfile' 📄

+------------------+-------------------------------+
|    Detected Values from './fastlane/Snapfile'    |
+------------------+-------------------------------+
| devices          | ["iPhone 4s"]                 |
| languages        | ["en-US"]                     |
| launch_arguments | ["-myUrl https://google.com"] |
+------------------+-------------------------------+

[14:49:07]: $ xcodebuild -list -project ./InAppTester.xcodeproj

+----------------------------+---------------------------------------------------------------------+
|                                    Summary for snapshot 2.2.0                                    |
+----------------------------+---------------------------------------------------------------------+
| devices                    | ["iPhone 4s"]                                                       |
| languages                  | ["en-US"]                                                           |
| launch_arguments           | ["-myUrl https://google.com"]                                       |
| project                    | ./InAppTester.xcodeproj                                             |
| scheme                     | InAppTester                                                         |
| output_directory           | /Users/MyApp/fastlane/scree... |
| skip_open_summary          | false                                                               |
| clear_previous_screenshots | false                                                               |
| reinstall_app              | false                                                               |
| erase_simulator            | false                                                               |
| localize_simulator         | false                                                               |
| buildlog_path              | ~/Library/Logs/snapshot                                             |
| clean                      | false                                                               |
| number_of_retries          | 1                                                                   |
| stop_after_first_error     | false                                                               |
| xcode_path                 | /Applications/Xcode7.3.1.app                                        |
+----------------------------+---------------------------------------------------------------------+

[14:49:09]: Building and running project - this might take some time...
[14:49:09]: snapshot run 1 of 1
[14:49:09]: Patching '/Users/me/Library/Preferences/com.apple.iphonesimulator.plist' to scale simulator to 100%
[14:49:11]: $ xcodebuild clean -showBuildSettings -scheme InAppTester -project ./InAppTester.xcodeproj
[14:49:12]: -------------------------
[14:49:12]: --- iPhone 4s - en-US ---
[14:49:12]: -------------------------
[14:49:12]: $ set -o pipefail && xcodebuild -scheme InAppTester -project ./InAppTester.xcodeproj -derivedDataPath '/var/folders/94/j6g83n_137gcp10cvxb4jqfh0000gp/T/snapshot_derived20161223-39216-a3sxt6' -destination 'platform=iOS Simulator,id=28076592-81BF-495D-8ABD-491C49175E2C,OS=9.3' FASTLANE_SNAPSHOT=YES build test | tee /Users/me/Library/Logs/snapshot/InAppTester-InAppTester.log | xcpretty
[14:49:12]: ▸ Loading...
[14:49:13]: ▸ Building InAppTester/InAppTester [Debug]
[14:49:13]: ▸ Check Dependencies
[14:49:14]: ▸ Compiling main.m
[14:49:15]: ▸ Compiling AppDelegate.m
[14:49:15]: ▸ Compiling ViewController.m
[14:49:15]: ▸ Linking InAppTester
[14:49:15]: ▸ Compiling Main.storyboard
[14:49:15]: ▸ Compiling LaunchScreen.storyboard
[14:49:15]: ▸ Processing Info.plist
[14:49:15]: Running Tests: ▸ Touching InAppTester.app
[14:49:15]: ▸ Build Succeeded
[14:49:15]: ▸ 2016-12-23 14:49:15.865 xcodebuild[39288:3926585] [MT] IDETestOperationsObserverDebug: (95E7AB08-D24E-4A6B-AB38-E590F954501A) Beginning test session 95E7AB08-D24E-4A6B-AB38-E590F954501A with Xcode 7D1014 on target <DVTiPhoneSimulator: 0x7fe266b7c5c0> {
[14:49:15]: ▸ SimDevice: SimDevice : iPhone 4s (28076592-81BF-495D-8ABD-491C49175E2C) : state={ Shutdown } deviceType={ SimDeviceType : com.apple.CoreSimulator.SimDeviceType.iPhone-4s } runtime={ SimRuntime : 9.3 (13E230) - com.apple.CoreSimulator.SimRuntime.iOS-9-3 }
[14:49:15]: ▸ } (9.3 (13E230))
[14:49:15]: ▸ 2016-12-23 14:49:15.866 xcodebuild[39288:3926589]  IDETestOperationsObserverDebug: Writing diagnostic log for test session to:
[14:49:15]: ▸ /var/folders/94/j6g83n_137gcp10cvxb4jqfh0000gp/T/snapshot_derived20161223-39216-a3sxt6/Logs/Test/6525B2D0-17EA-43D4-8977-F6CA426AE52A/Session-2016-12-23_14:49:15-Fylmh1.log
[14:49:15]: ▸ Building InAppTester/InAppTester [Debug]
[14:49:15]: ▸ Check Dependencies
[14:49:15]: ▸ Building InAppTester/InAppTesterUITests [Debug]
[14:49:15]: ▸ Check Dependencies
[14:49:15]: ▸ Processing Info.plist
[14:49:15]: ▸ Preprocessing /Applications/Xcode7.3.1.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Library/Xcode/Agents/XCTRunner.app/Info.plist
[14:49:15]: ▸ Compiling SnapshotHelper2-3.swift
[14:49:18]: ▸ Compiling InAppTesterUITests.swift
[14:49:18]: ▸ Linking InAppTesterUITests
[14:49:18]: Running Tests: ▸ Touching InAppTesterUITests.xctest
[14:49:28]: ▸ Test Succeeded
[14:49:28]: ▸ All tests
[14:49:28]: ▸ Test Suite InAppTesterUITests.xctest started
[14:49:28]: ▸ InAppTesterUITests
[14:49:28]: ▸ ✓ testExample (5.241 seconds)
[14:49:28]: ▸ 	 Executed 1 test, with 0 failures (0 unexpected) in 5.241 (5.242) seconds
[14:49:28]: ▸
[14:49:28]: Collecting screenshots...
[14:49:28]: Found 1 screenshots...
[14:49:28]: Copying '/Users/MyApp/fastlane/screenshots/en-US/iPhone4s--myUrl https://google.com-0Launch.png'...
[14:49:28]: No such file or directory @ rb_sysopen - /Users/MyApp/fastlane/screenshots/en-US/iPhone4s--myUrl https://google.com-0Launch.png
[14:49:28]: Tests failed, re-trying 1 out of 2 times

Environment
fastlane env
[14:53:11]: Generating fastlane environment output, this might take a few seconds...
<details><summary>✅ fastlane environment ✅</summary>

### Stack

| Key                 | Value                                            |
| ------------------- | ------------------------------------------------ |
| OS                  | 10.11.6                                          |
| Ruby                | 2.3.0                                            |
| Bundler?            | false                                            |
| Git                 | git version 2.7.3                                |
| Installation Source | ~/.rvm/gems/ruby-2.3.0/bin/fastlane              |
| Host                | Mac OS X 10.11.6 (15G1108)                       |
| Ruby Lib Dir        | ~/.rvm/rubies/ruby-2.3.0/lib                     |
| OpenSSL Version     | OpenSSL 1.0.2h  3 May 2016                       |
| Is contained        | false                                            |
| Xcode Path          | /Applications/Xcode7.3.1.app/Contents/Developer/ |
| Xcode Version       | 7.3.1                                            |

### System Locale

| Variable | Value       |   |
| -------- | ----------- | - |
| LANG     | en_US.UTF-8 | ✅ |
| LC_ALL   | en_US.UTF-8 | ✅ |
| LANGUAGE | en_US.UTF-8 | ✅ |

### fastlane files:

<details><summary>`./fastlane/Fastfile`</summary>

```ruby
# Customise this file, documentation can be found here:
# https://github.com/fastlane/fastlane/tree/master/docs
# All available actions: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Actions.md
# can also be listed using the `fastlane actions` command

# Change the syntax highlighting to Ruby
# All lines starting with a # are ignored when running `fastlane`

# If you want to automatically update fastlane if a new version is available:
# update_fastlane

# This is the minimum version number required.
# Update this, if you use features of a newer version
# fastlane_version '1.95.0'

default_platform :ios

platform :ios do

    desc 'Runs all unit the tests and generates reports in `fastlane/reports`'
    lane :inapp do
        snapshot
    end
end

No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.2.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.0.2

executable-hooks
1.3.2

bundler-unload
1.0.2

rubygems-bundler
1.4.4

bundler
1.13.2

io-console
0.4.6

slack-notifier
1.5.1

rouge
1.11.1

xcpretty
0.2.4

multipart-post
2.0.0

word_wrap
1.0.0

babosa
1.0.2

colored
1.2

highline
1.7.8

commander
4.4.0

faraday-cookie_jar
0.0.6

gh_inspector
1.0.2

mini_magick
4.5.1

multi_json
1.12.1

multi_xml
0.5.5

security
0.1.3

xcpretty-travis-formatter
0.0.4

dotenv
2.1.1

faraday
0.9.2

faraday_middleware
0.10.0

json
2.0.2

excon
0.53.0

rubyzip
1.2.0

plist
3.2.0

claide
1.0.1

xcodeproj
1.3.3

unicode-display_width
1.1.1

terminal-table
1.7.3

generated on: 2016-12-23

```

Hey @JanC, thanks for reporting this issue, it's definitely a bug in snapshot and something we need to fix. In the mean-time, can you use snapshot without the launch arguments and give a try if that works? You can probably fake the same thing somehow from within your app for now?

Thanks Felix,
yes I did a workaround in my app.
Cheers

@JanC i did a PR #7670  which should fix the issue - could you give it a try - and confirm it works?


feat: port LinearAlgebra.AffineSpace.Pointwise

Try bors merge again over here, @semorrison?

bors r+


eslint config file doesn't appear to be committed

Running gulp lint yields many errors.

Might also be a smart idea to add eslint gulp test to npm test so Travis CI will pick up on it for pull requests. After the config file is added.

Ouch. I had it on, but was doing a lot of dev and so took it off. Putting it back on. :)
It's xo-linted, and properly configured for that.

All good - enforced as well.


Edgar CB3-431 Can't enable Legacy; Firmware utility script has RW_Legacy option grayed out

Successfully enabled Developer mode, ran CL to enable legacy crossystem dev_boot_altfw=1 (chronos insisted on using altfw in place of legacy).  On white dev splash screen Ctrl-L still gives 2 beeps, then boots to ChromeOS.  Firmware utility script does not offer the RW_Legacy firmware update option, it's grayed out.  Trying to boot Gallium or Lubuntu, stuck!  Is it hopeless on a Braswell 'book?

Solved, apparently.  Even though grayed out,  RW_Legacy firmware update  ran and installed it.  Kinds unintuitive. All good though, Lubuntu running in live session and functionality is good...haven't tested camera yet.

if it ran, it's a bug and I need to fix it. RW_LEGACY is not supported on EOL devices


luci-app-miniupnpd: restore missing luci install file

Restore luci indexcache handling incorrect removed in
https://github.com/openwrt/luci/commit/387a06bb73462312c075e53ce9e6002d4af09e92
Signed-off-by: Kevin Darbyshire-Bryant<EMAIL_ADDRESS>

@jow-
Are those ucitrack blocks still needed for LuCI apps?
I am unsure how procd has impacted on the need of ucitrack.

Well, this does not hurt in any case, so lets add that back.


After including pod SwipeCellKit the app is not going to built

Xcode - 9.4.1
Swift - 4.1
iOS - 11.4

Read the requirements and install guide in the README


BUG: the parameter --taipy-force is broken

The  --taipy-force option does not work.
jeanrobin@LAPTOP-RPTO2SFK MINGW64 ~/workspace/demos/scenario
$ python main.py --production 2.0 --taipy-force
[2023-06-18 17:00:06][Taipy][INFO] No scenario comparators defined for ScenarioConfig `scenario_configuration`.
[2023-06-18 17:00:06][Taipy][INFO] There are non-conflicting changes between the version 1.0 Configuration and the current Configuration:
        CORE "version_number" was modified: 1.0 -> 2.0
        CORE "force" was modified: False:bool -> True:bool
[2023-06-18 17:00:06][Taipy][ERROR] The version 1.0 Configuration is conflicted with the current Configuration:
        DATA_NODE "replacement_type" has attribute "default_value" added: DEFAULT
[2023-06-18 17:00:06][Taipy][ERROR] To force running the application with the changes, run your application with --taipy-force option.
The application is stopped. Please check the error log for more information.

First the "force" parameter should not appear in the config changes.
Second, I should be able to run passing the --taipy-force parameter

The "force" parameter appears under INFO section, which means that it is a "non-conflicting change". If I get your message correctly, you want to keep the "version_number" change in the INFO, but remove "force" right? That would require an exception since both are on the CoreSection.
My guess is that the --taipy-force is failing here because the production version 1.0 is conflict with the current Configuration. On 2.3, we do not provide any migration method yet, so it is supposed to fail.

To resolve the second point, I added 2 PRs to improve the error message. It will be something like
$ python3 main.py --production "2.0"
[2023-06-21 10:41:57][Taipy][INFO] No scenario comparators defined for ScenarioConfig `s`.
[2023-06-21 10:41:57][Taipy][INFO] There are non-conflicting changes between the version 1.0 Configuration and the current Configuration:
        CORE "mode" was modified: experiment -> production
        CORE "version_number" was modified: 1.0 -> 2.0
[2023-06-21 10:41:57][Taipy][ERROR] The version 1.0 Configuration is conflicted with the current Configuration:
        DATA_NODE "b" has attribute "default_data" added: b
[2023-06-21 10:41:57][Taipy][ERROR] Please remove version 1.0 from production to avoid conflict.

The production version 1.0 is still blocked from running, since there is conflict.

What is wrong, according to me, is that I am running the app with --taipy-force, and there is an error message saying I should run it with --taipy-force. This is inconsistent.
Should we replace the error message with a Warning saying:
"Conflicting changes have been detected but option --force is used. The application runs anyway."

So instead of blocking the application from running, we let the user run it right?
Working on it.

If --taipy-force is True, yes.

So about the first point
Right now, when there is unconflicted change (in sections Job, GUI, CoreSection), the change is still shown in the terminal.
My question is: Should we add another layer for the _CoreSection to hide it entirely, or should we hide all unconflicted sections?


nginx 1.9.9 not shutting down properly when on <IP_ADDRESS>-beta

Just updated on CentOS 6.7, nginx 1.9.9 to <IP_ADDRESS>-beta using the clang and devtoolset-3 gcc 4.9.1 workaround outlined at https://github.com/pagespeed/ngx_pagespeed/issues/1079 on my live forums running pagespeed at https://community.centminmod.com/
After update, and restarting nginx gives me the following error
Starting nginx: nginx: [emerg] bind() to <IP_ADDRESS>:80 failed (98: Address already in use)
nginx: [emerg] bind() to <IP_ADDRESS>:81 failed (98: Address already in use)
nginx: [emerg] bind() to <IP_ADDRESS>:82 failed (98: Address already in use)
nginx: [emerg] still could not bind()

and ends up with failed nginx start, process list shows nginx processes are still running so stop didn't happen.
If I turn off ngx_pagespeed via pagespeed off;, nginx starts properly.
Had no problems with ngx_pagespeed <IP_ADDRESS>-beta previous beta

more investigation seems it is related to the 2nd method outlined at https://github.com/pagespeed/ngx_pagespeed/issues/1079 with export CFLAGS workaround as even downgrading to <IP_ADDRESS>-beta didn't help nginx properly stop and start
<IP_ADDRESS>-beta worked with the initial workaround passing devtoolset-3 toolchain via exported CC variable.

so it works when built with gcc, but not clang?

yeah with GCC 4.9.1 not clang
i see even with nginx stop command that processes are consuming cpu time
top -c
top - 19:27:00 up 112 days, 13:26,  1 user,  load average: 6.18, 4.12, 2.56
Tasks: 186 total,   4 running, 182 sleeping,   0 stopped,   0 zombie
Cpu0  : 99.7%us,  0.3%sy,  0.0%ni,  0.0%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Cpu1  :100.0%us,  0.0%sy,  0.0%ni,  0.0%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Cpu2  :100.0%us,  0.0%sy,  0.0%ni,  0.0%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Cpu3  :100.0%us,  0.0%sy,  0.0%ni,  0.0%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Mem:   4045132k total,  3384436k used,   660696k free,    73224k buffers
Swap:  4194300k total,   287800k used,  3906500k free,  1401772k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 5634 nginx     10 -10  707m  39m  12m R 139.2  1.0   4:39.67 nginx: worker process
 5633 nginx     10 -10  707m  39m  12m R 132.6  1.0   4:21.58 nginx: worker process
 5635 nginx     10 -10  707m  39m  12m R 126.6  1.0   4:25.87 nginx: worker process

with GCC 4.9.1 nginx starts and forums load but all css is broken https://community.centminmod.com/

what is broken with the CSS? on a cursory look it appears fine to me.

Looks like it's working now with pagespeed off and pagespeed on for css files.. must of been some caching within the forum app.
To summarize so far
nginx 1.9.9 with ngx_pagespeed <IP_ADDRESS>-beta and <IP_ADDRESS>-beta

with clang and any gcc-toolchain path devtoolset-3 workaround with GCC 4.9.1 results in nginx failing to properly stop and those Address already in use errors and nginx worker processes consuming large amounts of cpu resources
with GCC compiled nginx via devtoolset-3, ngx_pagespeed 1.10 works fine and is currently in use and seems to be working on the forums

I would just like to inform you that I am also having several problems with this last 1.10.XX version , nginx 1.9.x.
After the upgrade, the server keeps crashing .
At the moment , I have to use version <IP_ADDRESS>

@arielesp Does it print anything in the error log when it crashes?

So, dont crash stopping... but dont answer and need restart nginx
I already tested in 20 servers...
There are some bug in version 1.10... or with compiler ... I dont know...
This problem occurs with big sites ...
server setup
32GB RAM
SSD 120GB
Intel Xeon E3 1245v2
I tested with nginx 1.9.9, only frontend / backend
And other with apache as backend

@arielesp It sounds to me like you're saying you're seeing 1.10 hang and be unresponsive, but it's not crashing, is that right?  Is there anything printed to the error logs when it goes unresponsive?

@jeffkaufman I didnt checked. ... but I will reinstall again to check ...

@centminmod Over on #1114 you indicated that you were still having these problems with 1.10, and so are still on 1.9?
(I had thought this was working for you now.)

@jeffkaufman yes i have it working in latest beta of my Centmin Mod LEMP stack if i use GCC devtoolset but I need for it to work with Clang too as for my stack the difference in compile speed and memory usage is enough to justify using Clang compiler and that doesn't work with ngx_pagespeed 1.10.
For now, I am just temporarily disabling ngx_pagespeed from integration into the stable version of my Centmin Mod LEMP stack (which doesn't have my fix from my beta version) as it's breaking a lot of users nginx 1.9.11 upgrades (~3,000 new installs per month). Guess this is expected with nginx mainline 1.9 usage :)

@centminmod sorry for the delay on this.
I've tried with building clang 3.7, with using devtoolset and with gcc5 compiled from source.
Each time it seems like the __init_array isn't populated when using clang. I'm opening a bug with clang to track this (maybe it's still our fault, but I'm not convinced otherwise).

bug i opened on llvm's bugtracker https://llvm.org/bugs/show_bug.cgi?id=26727

@crowell cheers much appreciated - fingers crossed :)


Program treats "." in numeric "0.x" as an operator and throw an exception!

When I parse the expression: "b+0.5", the program treats "." in "0.5" as an operator, then throw an exception.

Uhmm, this might be something new, I made an update in the code that parses numbers. I will investigate it tonight and try to fix this. Thanks for reporting.

Actually, this was really simple to fix =], I fixed it on commit: 9576265e14fe55ef23108ec19cfea81eccb14e9d
Can you check to see if this works for you?

It works now. Thank you so much. I have been struggling with this issue for a day at my company. By the way, could you add a README to run "test-shunting-yard.cpp", I know this file is used to run test cases but I don't know how to run it.

Sure, I will add it to the README file, but in short the Makefile handles it, so you need to make installed and then you can just run:
make test

And everything should just work

Done:
https://github.com/cparse/cparse/blob/master/README.md#running-the-library-tests
=]


add Resource Group to RBAC doc

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the CODEOWNERS.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screenshot.

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

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65f0b73fc4066c3cd59e4720--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65fa0ecad8a1422d0435bf37--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65fa0f428773392e25af6cef--harness-developer.netlify.app


Adding gits sync feature workflow

This feature enables the current branch to be up-to-date with master while keeping the changes in the current branch intact

I have implemented this functionality which is useful when the team is working on trunk-based development and the developer needs to keep his/her personal development branch in sync with the main tunk (main/master) in order to avoid any possible merge conflicts in the future.

Implemented by @urvishvasani. Closing the branch.


Feature Request:  Add PARAMCD from lookup table and output where obs not mapped

Feature Idea
Read in look up table with PARAMCD/PARAM mappings, and left join the PARAMCD/MAPPING, for those observations with no PARAMCD added, output the records for user to review.
Relevant Input
ADVS/ADEG/ADLB CDISC data with lookup table for PARAMCD as we have in ADVS script (or BDS Vignette).
Relevant Output
ADVS/ADEG/ADLB with PARAMCD/PARAM added, and if no mapping found for observations then output to another data frame, controlled user.
Reproducible Example/Pseudo Code
See VS script with lookup table and LEFT JOIN statements, just need to add in checking for missing PARAMCD, and output thse records somewhere.

Could this be metadata driven or data-driven
Messaging around mappings not complete
Some scenarios where we might have to make up own paramcds - if it was data-driven
How does a company create a look-up table?
CDISC dummy data versus company-specific data
#552

Hey @konstantinakoukR just checking on where you are at with this issue.  We have till May 13th to get this one done :)

My understanding is it would be a function with a user-defined table.  A user would have their PARAMCD/PARAM mappings and then using the function join it onto the dataset.  If things are not mapped correctly or missing params then you get a warning message and results to review.  @millerg23 is that correct?

My understanding is it would be a function with a user-defined table. A user would have their PARAMCD/PARAM mappings and then using the function join it onto the dataset. If things are not mapped correctly or missing params then you get a warning message and results to review. @millerg23 is that correct?

Yes, thats correct, so function would have the following inputs as a minimum:
input data set (ie ADLB)
LOOK-UP table
BY_VARS for merging ADLB and LOOK-UP table
The function would return the dataframe with the variables in the look-up table added.
If there were observations in the new dataframe where PARAMCD missing then a WARNING would be triggered with the unique entries for the variables (from BY_VARS).
So if BY_VARS was LBTESTCD, LBMETHOD, then the WARNING would display the unique entries of LBTESTCD, LBMETHOD where PARAMCD was missing.
The function would call derive_vars_merged I think, then check for missing PARAMCD.

Hi @bms63 , @millerg23 and @yangc71 ! I think I got an initial draft ready. Just a couple of things:

where should we store the function? In the R folder?
how the function should be called? What about derive_adlb_lookup?

Yes R folder for sure.
I would take a look at the https://pharmaverse.github.io/admiral/articles/programming_strategy.html to make that call and see if there are other lookup tables already available?

Thank you @bms63 ! Based on Programming Strategy I proposed the derive_adlb_lookup, since derive_ takes a dataset as input and returns a new dataset as output. I don't think there are any other lookup tables available already but maybe I'm missing something.

Ummm...thinking if this is only for adlb or can it be generalize for other datasets?  adeg?

Good point! Maybe we can have a more general name like derive_lookup_table but for now we can have it limited to ADLB as first PR/testing?

Shouldn't we use the vars fragment as it adds variables to the input dataset?

So derive_vars_lookup_table  ?

But it doesn't derive any new variable really :/ It merges the two datasets together and gives a new dataset with the records that PARAMCD is empty. Happy to use derive_vars_lookup_table though! :)

To me, this is similar to other derive_vars_merge_xxxx functions we have, that all call derive_vars_merged function.
Maybe, derive_vars_merge_lookup or derive_vars_merge_lookup_table (maybe too long a name!)?

Hi all, I tried to move forward with this issue and linked a pull request (#1298). Currently the function optionally outputs a message showing a table of unique by_vars values that are not mapped. Could you please take a look and let me know if it's the right approach? Thanks.


Add Constant for Zookeeper user Path; Improve naming standardization.

Fixes #3120 by adding constant for "/users"  ZK path.
Also updated case style of ZKUserPath variable for consistency.

I am surprised that the instance variable name convention that variables should start with a lower case letter is not complaining about ZKUserPath - with is seems to consistent with other variable names in places, but I thought that this would be against conventions.
In this case, I lean towards favoring convention and consistency could be examined separably (another pr making the other variables consistent and following convention - if that does not violate any API concerns)

@EdColeman yeah I wasn't sure what our desired state was as the formatter and style guide wasn't throwing errors and other private variables in the same classes also didn't match.
I'm happy to switch everything to the zkUserPath option instead.


Update to CCF 4.0.16

Update to CCF 4.0.16

Build is failing because the 4.0.16 version cannot be found:

Indeed, there is no new version available in PyPi

I see that the CCF github action that publishes the package has failed, I'm checking with the CCF team on this

CCF team has fixed the GH action and the package has been published. I'm triggering a new build:

CCF team has fixed the GH action and the package has been published. I'm triggering a new build:

Thanks Andrea! Looks like all the checks have passed now.


BMP and PNG images are supported. Header added.

Reading from files moved to get_file function.
Working with headers is pretty straightforward. But a dirty trick is used not to change a lot of functions. PDF_HEADER_PAGE is used instead of NULL or page pointer to add data (text, images, figures) to a common header like this:
pdf_add_text(pdf, PDF_HEADER_PAGE, "Header 2", 24, 60, 800, PDF_RGB(0, 100, 0));
pdf_add_rectangle(pdf, PDF_HEADER_PAGE, 40, 750, 520, 80, 1, PDF_RGB(100, 0, 0));
pdf_add_ppm(pdf, PDF_HEADER_PAGE, 480, 765, 50, 50, "teapot.ppm");

So it is used to distinguish between real page to add and page header.

So I have removed everything concerning the header and fixed your remarks.

The valgrind issue on the tests is being caused by this:
==178== Memcheck, a memory error detector ==178== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==178== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info ==178== Command: ./testprog ==178== ==178== Invalid read of size 1 ==178==    at 0x116435: pdf_add_bmp (pdfgen.c:2694) ==178==    by 0x10B906: main (main.c:55) ==178==  Address 0x4b0cf56 is 0 bytes after a block of size 149,382 alloc'd ==178==    at 0x483B7F3: malloc (in /usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so) ==178==    by 0x10D119: get_file (pdfgen.c:2267) ==178==    by 0x116020: pdf_add_bmp (pdfgen.c:2652) ==178==    by 0x10B906: main (main.c:55) ==178== ==178== Invalid read of size 1 ==178==    at 0x11643D: pdf_add_bmp (pdfgen.c:2695) ==178==    by 0x10B906: main (main.c:55) ==178==  Address 0x4b0cf58 is 2 bytes after a block of size 149,382 alloc'd ==178==    at 0x483B7F3: malloc (in /usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so) ==178==    by 0x10D119: get_file (pdfgen.c:2267) ==178==    by 0x116020: pdf_add_bmp (pdfgen.c:2652) ==178==    by 0x10B906: main (main.c:55) ==178== ==178== Invalid read of size 1 ==178==    at 0x11645B: pdf_add_bmp (pdfgen.c:2696) ==178==    by 0x10B906: main (main.c:55) ==178==  Address 0x4b0cf57 is 1 bytes after a block of size 149,382 alloc'd ==178==    at 0x483B7F3: malloc (in /usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so) ==178==    by 0x10D119: get_file (pdfgen.c:2267) ==178==    by 0x116020: pdf_add_bmp (pdfgen.c:2652) ==178==    by 0x10B906: main (main.c:55) ==178== ==178== ==178== HEAP SUMMARY: ==178==     in use at exit: 157,297 bytes in 2 blocks ==178==   total heap usage: 6,265 allocs, 6,263 frees, 15,390,636 bytes allocated ==178== ==178== LEAK SUMMARY: ==178==    definitely lost: 157,297 bytes in 2 blocks ==178==    indirectly lost: 0 bytes in 0 blocks ==178==      possibly lost: 0 bytes in 0 blocks ==178==    still reachable: 0 bytes in 0 blocks ==178==         suppressed: 0 bytes in 0 blocks ==178== Rerun with --leak-check=full to see details of leaked memory ==178== ==178== For lists of detected and suppressed errors, rerun with: -s ==178== ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0)

Sorry, I can't execute valgrind with my Linux subsystem because of make errors, so I can't see any its messages:
sudo make clean && scan-build-10 --status-bugs make check CLANG_FORMAT=clang-format-10 rm -f *.o tests/*.o testprog *.gcda *.gcno *.gcov tests/*.gcda tests/*.gcno output.pdf output.txt tests/fuzz-ppm tests/fuzz-jpg tests/fuzz-header tests/fuzz-text output.pdftk fuzz.jpg fuzz.ppm fuzz.pdf doxygen.log tests/penguin.c valgrind.log rm -rf docs fuzz-artifacts infer-out scan-build: Using '/usr/lib/llvm-10/bin/clang' for static analysis /usr/share/clang/scan-build-10/bin/../libexec/ccc-analyzer -I. -c pdfgen.c -o pdfgen.o -g -Wall -pipe --std=c1x -O3 -pedantic -Wsuggest-attribute=const -Wsuggest-attribute=format -Wclobbered -Wempty-body -Wignored-qualifiers -Wmissing-field-initializers -Wold-style-declaration -Wmissing-parameter-type -Woverride-init -Wtype-limits -Wuninitialized -Wunused-but-set-parameter -fprofile-arcs -ftest-coverage Assembler messages: Fatal error: can't create pdfgen.o: Permission denied pdfgen.c:1: error: cannot open pdfgen.gcno     1 | /**       | make: *** [Makefile:32: pdfgen.o] Error 2

Sorry for not responding earlier. Valgrind is complaining because there are some memory leaks in pdf_add_png & pdf_add_raw_bitmap.
This should fix it: https://gist.github.com/AndreRenaud/1b8b0052365a42bff5842bece722e73c

Sorry for not responding earlier. Valgrind is complaining because there are some memory leaks in pdf_add_png & pdf_add_raw_bitmap.
This should fix it: https://gist.github.com/AndreRenaud/1b8b0052365a42bff5842bece722e73c

Yes, you are right, the stream was freed in the pdf_add_image function in the old version of PDFGen, but now the structure was changed, so I didn't notice it.
Valgrind shows no errors now, but check is still not successful. Is it a formatting problem?

Yes. You should be able to fix it by running 'make format'. You may need to specify the clang-format binary, ie: make format CLANG_FORMAT=clang-format-10
I've made the tooling for PDFGen really very strict, which does make contributing a bit awkward. Sorry about that.

If these last few steps are too much hassle, let me know and I'll clone your branch to do the last few code cleanups and push it from there.

Hello Andre, I try to fix it ASAP

If these last few steps are too much hassle, let me know and I'll clone your branch to do the last few code cleanups and push it from there.

Ready :)

Wonderful. Thanks for all the work on this.


(bluefox) many adapter commands were called parallel. This PR tries t…

many adapter commands were called parallel. This PR tries to remove many parallel calls.

This pull request introduces 10 alerts and fixes 21 when merging d03105d2a0ea20968b13b4d703c65a5ed1892989 into c81cb1a60e9a2793dd5144725e221c6ad15d9cb0 - view on LGTM.com
new alerts:

10 for Unneeded defensive code

fixed alerts:

17 for Unused variable, import, function or class
4 for Useless assignment to local variable

Comment posted by LGTM.com

This pull request fixes 21 alerts when merging d632feec39926e2ccd784e463af31b0870e77bcc into c81cb1a60e9a2793dd5144725e221c6ad15d9cb0 - view on LGTM.com
fixed alerts:

17 for Unused variable, import, function or class
4 for Useless assignment to local variable

Comment posted by LGTM.com

https://forum.iobroker.net/topic/20097/iobroker-upnp-please-test/2
Ack, that adapter do work

This pull request fixes 21 alerts when merging bbeeccd5a72bb1e78bef03e8b89d558941a891b8 into c81cb1a60e9a2793dd5144725e221c6ad15d9cb0 - view on LGTM.com
fixed alerts:

17 for Unused variable, import, function or class
4 for Useless assignment to local variable

Comment posted by LGTM.com

This pull request introduces 3 alerts and fixes 24 when merging 3bd1f69f291fffd26f799b7ebfe1df44ef73746b into b81b12c6a7bf104ac2c92186206d22aaf3a5a09c - view on LGTM.com
new alerts:

2 for Unneeded defensive code
1 for Incomplete string escaping or encoding

fixed alerts:

18 for Unused variable, import, function or class
4 for Useless assignment to local variable
1 for Replacement of a substring with itself
1 for Incomplete string escaping or encoding

Comment posted by LGTM.com

This pull request introduces 4 alerts and fixes 23 when merging d055be7fa112ec34880116d677231d0487802847 into b81b12c6a7bf104ac2c92186206d22aaf3a5a09c - view on LGTM.com
new alerts:

3 for Unneeded defensive code
1 for Useless assignment to local variable

fixed alerts:

18 for Unused variable, import, function or class
4 for Useless assignment to local variable
1 for Replacement of a substring with itself

Comment posted by LGTM.com

This pull request fixes 23 alerts when merging e910ff272864539ed8478180b8cde072b232aef1 into b81b12c6a7bf104ac2c92186206d22aaf3a5a09c - view on LGTM.com
fixed alerts:

18 for Unused variable, import, function or class
4 for Useless assignment to local variable
1 for Replacement of a substring with itself

Comment posted by LGTM.com

This pull request fixes 23 alerts when merging a3ddb6f5cff466db2bd5aca507308546c2665c36 into b81b12c6a7bf104ac2c92186206d22aaf3a5a09c - view on LGTM.com
fixed alerts:

18 for Unused variable, import, function or class
4 for Useless assignment to local variable
1 for Replacement of a substring with itself

Comment posted by LGTM.com

This pull request fixes 24 alerts when merging 691237b66c9b10c9eac281225fb2137fb5ec1428 into b81b12c6a7bf104ac2c92186206d22aaf3a5a09c - view on LGTM.com
fixed alerts:

18 for Unused variable, import, function or class
4 for Useless assignment to local variable
1 for Comparison between inconvertible types
1 for Replacement of a substring with itself

Comment posted by LGTM.com


Parameter checker difference should be absolute, not relative

here:
https://github.com/spine-generic/spine-generic/blob/master/spinegeneric/cli/params_checker.py#L71
the tolerance on the difference should not be signed, ie: the absolute value should be used for the difference. Same comment for other parameters.
Also: we should document where the hard-coded param values are located.

hard-coded values are located here: https://github.com/spine-generic/spine-generic/issues/189


Consistency - Install CLI from package vs from Bintray

The section for "Install CLI from Package" and the section for "Install CLI from Bintray" in cli-installcli.md are slightly inconsistent.
Both should have very similar steps, with the exception of the registry set step and some of the syntax.
For example, install from Bintray should also include the "Address Prereqs" as step 1.

We addressed this issue as part of a CLI squad story. We can close this issue.


Extensions refactor

What is included in this request?

[X] Bug Fix
[X] New feature
[X] Changes to an existing feature
[X] New extension
[X] Changes to an existing extension

Describe your changes
Completely refactor extensions functionality

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

:tada: This PR is included in version 1.24.0-dev.6 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket: