1292 persist charge pricelists

Description
Persisting charge prices from messages with business reasoncode "D08".
Chargeinformation and chargeprices is also seperated into flow for each entity.
Charge prices is now a an aggregation root and the architecture reflects this

[x] Persist charge prices
[x] Make chargeprices an aggregat root
[x] Rename charges to chargeinformation and move to own folderstructure
[x] Remove point from charges and chargelinks
[x] Cleanup project
[ ] Write unittests for charge prices classes
[ ] Write integration test for charge prices
[x] Split chargeinformation and chargeprices into seperate test folders to reflect the domain
[ ] Merge with #1346

References

#1292

@cla-bot check


Verify load and save

In the verification tests, check that saving and reloading the program is the same program. This also fixes serialization to always load instructions in the same order. There is also fixes for deconv and quant_conv which didn't save the solution id, and was broken for serialization.

Looks like *.mxr files from the save/load test aren't being cleaned up afterwards?

Where are you seeing left over .mxr files? I dont see them:
$ echo /tmp/migraphx-migraphx_test-*
/tmp/migraphx-migraphx_test-*


incorrect grep for assembly jars in bin/pyadam

the pyadam script has the incorrect grep for the assembly jars at https://github.com/bigdatagenomics/adam/blob/master/bin/pyadam#L33
Should
grep "^adam_[0-9A-Za-z\.-]*\.jar$"
be
^adam-assembly_[0-9A-Za-z\.-]*\.jar$"  ?
Unless I am missing the jar it is supposed to be accessing.

Thanks for catching this @akmorrow13! It should be "^adam[0-9A-Za-z\.\_\-]*\.jar$", as it is in adam-submit


Change searchReposR function.

The SearchRepos.hs did not working so it was fixed.
And, Since several parameters were added, we fixed the searchReposR function so that it can handle it well.
how is it?

I'd like to see a solution like http://hackage.haskell.org/package/github-0.15.0/docs/GitHub-Data-Options.html#t:IssueRepoMod


Improve tf.batch_to_space documentation. Refer issue #34005

Made minor changes to make code more suitable for GCI challenge. Refer https://github.com/tensorflow/tensorflow/issues/34005 .

The changes have been made in order to make the code suitable for a Google Code-In Documentation and Research challenge.
The task now is to clean the documentation so that it is more clear. There are too many code blocks in-between the text.
Some examples are placed in the args section for illustration. A better way to handle that would be to add those examples in a separate "Examples" section (consistent with other docs) and add pointers in the "Args" section.
Similarly, some other code elements could be eliminated from the text by adding pointers.
Clarify the crops part in the "Args" section further.

Please open PR against master branch. We don't update release branches (r...) after the final release of the corresponding TF version (i.e., we won't update r2.1 after TF2.1 is released).
The only time release branches are updated is when we make a patch release to fix a security vulnerability. As that requires expediency, we only accept minimal changes even then.


Check for incorrect backends

Hey there kojix2 and Andy,
Following my tests yesterday on windows I tried today to see whether mpv as backend
is supported (on linux actually). I think it is not.
It should be quite simple to support e. g.
https://shapeshed.com/listening-to-bbc-radio-with-mpv/
https://shapeshed.com/listening-to-bbc-radio-with-mpv/

Anyway - this is actually not the reason for the issue report here.
Just for the sake of it, I tested the following
ruby rubio  --backend mpveegge

So a bogus variant for --backend.
My proposal:

Would it be possible to specify the allowed backends, and if the input (such as
mpveegge in this case) is NOT found as allowed backend, to notify the user
about it, and perhaps explain that as backend vlc will be used instead?

Also I think it may be useful to add an additional entry in the menu interface
to indicate which backend is currently used. Perhaps an additional message
popup showing this like:
backend in use: vlc

and, if possible and you want to go fancy, to perhaps also toggle this in the
menu or some other interface. Something like "configuration" options or
something like that.
Anway, I like how much you can do with a minimalistic radio. Now let's hope
libui-ng can add tons more cross-platform goodies eventually  ... :D
Edit: Ah yes, also ... right now I have not vlc installed on linux. So perhaps
the command should be checked whether vlc exists or not before it tries
to play it. This actually led to a crash on my linux box but I will add a
separate issue. This may be more related to the glimmer code actually
so perhaps Andy may have a look at it, but you'll understand this in
the other issue request.

No, because the whole point of keeping backend support open is to support even future platforms or unknown platforms that can stream/play radio by simply passing in a URL. This makes rubio-radio more compatible with a lot more backends, without even knowing about them.
As such, I don't recommend implementing any validation. It's OK if it fails on incompatible backends. That's on the consumer to handle properly.
By the way, here are 3 ways to install VLC on Linux that might make your life easier.
https://www.vlchelp.com/install-ubuntu-linux/#:~:text=Search for and launch Terminal,be downloaded and installed automatically.

Hi, shevy.
I just tried rubio --backend mpv on Ubuntu. It seems to work well. I think --backend option should be open to accepting future or unknown backends. Thanks to that, I didn't know about mpv until now, but I'm calling mpv with rubio. Andy explains this in more precise English above.
But let's think for a moment about implementing validation.
First, it is impossible to list the players available on the local computer. (When someone places a player named excel.exe in the path, it would be challenging to determine that it is, in fact a media player.)
Second, consider checking to see if a player's command line tools are available.
In the bioinformatics field, people create workflows and use a combination of Unix tools. Shell scripts, Perl, and workflow languages. My favorite is nextflow, but it seems that there are many CWL enthusiasts in Japan. But this is not the time to talk about this. The which command is usually used to determine if the tool is available. (You may know this because you published a gem called biorobe and probably did some work related to bioinformatics.)
For example,  d-cameron, a famous Australian bioinformatician, wrote the following code (slightly modified):
write_status() {
	echo "$(date): $1" 1>&2
}

for tool in samtools bcftools gunzip tar rsync wget ; do
	if ! which $tool >/dev/null; then
		echo "Error: unable to find $tool on \$PATH" 1>&2
		exit
	fi
	write_status "Found $(which $tool)"
done

The which command is not available on Windows, so it seems that you need to use something called where.exe instead.
This way we would be able to see if command line tools are available. However, I am not confident about Windows compatibility.
If you are interested, please send me a pull request.

I am closing this because:

We provided a solution for making mpv work
We indicated we could not really validate backends
The user could always create an adapter-script (shell script, Ruby script, or any kind of script) that could adapt any player's command to work by receiving a URL as expected by the rubio-radio backend option (e.g. assuming playerxyz does not work by accepting URL directly yet by passing --url=URL, you could create a rubio-playerxyz script that could accept URL directly and invoke playerxyz correctly with it).

Also, if the issue author wants to submit a pull request with enhancements to the backend option, they are free to do so outside of this issue.


⚠ Bofrost.lu has degraded performance

In 27ac8d5, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2752 ms

Resolved: Bofrost.lu performance has improved in 64068b6 after 6 minutes.


upgrade node on app

otherwise, nothing will pass tests.

fyi, i pick this up - needed it to get some other changes working on app

https://github.com/OpenCollective/opencollective-app/pull/190


Check if grounded

When a pokemon is not grounded, certain things can be prevented from happening. This can happen due to an item, ability, field condition, volatile status, or move. Track all of these carefully and add a helper property Pokemon.grounded to check this. May also be useful to add this to an active pokemon's array data when being processed by the neural network.

The following conditions have not yet been tracked:

[ ] Gravity
[ ] Ingrain
[ ] Smack Down
[ ] Iron Ball
[ ] Item-ignoring abilities
[ ] Gastro Acid
[ ] Roost
[ ] Levitate
[ ] Telekinesis
[ ] Magnet Rise
[ ] Air Balloon

Will update this list to correspond with issues.


How can I refer the kubelet identity in bicep

I am provisioning an aks cluster using Bicep It creates two identities, one is a managed identity the I add and the second is a kubelet identity in the format AKS Cluster Name-agentpool which is auto-created.
How can I refer to this kubelet identity in another module. I tried like output kubeletid string = aksCluster.identity.principalId but it throws errors like The template output 'kubeletid' is not valid: The language expression property 'principalId' doesn't exist, available properties are 'type, userAssignedIdentities'
I wanted to give the kubelet identity acrpull permissions on car so it can authenticate with acr.

@jobinjosem would you mind sharing a Bicep code sample?

@anthony-c-martin  Thie below is the code I use
`
resource managedIdentity 'Microsoft.ManagedIdentity/userAssignedIdentities@2018-11-30' = {
name: 'test-aks-mi'
location: resourceGroup().location
}
resource aksCluster 'Microsoft.ContainerService/managedClusters@2021-03-01' = {
name: 'test-aks'
location: resourceGroup().location
sku: {
name: 'Basic'
tier: 'Free'
}
identity: {
type: 'UserAssigned'
userAssignedIdentities: {
'${managedIdentity.id}': {}
}
}
properties: {
kubernetesVersion: '1.21.2'
dnsPrefix: 'akstest.net'
enableRBAC: true
addonProfiles: {}
servicePrincipalProfile: {
clientId: 'msi'
}
networkProfile: {
outboundType: 'loadBalancer'
networkPlugin: 'azure'
networkPolicy: 'calico'
dnsServiceIP: '<IP_ADDRESS>'
serviceCidr: '<IP_ADDRESS>/16'
loadBalancerSku: 'standard'
}
aadProfile: {
adminGroupObjectIDs: [
'1b550e7b-9fqw89-4369-92ea-524a62we6b1f'
]
enableAzureRBAC: true
tenantID: 'tenantID'
managed: true
}
agentPoolProfiles: [
{
name: 'agentpool'
count: 2
vmSize: 'Standard_B2s'
osType: 'Linux'
mode: 'System'
enableAutoScaling: true
enableNodePublicIP: false
maxCount: 3
minCount: 1
nodeLabels: {}
vnetSubnetID: 'vnetSubnetID'
type: 'VirtualMachineScaleSets'
osSKU: 'Ubuntu'
osDiskSizeGB: 50
nodeTaints: []
availabilityZones: []
maxPods: 100
}
]
identityProfile: {}
}
}
resource vmoperator 'Microsoft.Authorization/roleAssignments@2020-04-01-preview' = {
name: '${guid(resourceGroup().name, 'vmoperator')}'
properties: {
roleDefinitionId: '${subscriptionResourceId('Microsoft.Authorization/roleDefinitions', '9980e02c-c2be-4d73-94e8-173b1dc7cf3c')}'
principalId: aksCluster.identity.principalId
principalType: 'ServicePrincipal'
}
}
`

Looking at this sample from the quickstarts repo, I think you need to use:
aksCluster.properties.identityProfile.kubeletidentity.objectId

Worked perfectly! Thanks a lot @anthony-c-martin for your quick help

@justinmchase - I wasn't able to find much great documentation on this, but my guess after following through the AzureCLI code for the param you're referencing is this would look something like (... are sections I've omitted):
resource kubeletIdentity 'Microsoft.ManagedIdentity/userAssignedIdentities@2018-11-30' existing = {
  scope: ...
  name: ...
}

resource aksCluster 'Microsoft.ContainerService/managedClusters@2021-03-01' = {
  name: ...
  ...
  properties: {
    ...
    identityProfile: {
      kubeletidentity: {
        resourceId: kubeletIdentity.id
        clientId: kubeletIdentity.properties.clientId
        objectId: kubeletIdentity.properties.principalId
      }
    }
  }
}

If you're able to get this working, it would be amazing if you could share a sample, or contribute it to https://github.com/Azure/azure-quickstart-templates/ for others to use!

That's pretty close, that is correct but it does return an errror:

{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"CustomKubeletIdentityOnlySupportedOnUserAssignedMSICluster","message":"Custom kubelet identity feature only supported on user assigned MSI cluster."}]}


fix: bug 2110

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

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Feature: animated properties

Toyed with this already - you can keyframe properties of materials, as well as camera rotation with the centre constraint.
This allows you to output an absolute tonne of matcaps based from a single baseline material - just animate a few values and render each keyframe individually (Viewport Render Animation instead of Image)
Ideally this would add camera movement w/ backwards compatibility, but the current setup might have to be nuked because of the contstraint requirement. We'll see.

If lighting properties can be controlled via drivers, we could implement this as an easy means to control their properties in viewport w/ labels etc, similar to a rigging panel. Could save selecting different sub viewports etc to control lighting.


[needs review] Added Relationship class to spdx-python tool

Summary
this P.R. is a part of my communitybridge project (1st evaluation). I am pretty much done with code but it needs to be debugged & reviewed.
This P.R. adds relationship (parser, builder & writer) to every format (rdf, tag, jsonyamlxml).
When running the tests, the relationship shows ERROR:
(mostly this)
doc.add_relationship(relationship.Relationship(relationship=relationship))
AttributeError: 'str' object has no attribute 'Relationship'

Files Created/Changed:

spdx/relationship.py
spdx/parsers/rdf.py
spdx/parsers/rdfbuilder.py
spdx/parsers/tagvalue.py
spdx/parser/tagvaluebuilder.py
spdx/parser/jsonyamlxml.py
spdx/parser/jsonyamlxmlbuilder.py
spdx/writers/rdf.py
spdx/writers/tagvalue.py
spdx/writers/jsonyamlxml.py
tests/test_builder.py

Status

[ ]  Debugging

[ ]  Ready to Merge

Used 'Black' formatter for all python files edited.

Thanks!
can you use an imperative style for your commit messages be more explicit?
Right now your commit stream reads a bit like this: https://xkcd.com/1296/
'Added the relationship.py file in spdx'
'Added relationship class in document class as well as introduced it …
    "Added project_details.md in local branch"
added
" updated the parsers for rdf "
correction in last push
to be continued ...
    added relation_subject & related_spdx_element
    modified parsers and relationship.py
added builders for rdf and tagvalue
    added license to relationship.py
removed relationship_type class in relationship.py file
    updated daily_work
added relationship parser in tagvalue.py
    added create_entity in rdf
added relationship in tag
    added relationship in jsonyamlxml parser & builder
updated xmlparser.py to support relationship
    added relationship writer for rdf format
added relationship writer in tagvalue & jsonyamlxml
    added tests for relationship in tests/test_buildr.py
ready for P.R.

So the simplest at this stage is to squash in one clean commit IMHO and use a proper message there.
Also can your reference a ticket for your work?

@pombredanne thank you for your suggestion, I have squashed all the commits into 1.


bug: Model selection drop down covered by left side hamburger menu

Bug Report
Description
Bug Summary:
Model selection drop down covered by left side hamburger menu when visiting Open-WebUI on a device with a large window.
Steps to Reproduce:

Navigate to Open-WebUI in browser on a computer with a large screen
Have the browser in full-screen mode or with a large window
Click the drop down on the right to select model

Expected Behavior:
Models available for selection are visible.
Actual Behavior:
Models available for selection are not visible, but are hiding under the hamburger menu per screenshot

Environment

Open WebUI Version: 0.1.123

Ollama (if applicable):  0.1.32

Operating System: macOS 14.4.1

Browser (if applicable): Safari 17.4.1 (196<IP_ADDRESS>.14)

Reproduction Details
Confirmation:

[x] I have read and followed all the instructions provided in the README.md.
[x] I am on the latest version of both Open WebUI and Ollama.
[ ] I have included the browser console logs.
[ ] I have included the Docker container logs.

Logs and Screenshots
See above.
Browser Console Logs:
n/a
Docker Container Logs:
n/a
Screenshots (if applicable):
See above.
Installation Method
Docker
Additional Information
n/a

Fixed with https://github.com/open-webui/open-webui/issues/1934

Sorry to miss this was already reported and fixed!


Revise a few docs to make it more clear

Jenkins job istio.github.io/presubmit passed

Jenkins job istio.github.io/presubmit passed

Jenkins job istio.github.io/presubmit passed


Add test correction workflow (migration)

DATABASE PULL REQUEST
Related Issue

#3417

Changes Proposed

Adds the following columns to both test_order and test_event tables:

corrected_at
corrected_by

Required to implement the requested by {name} on {date} part of the following design:

correction_type

This holds a member of an enum of valid test correction reasons

We will maintain the existing reason_for_correction column for now, which will be populated by the "Additional details" field in the test correction form

Longer-term we would like to migrate that column to, e.g. additional_correction_information to be more descriptive of its contents

Additional Information

Please see https://github.com/CDCgov/prime-simplereport/pull/3650#discussion_r849864098 and 3d3a348 for the proposed approach to migrating existing data

Testing

Create or establish any number of test result removals

Perform the migration
Verify the post-migration state of the database

All pre-existing test orders/events should have a correction reason of "OTHER" since we have no way of parsing the plaintext correction reasons

Checklist for Primary Reviewer

[x] Only database changes are included in this PR
[x] Any new tables or columns that do not contain PII are accompanied by a GRANT SELECT to the no-PHI user
[x] Any changes to tables that have custom no-PHI views are accompanied by changes to those views (including re-granting permission to the no-PHI user if need be)
[x] Each new changeset has a corresponding tag
[x] Rollback has been verifed locally and in a deployed environment

@nathancrtr I'd remove both colons on the last two headers, please.

Question for reviewers: do we want to perform a data migration here to standardize those fields?

This would look like:

Create an enum to hold valid reason_for_correction values

Copy value of reason_for_correction into the new additional_correction_information

Update all reason_for_correction values to CorrectionEnum.OTHER

Only the "other reason" case will have additional_correction_information

@DanielSass proposed inverting this approach - keeping the reason_for_correction column holding plaintext like it does now, and adding a new column for the "correction reason enum" value

I'm in favor of Dan's approach here. reason_for_correction seems like a logical place to store the user's plaintext reason. Maybe we can use correction_type or correction_category to store the enum?

I'm in favor of Dan's approach here. reason_for_correction seems like a logical place to store the user's plaintext reason. Maybe we can use correction_type or correction_category to store the enum?

@emmastephenson oh wow, thank you, correction_type is the perfect name and it managed to elude Dan and I for a whole hour 😂
Please see 3d3a348 for the implementation of the general approach and f333949 for the column name changes.


yarn react-scripts start webpack bundle.js

working with React-Hooks, we get the generic Hooks can only be called inside the body of a function component. Confirmed hooks are within the react functional component
Uncaught Error: Hooks can only be called inside the body of a function component.

[x] Tested in webpack-dev mode.

[ ] Testing in yarn start NODE_ENV=development react-scripts start

[x] Tested in docker-compose up --build, complies without any errors.

Error seems to be only attached with dev build with out docker.  may be related to issue #1088

tested in both webpack-dev and in prod build with docker and they work fine, if you remove the bundle div tag all works fine with-out error, work around for now.


Marking Repo as Deprecated and Offering Alternatives

This repo has a vulnerability that isn't being addressed. This repo seems abandoned. I wanted to offer an alternative that is working well for me with the readline sync package (https://github.com/anseki/readline-sync#utility_methods-keyinyn):
Before:
const prompt = require('prompt-sync')();
prompt('> ')

After using readline-sync:
const readlineSync = require('readline-sync');
const answer = readlineSync.prompt();

Came here looking for an alternative after noticing the npm audit warning. Thanks for sharing!

readline-sync seems now, itself, deprecated.

The node:readline module looks like it's easy enough to use by itself:
import * as readline from 'node:readline/promises';
import { stdin as input, stdout as output } from 'node:process';

const rl = readline.createInterface({ input, output });

const answer = await rl.question('What do you think of Node.js? ');

console.log(`Thank you for your valuable feedback: ${answer}`);

rl.close();

See https://nodejs.org/docs/latest-v20.x/api/readline.html.


Classic and skeumorphic Chrome 7-49 design

Supermium having the 3D Chromium icon that was used from the first beta until Chromium 11, it would be great for Windows 7, Vista (and future XP support) users to have the design that was used in the first half of the 2010's up to Chrome 49. And it can be activated or deactivated in chrome://flags regardless of the operating system.
It's just an idea, but it wouldn't be bad because of the supermium 3d icon, and also in the theme without DWM or basic, the Windows 10 title bar looks ugly.

Yeah, would be amazing to have it back, I miss that design very much.
But FYI, that old Chrome design was used up to Chrome 52, where beginning Chrome 53 up to Chrome 68, the design was flattened and got changed from blue to gray.

A significant problem is that the code that rendered the UI elements with that design was removed years ago. The tab code was rewritten from scratch because the old code did not produce anything resembling a trapezoid when used in Supermium.
Next up to is change the new-tab button and square-off the omnibox's address bar.

Thumbs up for this feature. It would be really useful and gave a native look on Windows XP. Chrome 49 looks are awesome.

Thumbs up for this feature request. It would be really useful and gave a native look on Windows XP. Chrome 49 looks, colors and icons are awesome. No unnecessary padding either, that would waste vertical real estate.

Somebody already made a Firefox based theme that mimics the old Chrome 23 based design from 2012, but runs on Firefox version 115esr so somebody could port this theme into Chromium based browsers but unlike on Firefox, there isn't a easy way to import a heavily modified theme into the browser itself as due to the nature of Chromium based theming, it dosen't let you customize the deeper menu elements as easily as with Firefox with a simple theme file. In order to make the theme work, the whole UI part of Supermium's source code has to be rewritten to allow core UI elements to be different like other browsers did to make their browser unique (such as Microsoft Edge)

Everything related to the "old Chrome UI" was controlled by --chrome-refresh-md, which had various options that changed over the years. Most of this code is not applicable to the current Chromium source code due to changes in the internal APIs and file structure, but I am trying to replicate it within the framework of the current code.
I am figuring out more and more of the UI code. I will be cautious in implementation but I am trying for further increases to customizability, which will make Supermium stand out in the field of Chromium browsers.

@win32ss Trapezoidal tabs UI flag already looks pretty good, albeit with some minor glitches related to the Win 10 frame thing. But yeah this would be nice. M49 tabstrip always looked good.

one day hopefully we will get close!


Testmunk API request requires features.zip

The "testmunk" action actually fails because the request did not include the "testcases" param.
The param is now correctly set. Before that, the required testcases.zip file is build from the testcases/-folder - when you're following the testmunk docs, it should be placed in the root-folder of your Xcode-project.
I also added the IPA_OUTPUT_PATH as default value for the TESTMUNK_IPA var.

Thanks for your contribution @johannesberdin :+1:


Changes to add pre/post deploy script to sqlproj

This PR is an extension to https://github.com/microsoft/azuredatastudio/pull/11703.
This PR completes the changes needed to support pre/post deploy script in sqlproj.
Adds the ability to add new pre-deploy and post deploy script. If more than one pre or post deploy script is added, it gets updated with "None" tag.

Coverage decreased (-0.009%) to 37.831% when pulling 5587744c5cf9891cc4bfc102982b68b251871a7f on sakshis/PrePostDeploy2 into e90341b3d282d25ad352f5d2c1f18fb6a5535fbb on main.


feat: support Coinbase wallet

Integrate Coinbase Wallet to be used with Web3Modal out of the box:
Install and integrate Coinbase's Swift SDK
Configure Web3Modal to toggle Coinbase wallet visibility
Use Coinbase Wallet as any other listed wallet
https://github.com/coinbase/wallet-mobile-sdk#coinbase-wallet-mobile-sdk

Is there a timeline for when this will be added? At the moment, I'm able to connect to Coinbase Wallet but the the sessionSettle event is never fired so there's no way to know whether or not it the connection was successful.
I see in the code that it updates the Store, but there's no public access or events fired to be consumed.


Bugfix/docker server

Fixes

Issues with docker server
Removes duplicate "Dockerfiles"
Addresses performance issues during dev (by using the new docker container, the app runs a lot faster and with less issues)
Simplify the use with docker

New Features

quick scripts to use docker via npm scripts
auto docker install
avoids manual docker installation or weird setups
auto yarn install into container
scripts to start, stop and cli (enters the docker via bash interactive)
optimizes the performance by using dockers features when using node modules and shared folders
It auto copies the required files (env and docker-compose)
Added quick shortcuts to the scripts so that:

npm run docker:start

installs, starts and runs the yarn stuff all in one
If everything is already installed, it will just start the docker and the flowise

npm run docker:stop

Stops the correct container

npm run docker:cli

enters the correct container in bash mode

Usage and instructions

Go to Instructions

thanks for the PR @knighttower !
Few question:

Is it still possible to use the docker-compose way to install Flowise via npm?
Is it still possible to use the root level Dockerfile to build & install Flowise locally?
Does the new method works across different deployments like Render, AWS, DigitalOcean, Azure, GCP - https://docs.flowiseai.com/deployment

Hello @HenryHengZJ ,
Q- "Is it still possible to use the docker-compose way to install Flowise via npm?"

A- Short answer, yes. Long answer, I added a new 'script' command to automate all that and avoid confusion and errors. This has been documented in the readme file (https://github.com/knighttower/Flowise/tree/bugfix/docker-server/docker). The new method is simple and fast, devs only have to run npm run docker:start and it will:

Copy the ENV if there is none. (it will skip if there is one present).
Run the docker-compose container.
Install Flowise (it will use the cache via Yarn if it has already been installed and skip the install if so).
Start the Flowiser server.

If anyone still wants or need to install extra stuff, they can use the npm run docker:cli or use standard docker method docker exec -it bash but using the scripts is preferred for simplicity and accuracy.
Q- "Is it still possible to use the root level Dockerfile to build & install Flowise locally?"
A- The container build is always locally to favor offline builds, customization and mostly easy maintenance of the "Dockerfile". I noticed a lot of discrepancies with the previous files and remote Docker image that it is very hard to know which one was the current one.
Q- "Does the new method works across different deployments like Render, AWS, DigitalOcean, Azure, GCP - https://docs.flowiseai.com/deployment"
A- Yes, in any service that allows the use of Docker, it will allow running the Dockerfile. With a Few exceptions where the Dockerfile is not used, like Render, Railway, Replit because they use their own Docker setup and not the Flowise image.
Note that once this PR is merged the docs there need to Updated. They seem to be outdated anyway, so this will be a good push to make updates happen at that end.
For reference: I updated the Readme files of this repo to reflect the new changes:
https://github.com/knighttower/Flowise/blob/bugfix/docker-server/README.md#-docker
https://github.com/knighttower/Flowise/tree/bugfix/docker-server/docker
Let me know if you have any other questions.
Thanks!

Reason we have 2 Dockerfiles, 1 for building image locally, and the other 1 for building via docker-compose using image from dockerhub, is because some cloud services dont support docker-compose like you mentioned Render. Will have to test thoroughly across different deployments to verify if they are still working the same. Plus, we will be merging in this PR which introduces new infrastructure change, so might hold off on this PR for a while


catch onFocus event

Can I somehow catch onFocus/onBlur events?

No, You can not catch onFocus/onBlur events at this moment. We will add this in next release.

Hey, We released a new version 1.0.35 of the library.
Please try the new version and see if it addresses your issue. If not, please open a new issue.


DTRT on Windows

As it was, it would just bomb out on any Windows integration testing. Solution found here: http://stackoverflow.com/questions/31418609/test-kitchen-serverspec-testing-exception-on-windows

:+1:

Merged as 9ddec09e3e23ed369d79f6e717e97efc9c8e5fbe


Conditions to check for any state

Objective
Sometimes we need to run the same system within different states, but not in all of them.
For example a background animation should run on both Playing and Paused states but never in GameOver state.
Currently we can do the following:
enum GameState {
    #[default]
    Playing,
    Paused,
    GameOver,
}

background_animation.run_if(in_state(GameState::Playing).or_else(in_state(GameState::Paused)))

Consider having multiple checks, it becomes spaghetti.
This code can be reduce to:
background_animation.run_if(in_any_state([GameState::LevelPlaying, GameState::Editor]))

Solution
Implementing in_any_state and state_exists_and_equals_any conditions.
Use Cases
I've used this pattern a lot in my game so I put here some examples.
Consider having a game that contains these states: LevelPlaying, Editor, EditorSimulating + others.
And a CameraPlugin which have some system.
A camera can be rotated 90 degrees only when you are in LevelPlaying, Editor and EditorSimulating.
You can manually move a camera only when you are in Editor or EditorSimulating.
pub struct CameraPlugin;

.add_systems(
    PreUpdate,
    camera_rotate_90
        .run_if(in_any_state([
            GameState::LevelPlaying,
            GameState::Editor,
            GameState::EditorSimulating,
        ])),
).add_systems(
    Update,
    camera_manual_movement
        .run_if(in_any_state([
            GameState::Editor,
            GameState::EditorSimulating,
        ])),
);

Another example is a return to main menu functionality. You can do that when you are only in some states.
This way you force that if the event ReturnToMainMenu is send from another state, nothing happens, and you make sure
another devs on your team won't create behaviour that is not intended.
pub struct MainMenuPlugin;

.add_systems(
    Update,
    return_to_main_menu
        .run_if(on_event::<ReturnToMainMenu>())
        .run_if(in_any_state([
            GameState::LevelPlaying,
            GameState::LevelPaused,
            GameState::LevelCleared,
            GameState::GameOver,
            GameState::Editor,
        ])),
);

The third example is similar to the first one, I want to run my player_logic only when I am inside LevelPlaying and EditorSimulating states.
pub struct PlayerPlugin;

.add_systems(
    PreUpdate,
    player_logic
        .run_if(in_any_state([
            GameState::LevelPlaying,
            GameState::EditorSimulating,
        ])),
)

I just want to point out that if https://github.com/bevyengine/bevy/pull/9957 is merged first, this will need some implementation adjustments (and vice versa). While there aren't really code-line conflicts here, there are conceptual changes around States that make the two PR's incompatible without some modification.

I agree.

This is well made, but feels like a pretty heavy tool without a lot of flexibility. Is this really easier than writing your own run condition?
I'd happily approve an example demonstrating this pattern though.

I added some examples from my game in the description.

Hmm okay, that's helping me understand why this might be a natural fit. Could we use the matches! machinery somehow? Then do run_if(state_matches!(GameState::LevelPlaying | GameState::Editor)), which exposes the full power of enum pattern matching in this API.

I think that's a really good point. Being able to pattern match on states would allow us to do most of what's demonstrated here, and we really want pattern matching anyway now that we can make states out of structs, nested enums, etc.

Hmm okay, that's helping me understand why this might be a natural fit. Could we use the matches! machinery somehow? Then do run_if(state_matches!(GameState::LevelPlaying | GameState::Editor)), which exposes the full power of enum pattern matching in this API.

After #9957 gets merged I can use the same pattern like there. As I saw, in that PR there it is:
in_state!(GameState, LevelPlaying { .. })
and then I can implement:
state_matches!(GameState, LevelPlaying | Editor).

Superseded by https://github.com/bevyengine/bevy/pull/10088 <3


[core][setup] Update dependencies to Python 3.

The requirements-top-level.txt was modified to remove the version
pinning of the aliyun-python-sdk-* dependencies, allowing the upgrade to
Python 3 compatible versions. The requirements.txt was updated to
reflect the Python 3 compatible versions of the project dependencies.
[note: ignoring contribution guidelines since base branch is being merged upstream as a whole]

 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.


patch: use "flux-system" namespace instead of "default" for config

The branch planner program would run inside flux-system by default, so configuration is assumed to be read from the flux-system instead of default.
Closes #760
References:

https://github.com/weaveworks/tf-controller/issues/760

@yitsushi I forgot this one : const DefaultConfigMapName = "flux-system/branch-planner"


<EMAIL_ADDRESS>-  Elevation page - Overview tab

adds Elevation page - Overview tab

Not sure if designs cover this but do we want to use bold on the token references in the caption?

@raoufswe were you given these SVG images or did you export them yourself? We may not want to use SVG for all of these images (vs compressed jpegs/pngs/webp)

@jamieomaguire I got the assets from Jordi, I do have them in PNG as well, should I change them?

Not sure if designs cover this but do we want to use bold on the token references in the caption?

will be addressed in the future as it will require a bit of changes in figma


[BUG] Unstable output for text generation

It seems that for deepspeed inference the beam size is 1. However, when I run opt-30b for inference, the generated text changed for the same input.

Hi @frankxyy - could you please provide some code to replicate this behavior? One thing to note is that you should set do_sample=False when making calls to model.generate() or pipeline() objects. This will ensure that the same output is produced each time an input is encountered.

@mrwyattii  get it, thanks


Harvest Info

I would like to propose add new endpoint to get harvester infomation.
Reason

As supernode owner I believe harvest infomation is important to them.
Implement Harvester information on Symbol explorer.

Route
/harvesters
/harvesters/{accountId}
Example HarvesterDTO
address : '9081FCCB41F8C8409A9B99E485E0E28D23BD6304EF7215E01A'
harvestStatus : Enum (disable | enable)
totalHarvestedBlocks :  100
totalHarvestedFees:  2300.000000
lastHarvestedBlock : '23410'

Remark

Aggregating data for /harvesters queries may cost inefficient performance for rest endpoint.
not sure using pagination will resolved this issue.

feedback are welcome.

I think you can drop harvestStatus because it cannot be known by REST afaik.

@evias thanks for input.

Count/  Topqueries can be quite expensive in Mongo. Unless the infrastructure of the node can cope with it otherwise won't recommend it.

@rg911 I see, the PR #93 should be able to solve my problem, and thanks for the feedback.


Update the logo

What and Why
The current logo looks more like a box and less like a tulip.
Possible Drawbacks
No response
Related Issues
No response

This is the latest iteration on logo ideas. @clizbe, @datejada and I like the second version the best, I think. It works on both light and dark background, and in smaller sizes too.

@abelsiqueira @suvayu @gnawin @g-moralesespana your opinions?

same logos but scaled down to see how they appear in a smaller resolution

I like the small change that makes it look more like a tulip, and it is still a convex region ;). I do not know about the other, but I like the two in the middle best.

I like number 2 the most. Are we voting or ranking or grading.

My vote is for the second one, too 😄

Number 2 or 3 for me.

We're voting! @suvayu you're the only one missing. :)

New question, do we want the toned-down yellow or the original BRIGHT yellow?  I think with the new design the bright might look nice. 🙃

Also, where do we put the name ("Tulipa" or "TULIPA"or "TulipaEnergyModel.jl") for the bigger logo?

If we include a name, I prefer TulipaEnergyModel or TulipaEnergy (as the organization name in GitHub). Tulipa alone may not be associated with energy, and all uppercase letters may seem like an acronym.

+1 TulipaEnergy

I am also ok with TulipaEnergy or TulipaEnergyModel, but whatever it is let's not use capital letter for the full name because the it looks like an acronym.

Needs updating in the docs


Content area and some buttons are kind of skinny on iPhone SE

Buttons - less margin/padding

Wrong project. :(


assertion failure with message: proceeds are negligible

When I sell REX, it shows the following errors:

assertion failure with message: proceeds are negligible

Note, the cpu of my eos account is enough.

LOL, the minimum REX of sellrex is 1 REX, I use 0.0100 REX for testing.


Discourage mistaken ParaTime deposits into Cipher

Fixes https://github.com/oasisprotocol/wallet/issues/2066

snapshots


moment 2.3.1 has known vulnerabilities:  severity: low; summary: Regex denial of service;

please update https://nodesecurity.io/advisories/55
@danjenkins
@rogerc
@viktort

I should probably be removed from this repo as a maintainer as I no longer have commit access. If you want moment updated why not do a PR yourself and ask @viktort to merge it?

@victort Just to clarify, @pboomgaart was pointing out that there is a pull request open waiting to be merged that addresses this issue.

@hx-markterry can you help with this from a Holiday Extras point of view?

#15 fixes this

Resolved in 0.0.7.


Commands "addnode" & "getaddednodeinfo" Added

I have added these RPCs manually in a4ad649d08c1cb05e04034080607a4b445222bdb due to merge conflicts.


ES6 updates?

var a = 1 is as global as a = 1 private would be let a = 1
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/let

I'm afraid ES6 should take another entire project, so let's try not to make it that complicated here.

Welp, I'll get started on that then!

@Rayraegah Just do it!


Missing Method getCroppedImageAsync()

Attempting to convert an old project from theartofdev version, and tried both 4.3.3 as recommended and 4.5.0, however
cropImageView.getCroppedImageAsync() does not appear to exist, although it's still referenced in the readme.

Probably a left over. Feel free to PR a removal of the method in the README.

What is the replacement for this method? @vanniktech

Attempting to convert an old project from theartofdev version, and tried both 4.3.3 as recommended and 4.5.0, however cropImageView.getCroppedImageAsync() does not appear to exist, although it's still referenced in the readme.

cropImageView.croppedImageAsync(customOutputUri = uri)

That's right. Thanks @fhalqahtani

How to use this
cropImageView.croppedImageAsync(customOutputUri = uri)

How to use this
cropImageView.croppedImageAsync(customOutputUri = uri)


recent app

add detect recent app

intercepting the "Recent apps" button would be really helpfull indeed.


[BugFix] Fix the wrong IS_NULLABLE result of system table

Fixes #27572
What type of PR is this:

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

Checklist:

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

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

Bugfix cherry-pick branch check:

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

[x] 3.1
[x] 3.0
[x] 2.5
[ ] 2.4

[FE PR Coverage Check]
:disappointed: fail : 0 / 1 (00.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/service/FrontendServiceImpl.java
0
1
00.00%
[919]

@Mergifyio backport branch-3.1

@Mergifyio backport branch-3.0

@Mergifyio backport branch-2.5

[FE PR Coverage Check]
:disappointed: fail : 0 / 1 (00.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/service/FrontendServiceImpl.java
0
1
00.00%
[919]


Can't Compile

Build FAILED.
"nanodbc-2.12.4\nanodbc.sln" (default target) (1) ->
"nanodbc-2.12.4\ALL_BUILD.vcxproj.metaproj" (default target) (2) ->
"nanodbc-2.12.4\examples\example_northwind.vcxproj.metaproj" (default target) (6) ->
"nanodbc-2.12.4\nanodbc.vcxproj.metaproj" (default target) (7) ->
"nanodbc-2.12.4\nanodbc.vcxproj" (default target) (8) ->
(ClCompile target) ->
  nanodbc-2.12.4\src\nanodbc.cpp(2614): error C2039: 'snprintf' :is not a member of 'std' [nanodbc-2.12.4\nanodbc.vcxproj]
  nanodbc-2.12.4\src\nanodbc.cpp(2614): error C3861: 'snprintf': identifier not found [nanodbc-2.12.4\nanodbc.vcxproj]
  nanodbc-2.12.4\src\nanodbc.cpp(2634): error C2039: 'snprintf' :is not a member of 'std' [nanodbc-2.12.4\nanodbc.vcxproj]
  nanodbc-2.12.4\src\nanodbc.cpp(2634): error C3861: 'snprintf': identifier not found [nanodbc-2.12.4\nanodbc.vcxproj]
  nanodbc-2.12.4\src\nanodbc.cpp(2653): error C2039: 'snprintf' :is not a member of 'std' [nanodbc-2.12.4\nanodbc.vcxproj]
  nanodbc-2.12.4\src\nanodbc.cpp(2653): error C3861: 'snprintf': identifier not found [nanodbc-2.12.4\nanodbc.vcxproj]
  nanodbc-2.12.4\src\nanodbc.cpp(2673): error C2039: 'snprintf' :is not a member of 'std' [nanodbc-2.12.4\nanodbc.vcxproj]
  nanodbc-2.12.4\src\nanodbc.cpp(2673): error C3861: 'snprintf': identifier not found [nanodbc-2.12.4\nanodbc.vcxproj]

    0 Warning(s)
    8 Error(s)

Time Elapsed 00:00:18.51

I've managed to compile just nanodbc by replacing std::snprintf by _snprintf, but a lot of other errors appeared in the project. Am I compiling it wrong?

First, you don't tell the what compiler you are using exactly, which version.
On Visual C++, std::snprintf is available since Visual Studio 2015, AFAIR.
Since, version 2.x targets C++14 and later versions of C++ standard compliance, VS2015 or later is required.

I was using Visual Studio 2013. I will update and try to compile again. Thank you very much.

I've update do Visual Studio 2015 and it gave me errors telling that the function isn't safe:

1>nanodbc.cpp(2614): error C4996: '_snprintf': This function or variable may be unsafe. Consider using _snprintf_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
1>  c:\program files\windows kits\10\include\10.0.10240.0\ucrt\stdio.h(1952): note: see declaration of '_snprintf'
1>nanodbc.cpp(2634): error C4996: '_snprintf': This function or variable may be unsafe. Consider using _snprintf_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
1>  c:\program files\windows kits\10\include\10.0.10240.0\ucrt\stdio.h(1952): note: see declaration of '_snprintf'
1>nanodbc.cpp(2653): error C4996: '_snprintf': This function or variable may be unsafe. Consider using _snprintf_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
1>  c:\program files\windows kits\10\include\10.0.10240.0\ucrt\stdio.h(1952): note: see declaration of '_snprintf'
1>nanodbc.cpp(2673): error C4996: '_snprintf': This function or variable may be unsafe. Consider using _snprintf_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
1>  c:\program files\windows kits\10\include\10.0.10240.0\ucrt\stdio.h(1952): note: see declaration of '_snprintf'
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

Then I configured the preprocessor definition _CRT_SECURE_NO_WARNINGS and it compiled but generated a link error:
1>nanodbc.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) public: static class std::locale::id std::codecvt<char16_t,char,struct _Mbstatet>::id" (__imp_?id@?$codecvt@_SDU_Mbstatet@@@std@@2V0locale@2@A)

I'm gonna try to figure out how to solve it and if I do I will commit a change. If you know how to solve it I would be very grateful.
Regards

Sorry, I saw now that all this issues were reported and fixed in master.

Yes, there have been number of fixes in the current master.
You can always check Build Status to confirm master is in shape, where AppVeyor builds are done with VS2015.


Improve test suite execution speed

I think there are a few areas for improvement in the GitHub test suite that we could address to improve the execution speed. Currently the unit tests take almost 20 minutes to run on CI. If we could reduce that it could help reduce the time it takes to validate PRs, improving our effectiveness as reviewers.
TODO

[ ] Refactor the slowest tests to run faster (see below)
[ ] Cache the installation of the dependencies, which currently take several minutes from each test job.

A prerequisite is having producible environments, as per #30.
Implemented in #84 , subject to cache total size limit.

[ ] Investigate parallelising the tests to run on multiple CPUs.

WIP attempt #41, abandoned as it seems to actually make the tests run even slower on CI.

[x]  Get CodeCov working, to help us evaluate relevant test coverage when reviewing PRs.


Installation Problem

After following the Setup, I found that I need to downgrade protobuf to 3.20 and intall wrapt, opt_einsum, gast, astunparse, termcolor, keras-preprocessing, and python-flatbuffers to load the package and model correctly.

Hi, I sadly cannot reproduce this error. Did you start from a clean environment or had packages installed already?

I followed the setup guide in Windows.
I retried it in a Linux system. No error this time.
Maybe I should retry it in Windows.


Claim about the activation functions. Index 37

In the french version "Deep Learning avec Keras et TensorFlow - 2e éd. - Mise en oeuvre et cas concrets"
page 61 index number 37 below the page
You say that biological neurons seems to implement a sigmoid curve function, which has led researchers to persist in using them, and that therefore this is an example of a case where the analogy with nature may have been misleading.
However, it seems to me that this statement is inaccurate, because based on the wikipedia page https://en.wikipedia.org/wiki/Rectifier_(neural_networks)#cite_note-Hahnloser2000-1 or the abstract of the original publication https://www.nature.com/articles/35016072 ReLu also seems to have "strong biological motivations".
I don't have enough knowledge in neuroscience to know if this is a precise point on which there is not yet a consensus even though I wanted to raise the question anyway.

Thanks for your feedback @atonkamanda, that's a very interesting remark.
I think the timeline looks like this:

1940s: researchers create the first artificial neuron and they use a step function because it has been observed that biological neurons exhibit this step-like behavior. So many biological systems saturate that this seems quite reasonable (in fact all biological systems saturate at one point, but some have a fairly linear region that they can operate in).
1960s: among many explorations, Fukushima et al. propose using the rectifier function max(0, x), now known as ReLU, but apparently people kept using step functions. Perhaps the benefits of ReLU were not apparent yet because there was no effective way of training neural nets back then. And perhaps the fact that it does not seem biologically plausible (due to the lack of saturation) may have played a role. It's hard to say.
1980s: when backprop is introduced, the sigmoid activation function is chosen because it looks very similar to a step function but it has the nice feature of being entirely differentiable, with a non zero derivative everywhere, so it plays nicely with gradient descent. The fact that biological saturation is often modelled with the sigmoid function may also have played a role. I'm not sure the ReLU activation function was even considered back then. We'd have to ask old timers like LeCun or Hinton. Note: I'm not entirely sure but I think it was Hinton who said that people stuck with sigmoid because it seemed biologically plausible. It may have been a self-critique.
2000: a paper suggests that the rectifier may after all be biologically plausible. This paper got plenty of citations, but many of them are actually quite recent. It was the ice age of neural nets anyway, so most researchers were busy with other topics.
2010s: ReLU are popularized by Glorot, Bordes and Benjio. I suspect that the 2000 paper got more traction then, to explain why ReLU is so successful.

Does this sound reasonable?


Remove empty files from a subset request

The current implementation sends contains test files to the subset endpoint even if it does not contain any tests. This is problematic especially when a user uses wantFunction/wantMethod interfaces to choose tests dynamically. For example, the Attrib plugin uses the interfaces and removes some tests.
To avoid that, I implemented the is_empty method which checks if a test file contains any test functions (or methods) recursively. With that change, the nose-launchable stop sending those empty test files to the subset endpoint.

Thank you!


Adds the standard X-Bundlephobia-User header

We've standardised on this header for API usage. In the absence of an API key, this header is required to recognise the source of traffic. It would be great if we can put this.

Hey @pastelsky,
I'll try to review this quickly and make a release.
Best regards. Adrien


Add support for .exe .appx files production and help us not install the emulator

wit hit we won't be needing ANdroid sdk

This does not appear to be requesting anything different from the other two bugs you filed at the same time; closing.


Quartiles and Impression events while playing Vast/Vpaid

How do i listen to Quartiles events while playing Vast/Vpaid?
How do i listen to an Impression event?

Any advice?

I could find impression events for VPAID. But not sure how to listen on VAST events.

+1

Oh wow this was easier than I thought.
all VAST/VPAID events are supported
    events: [
        'AdLoaded',
        'AdStarted',
        'AdStopped',
        'AdSkipped',
        'AdSkippableStateChange', // VPAID 2.0 new event
        'AdSizeChange', // VPAID 2.0 new event
        'AdLinearChange',
        'AdDurationChange', // VPAID 2.0 new event
        'AdExpandedChange',
        'AdRemainingTimeChange', // [Deprecated in 2.0] but will be still fired for backwards compatibility
        'AdVolumeChange',
        'AdImpression',
        'AdVideoStart',
        'AdVideoFirstQuartile',
        'AdVideoMidpoint',
        'AdVideoThirdQuartile',
        'AdVideoComplete',
        'AdClickThru',
        'AdInteraction', // VPAID 2.0 new event
        'AdUserAcceptInvitation',
        'AdUserMinimize',
        'AdUserClose',
        'AdPaused',
        'AdPlaying',
        'AdLog',
        'AdError'
    ]

by doing
player.on('vast.' + eventName)

@pbwilmot Can you confirm those events work for VAST as well? I am using them as vpaid.AdVideoFirstQuartile and that works. But if it works for VAST then it will be great. I don't find these events in the VASTIntegrator.js file or any of the VAST files. Only in VPAIDIntegrator.js.

You're right, it doesn't work for VAST, only VPAID. My +1 for this.


Allow subscription response to pass through the middleware

Closing this in favor of a custom stream middleware catered to MetaMask specifically to bring subscription support.


Navbar hiding compass

Hi Masashi,
I am having 2 issues with the plugin on my ipad.
When I use a normal div with height 100% I get a white space under my navbar header( see second image)
When I use fullscreen(map.showdialog) the navbar header hides the compass(see first image ).
Do you have any ideas on how this issues can be solved?
Thanks.
Here I use fullscreen(map.showdialog). The navbar hides the compass and the Google logo. How do I prevent this from happening or how do i change the location of the compass?

Here I place the map in a div. There is a white space between the map and the blue navbar header.
How do I get rid of this whitespace?

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/10531223-navbar-hiding-compass?utm_campaign=plugin&utm_content=tracker%2F637500&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F637500&utm_medium=issues&utm_source=github).

What the map plugin version do you use?
I think I already answered to simular issue in the past.
Did you check the issue list?

I use 1.2.4
I searched the issue list but I could not find a similar issue. Can you please provide a link?

https://github.com/wf9a5m75/phonegap-googlemaps-plugin/issues/242
I don't support old version of this plugin.
Please update it.

I tried updating the plugin and building the app with the new plugin but I get an error message. it says
"One of your plugins does not seem to compile for 64bit architecture. You will need to contact the plugin author. (error was: 'Id: symbol(s) not found for architecture arm64)'

Please include error line number and file name.
And I saw this error at once.
Please find the issue list at once becore asking.
On Sun, Apr 5, 2015, 11:01 PM klightning7<EMAIL_ADDRESS>wrote:

I tried updating the plugin and building the app with the new plugin but I
get an error message. it says
"One of your plugins does not seem to compile for 64bit architecture. You
will need to contact the plugin author. (error was: 'Id: symbol(s) not
found for architecture arm64)'
—
Reply to this email directly or view it on GitHub
https://github.com/wf9a5m75/phonegap-googlemaps-plugin/issues/479#issuecomment-89937571
.


Package name collision detected while running 'bosh -n deploy'

I get this error while running bosh -n deploy:
Started preparing deployment > Preparing deployment.
Failed: Package name collision detected in job routing_api_z1: template cf-routing/routing-api depends on package cf-routing/common, template cf/consul_agent depends on cf/common. BOSH cannot currently collocate two packages with identical names from separate releases. (00:00:00)
Here are the commands I ran after cloning:
. .envrc
./scripts/generate-bosh-lite-manifest ../../cloudfoundry/cf-release/bosh-lite/deployments/cf.yml ../diego-release/bosh-lite/deployments/diego.yml

# => Deployment set to `/home/ericp/git/cloudfoundry-incubator/cf-routing-release/bosh-lite/deployments/cf-routing-manifest.yml'

So try this:
bosh create release --force
bosh -n upload release
bosh -n deploy

I'm working on cf v224, so here's the version/compatibility report I'm working with:
cf-release v224
commit_hash: 65621dd0
DATE: Mon Nov 9 13:39:49 UTC 2015
DIRECTOR_VERSION:1.2992.0
CF_DEPLOYMENT_STEMCELL:bosh-aws-xen-hvm-ubuntu-trusty-go_agent/3126
DIEGO_RELEASE_VERSION:0.1440.0
DIEGO_RELEASE_COMMIT_SHA:deb51e25
DIEGO_DEPLOYMENT_STEMCELL:bosh-aws-xen-hvm-ubuntu-trusty-go_agent/3126
GARDEN_LINUX_RELEASE_VERSION:0.326.0
ETCD_RELEASE_VERSION:18

I don't see "common" anywhere in bosh-lite/deployments/cf-routing-manifest.yml (assuming that's the file 'bosh create release' uses). Do I need to move to a newer cf-release version? Or is there something else I can do?

This looks like an instance of the problem discussed at https://github.com/cloudfoundry-community/docker-boshrelease/issues/31 -- how did anyone deploy it?

And I just learned that there's a cf-routing package in newer versions of cf-release. So mark this yet another non-issue.


Add config option to allow token to be set as a url param instead of a header

Defaults to standard header format if not overridden,
otherwise will add access_token= to the url

If this commit is merged, imo the version should be bumped to 0.0.7
Also, please note that the diff for the dist files seems to contain some changes that are not part of my commit's code but rather, they show up due to some missing synchronization in a previous PR merge.

any movement on this?

This looks really good :).
@doshprompt can you rebase with master now? I'll merge afterwards.
Thanks!

@mgonto done, sorry I had some issues, please can you merge and then bump the version to 0.0.9

Yep.
I have one more remaining PR, I'll bump it in the next day :).
Thanks again!

Pushed as 0.0.9

Thanks :)


Wallet disconnection should be improved

Is your feature request related to a problem? Please describe.
The wallet disconnection does not work as in other EVM dapps like Uniswap. The selected account is just removed visually but the wallet connection remains behind the scenes.
Describe the solution you'd like
According to the investigation, there seems to be disconnect function in the polkadot-js API. We can use it to properly implement disconnection.
Describe alternatives you've considered
We should look at how polkadot dapps (e.g., Acala dapp) have implemented wallet disconnection if the above solution does not work.
Additional context

Add any other context or screenshots about the feature request here.

Closed as duplicate—this has been handled with https://github.com/interlay/interbtc-ui/pull/992 for now


Mill 0.10.9 BSP unable to initialize with nightly Metals

So I think some combination of these prs are causing things to break or behave in weird ways when using Mill as a build server with the nightly version of Metals. Mainly, the BSP server doesn't respond at all.

https://github.com/scalameta/metals/pull/4609
https://github.com/scalameta/metals/pull/4586
https://github.com/lefou/millw/pull/41
https://github.com/com-lihaoyi/mill/pull/2080

To illustrate I'll start with a fresh project.
g8 com-lihaoyi/mill-scala-hello.g8

Everything working
So I'll start with the following:

Metals version: 0.11.9 (brings in 0.4.2 of millw and sticks it in a temp dir)
Mill 0.10.9

Steps taken

Open the project
Answer "Not now" to build import
Trigger a "Switch Build Server" and select mill-bsp
Everything works as expected

.bsp/mill-bsp.json
{
  "name": "mill-bsp",
  "argv": [
    "/Users/ckipp/.cache/mill/download/0.10.9",
    "--bsp",
    "--disable-ticker",
    "--color",
    "false",
    "--jobs",
    "1"
  ],
  "millVersion": "0.10.9",
  "bspVersion": "2.0.0",
  "languages": [
    "scala",
    "java"
  ]
}

jps output is what I'd expect
❯ jps
9601 MillServerMain
9658 Jps
9628 MillClientMain
9565 metals

Stuff not working
Now I'll bump the Metals version to the latest nightly (0.11.9+131-601042ab-SNAPSHOT) which brings in the new placement and version of millw, and I'll fully clean the workspace.
Steps taken

Open the project
Answer "Not now" to build import
Trigger a "Switch Build Server" and select mill-bsp
Wait and see that Metals times out waiting for the BSP connection

.bsp/mill-bsp.json
{
  "name": "mill-bsp",
  "argv": [
    "/Users/ckipp/Documents/scala-workspace/mill-bsp-test/.metals/millw",
    "--bsp",
    "--disable-ticker",
    "--color",
    "false",
    "--jobs",
    "1"
  ],
  "millVersion": "0.10.9",
  "bspVersion": "2.0.0",
  "languages": [
    "scala",
    "java"
  ]
}

There is a mill-bsp.trace file created, but with nothing inside of it and no other files created by Mill.
When I look at the BSP trace file from Metals all I see is the following:
[Trace - 08:59:46 am] Sending request 'build/initialize - (1)'
Params: {
  "rootUri": "file:///Users/ckipp/Documents/scala-workspace/mill-bsp-test/",
  "displayName": "Metals",
  "version": "0.11.9+131-601042ab-SNAPSHOT",
  "bspVersion": "2.1.0-M3",
  "capabilities": {
    "languageIds": [
      "scala",
      "java"
    ]
  },
  "data": {
    "javaSemanticdbVersion": "0.7.4",
    "semanticdbVersion": "4.6.0",
    "supportedScalaVersions": [
      "2.13.10",
      "2.12.17",
      "2.12.16",
      "2.12.15",
      "2.12.14",
      "2.12.13",
      "2.12.12",
      "2.13.5",
      "2.13.6",
      "2.13.7",
      "2.13.8",
      "2.13.9",
      "2.11.12",
      "2.12.9",
      "2.12.10",
      "2.12.11",
      "2.13.1",
      "2.13.2",
      "2.13.3",
      "2.13.4"
    ]
  }
}

So the request is sent, but never responds.  Looking at the output of jps I do see that Mill has started:
❯ jps
10118 MillClientMain
10109 metals
10126 MillServerMain
10127 Jps

Other research
I also tried reverting the place that Metals stores the millw back to a tmp dir and that still doesn't work. For example the BSP entry in this case looks like:
{
  "name": "mill-bsp",
  "argv": [
    "/var/folders/fq/nx_jsnyd6550xp03czx898d40000gn/T/metals17064985890367699422/millw",
    "--bsp",
    "--disable-ticker",
    "--color",
    "false",
    "--jobs",
    "1"
  ],
  "millVersion": "0.10.9",
  "bspVersion": "2.0.0",
  "languages": [
    "scala",
    "java"
  ]
}

And the same behavior of an initialize being sent, but not responded to.
Conclusions
From what I can tell it just seems problematic that the BSP entry is pointing to the millw file. I'm not 100% sure how to dig in further to see why Mill isn't responding here or why pointing towards millw is an issue. Any ideas or anything else I can provide?

Thanks for the report!
It took me a while to see what the issue is, but I think, as we now pass -D as the first option, Mill is no longer correctly switching to the BSP mode. For this, the --bsp options needs to come as a first option. I just checked with other options, which need to be given as the first one like --repl or --interactice, and indeed, they no longer work.
This is actually an issue with the bundles mill script in Mill, as well as with millw 0.4.4.


Failure to build unity catalog server on Macbook

Describe the bug
The Armeria dependency does not include the netty classfiles necessary to successfully compile and run unity catalog.
This can be hacked around by specifying the transitive dependency (using "netty-all"). It is not yet clear why we must specify the upstream dependency manually.
To Reproduce
Steps to reproduce the behavior:

build/sbt package
bin/start-uc-server

Exception in thread "main" java.lang.NoClassDefFoundError: io/netty/channel/ChannelPipeline

Expected behavior
I expected the script to successfully start the UC server.
System [please complete the following information]:

OS: Macos Sonoma (14.4.1 (23E224)), Apple M1 Max, Macbook Pro

@abrassel Thanks for finding the issue.
I couldn't repro the issue on a new checkout of the repo on a Macbook Pro with MacOS Sonoma after deleting my .ivy2 and .sbt folders. Would love to see a reliable repro.

I'll let you know tomorrow!

@abrassel closing this issue since PR #67 is merged. Please reopen if you still see this issue.


Bulk Recommend

https://trello.com/c/61ShO8r0/5230
Context
Changes proposed in this pull request
Guidance to review
Important business

[ ] Does this PR introduce any PII fields that need to be overwritten or deleted in db/scripts/sanitise.sql?
[x] Does this PR change the database schema? If so, have you updated the config/analytics.yml file and considered whether you need to send 'import_entity' events?
[ ] Do we need to send any updates to DQT as part of the work in this PR?
[ ] Does this PR need an ADR?

NB: Please notify the #twd_data_insights team and ask for a review if new fields are being added to analytics.yml
TODO

[ ] Remove schema fluff (@d-a-v-e )
[ ] Check there are no more TODOs in code
[x] revert sample size in example data generator lib/tasks/example_data.rake:148 sample_size = rand(4...8)
[ ] Bulk recommend errors should go to BigQuery, the other new tables shouldn't
[x] Make sure the accordion page is set back to limit 50 per accordion, not 5

 Deploy bulk recommendation feature


feat: add schematics test

Description
Added schematics test
https://github.ibm.com/GoldenEye/issues/issues/5545
Release required?

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

Merge actions for mergers

When merging, use a relevant conventional commit message that is based on the PR contents and any release notes provided by the PR author. The commit message determines whether a new version of the module is needed, and if so, which semver increment to use (major, minor, or patch).
Merge by using "Squash and merge".

/run pipeline

/run pipeline

@jor2 Its the DA tests in https://github.com/terraform-ibm-modules/terraform-ibm-landing-zone/blob/main/tests/pr_test.go we want to update to use schematics, not in this repo


Retry running conformance tests as part of runtime tests

Brings back https://github.com/fermyon/spin/pull/2663
This time we skip tests that require Docker when docker is not installed.
The first commit is equivalent to https://github.com/fermyon/spin/pull/2663 so the only new code is in the subsequent commit.

I think we should maybe require explicitly opting out of docker tests (via e.g. ugly env var) rather than detecting whether docker is installed.

I don't have a strong opinion here. What are your reasons for this? Allowing people to filter out docker based tests locally even when they have docker installed?

I don't have a strong opinion here. What are your reasons for this? Allowing people to filter out docker based tests locally even when they have docker installed?

Just "don't make it too easy to skip tests accidentally"


service_sysv_linux issue with for operator once using dash

Hi.
for operator in service_sysv_linux is incorrect for dash.
To get it worked correctly for all shells it should be changed from {1..10} to $(seq 1 10)

Here is the pull request to fix it
https://github.com/kardianos/service/pull/102

Some history behind this problem,  starting with Debian Squeeze,  the default /bin/sh shell was changed from bash to dash.    Because of this,  any scripts that use the #!/bin/sh shebang that may run on Debian/Ubuntu, such as the kardianos init.d scripts, cannot use bash enhancements.   Brace expansion for sequences {x..y} was added to bash in version 3.0 and is not supported in dash.    The shellcheck static analysis tool can be used to catch these problems.


Locked wallet message always shown

Misleading message: Info: Minting suspended due to locked wallet

That notice should disappear once wallet has been unlocked.

Although wallet has been unlocked (Correctly reported as such in the status bar of the wallet); the notice still shows up

Start bitcorn-qt
Unlock wallet

bitcorn v3.0.0; prebuilt binary from github releases

Linux x86_64

Arch linux with GNOME Shell 3.34.2

Closing issue as it relates to the blockchain not yet being at Proof-of-Stake height and is no longer relevant.


Btree indexes on pg_catalog tables may get broken

It first seemed as a bug in zenith_ctl zenithdb/console#438, but recently it happened again with a cluster "shy-disk-996824":
       id        |              tenant              |             timeline
-----------------+----------------------------------+----------------------------------
 shy-disk-996824 | d8d2a80d7159c4c1be3ebb48ae138f02 | 4cb7130ac08e2f2019fc919b4d9fe46b

and I did an investigation today. At a first sight everything looks fine:
postgres=# select rolname, oid from pg_roles
;
          rolname          |  oid
---------------------------+-------
 zenith_admin              |    10
...
 stepashka@zenith          | 16384
(13 rows)

postgres=# select datname, oid, datdba from pg_database;
  datname  |  oid  | datdba
-----------+-------+--------
 postgres  | 12972 |     10
 main      | 16385 |  16384
...
(4 rows)

postgres=# select oid, rolname from pg_roles where rolname = 'stepashka@zenith';
  oid  |     rolname
-------+------------------
 16384 | stepashka@zenith
(1 row)

But zenith_ctl fails on:
postgres=# ALTER DATABASE "main" OWNER TO "stepashka@zenith";
ERROR:  role "stepashka@zenith" does not exist

My first guess was that there is a problem with indexes, and it seems so:
postgres=# select oid, rolname from pg_roles where rolname = 'stepashka@zenith';
  oid  |     rolname
-------+------------------
 16384 | stepashka@zenith
(1 row)

postgres=# set enable_indexscan=on;
postgres=# set enable_seqscan=off;

postgres=# select oid, rolname from pg_roles where rolname = 'stepashka@zenith';
 oid | rolname
-----+---------
(0 rows)

So it seems that indexes on at least system catalog were damaged. Bad news is that after my experiments this particular cluster got totally broken and now responds with
ERROR:  could not read block 4 in rel 1663/12972/2704.0 from page server at lsn 0/016A91E8
DETAIL:  page server returned error: Timed out while waiting for WAL record at LSN 0/16A91E8 to arrive, last_record_lsn 0/16A83B8 disk consistent LSN=0/16A83B8

on each query. And also we don't have any tools like amcheck installed on the computes by default. Good news is that this issue reproduces stably on staging, and e.g. cluster "tiny-wave-892101" is also affected.

decoded log records from safekeeper:
rmgr: Heap        len (rec/tot):     54/  1626, tx:        733, lsn: 0/01695D68, prev 0/01695D48, desc: INSERT off 13 flags 0x01, blkref #0: rel 1664/0/1260 blk 0 FPW
rmgr: Btree       len (rec/tot):     53/   553, tx:        733, lsn: 0/016963E0, prev 0/01695D68, desc: INSERT_LEAF off 12, blkref #0: rel 1664/0/2676 blk 1 FPW
rmgr: Btree       len (rec/tot):     53/   353, tx:        733, lsn: 0/01696610, prev 0/016963E0, desc: INSERT_LEAF off 13, blkref #0: rel 1664/0/2677 blk 1 FPW
rmgr: Transaction len (rec/tot):     82/    82, tx:        733, lsn: 0/01696778, prev 0/01696610, desc: COMMIT 2022-01-12 04:23:25.706425 PST; inval msgs: catcache 11 catcache 10

1260 is the pg_authid and 2676 and 2677 are the indexes on the catalog. the concern was the indexes were not properly updated.
next step is to validate the TID used in the index tuples match (0, 13) as per insert log record @0/01695D68

from the Safekeeper data, heap insert above (written as FPW) inserts a role name stepashka@zenith, the commit is recorded  on 2022-01-12 11:23:25.706425 UTC (there's no exact timestamp for LSN 01695D68, but it's hard to believe that LSN 01696778 is that that far off) while the timestamp of the delta layer on page service is 2022-01-14 20:59
@hlinnaka had successfully reproduced the case (twice), and the page server did not have the page modification replicated.
following needs to be validated:

Correct read page LSN is used after restart (currently it uses XLogCtlData.lastWrittenPageLSN, what is this inited @ startup to?)
Read requests should not succeed when reading @lsn not known to the Pageservice
Page read should log a warning when request has to wait longer than "A timeout value" -- Stuck read requests should be alarmed on
Adequate logging exists to correlate read errors with replication state between Safekeeper and Page service (log highest ingested LSN for each of the tenant/timeline)

No wait, there's the disk_consistent_lsn = oldest_pending_lsn; assignment before the break. I missed that. So that code looks correct to me, after all.
I still suspect there's something wrong with this checkpoint logic though. Something that causes us to write a too-new disk_consistent_lsn to the metadata file, without having actually flushed all the layers older than that to disk.

I was able to narrow this down to a simpler Python repro script. Attached. Copy it into test_runner/batch_others/, and run with ZENITH_BIN=../target/release pytest-3 -s -vv batch_others/test_pageserver_restart.py
test_pageserver_restart3.py.txt

There are two bugs in the script. After fixing them
test_pageserver_restart4.py.txt
test is passed at gc_cutoff_rwlock branch.
But my test is still reproduce error at 92 iteration.

There are two bugs in the script. After fixing them test_pageserver_restart4.py.txt test is passed at gc_cutoff_rwlock branch. But my test is still reproduce error at 92 iteration.

Interesting, so maybe this is the same GC bug? That's surprising, though the test is short, I don' think GC kicks in during it. I don't see signs of GC removing anything in the pageserver log. Does the script reproduce the error for you on 'main' branch?

Please notice that gc_loop sleeps after gc_iteration. So even with large timeout GC still can happen. To disable GC it is necessary to set gc_period to 0.

With main branch I got:
E       psycopg2.OperationalError: connection to server at "localhost" (<IP_ADDRESS>), port 15008 failed: FATAL:  role "testuser" does not exist

But unfortunately (or fortunatelly) even with  gc_cutoff_rwlock + xlog_recovery +  gc_cutoff_v2 my tests deterministically fail at 92 iteration.

I wonder why the following code removing future delta layers is correct:
                // The end-LSN is exclusive, while disk_consistent_lsn is
                // inclusive. For example, if disk_consistent_lsn is 100, it is
                // OK for a delta layer to have end LSN 101, but if the end LSN
                // is 102, then it might not have been fully flushed to disk
                // before crash.
                if deltafilename.end_lsn > disk_consistent_lsn + 1 {
                    warn!(
                        "found future delta layer {} on timeline {}",
                        deltafilename, self.timelineid
                    );

                    rename_to_backup(direntry.path())?;
                    continue;
                }

disk_consistent_lsn=0/560C73F0
gc_cutoff_lsn=0/5FEF4F90
Result:
rel_1663_13010_1259_0_0_000000000169A9A0                         rel_1663_13010_1259_0_0_000000000169A9A1_000000005FE18180.0.old  rel_1663_13010_1259_0_0_000000005FE18180.0.old

So we removed image layer at FE18180 and delta layer at 169A9A1, keeping only image layer at 169A9A0 .
But it means that we loose all updates from 169A9A0 till 560C73F0, don't we?

I do not completely understand why with such recovery policy the problem happen only at 92 iteration. Below are more details which my somehow clarify the test behavior:
I am running my test with the following parameters:
checkpoint_distance = 256Mb
checkpoint _interval = 100s
gc_horizon=64Kb
gc_interval=1s

Presence of pg_xact layer (which contains very few records) makes it not possible to advance disk_consistent_lsn:
TimelineMetadata { disk_consistent_lsn: 0/560C73F0, prev_record_lsn: None, ancestor_timeline: None, ancestor_lsn: 0/0, latest_gc_cutoff_lsn: 0/5FEF4F90, initdb_lsn: 0/169A928 }
```

In the log I see:
```
the oldest layer is now inmem-pg_xact_0000_0_000000000169A9A1_FFFFFFFFFFFFFFFF which is 165928072 bytes behind last_record_lsn
```

So the difference between gc_cutoff_lsn: 0/5FEF4F90
and disk_constent_lsn: 0/560C73F0 is exactly reported 166Mb.


Feature request: zip file deployment

Summary: support first-class deployment of zip files, with deployment status, history tracking, locking, deployment scripts, kudusync, etc.
App Service integration with VSTS is continually improving and awareness and usage of all brands of CI/CD systems is growing. As a result, more App Service users are deploying already-built artifacts to App Service, as opposed to deploying directly from source control and letting Kudu drive the build process.
MSDeploy is a purpose-built solution to this problem, but it is not cross platform, and it is not realistic to expect all customers of App Service (some of whom use very few Microsoft tools, or none at all) to be able to understand and use it. Doubly so with the introduction of App Service on Linux.
Zip files are easy to create, use and understand on any platform. They are the best way to move multiple files to App Service in most situations, especially with Kudu's zip API that automatically extracts the contents, so people often use them for these kinds of deployments. On Linux, this workflow is currently the only real option for such deployments.
Unfortunately, the zip API is purely a filesystem operation. It does not make use of a number of features that already exist in Kudu that are designed to make deployments safe and easy: history tracking, redeployment, locking semantics, running of deployment scripts (including smart file synchronization with kudusync), etc.
I propose we add support zip files as a first-class deployment source in order to better support deployments from external CI/CD/build systems, especially for App Service on Linux users.
Early thoughts on features:

Support zip files as a "fetch" deployment provider - allow users to provide a URL to a zip file and deploy from it. Consider the need for auth against this URL as well.
Support "push" deployment of zip files - be able to POST a zip file directly to an endpoint, similar to the existing zip API, but start a full deployment instead of just an extract operation. This could offer both synchronous and asynchronous modes, in the same way that the current fetch handler supports isAsync.
Support redeployment from previously-specified zip files.
Potentially support .tar.gz and/or other archive formats, especially on Linux.
Consider a way to provide deployment metadata in the zip file or in the deployment request, such as with a well-known filename, to support filling in the deployment status and history.

Thoughts on implementation:

Looking at the way that the OneDrive and Dropbox providers work within the deployment system should provide a good jumping-off point, not for their use of special APIs, but for the fact that they are simply collections of files and not source control management systems with branches, tags, commit IDs, etc.
May need to consider revisions to the detection system that Kudu uses to determine what kind of scripts to create, or maybe a simpler/more discoverable way to indicate that Kudu should only do a "basic" deployment (kudusync copy only). Users should be able to deploy from source via zip files, and so detection and build script generation should still work properly, but it will likely be more common to use them to deploy already-built artifacts. The nature of Kudu's presence-based detection system makes it likely that it will detect the need for a build script even for already-built artifacts on most app stacks.
The .NET zip APIs allow for manipulation and introspection of zip files in addition to simply extracting them. There is probably a lot of optimization that could be done relative to only extracting specific files, etc. There may be some special implementation needed if this is to be done in conjunction with kudusync.

Random thoughts:

We should focus on the 'push' scenario first, which is easier to use. Also, msdeploy does already support the cloud hosted zip scenario even cross platform, so that part is sort of covered.
Good point that maybe we don't want the whole deployment pipeline. Does it even make sense to support a custom deployment script if the zip is expected to contain everything that should go in wwwroot? Maybe not.
The zip introspection could be most optimal, but probably a little hard to pull off. Maybe we shoudl start simple: unzip the whole thing in a local tmp folder, and KuduSync from that to wwwroot.
It's hard to provide 'redeployment from previously-specified zip files' unless we store the historical zip files, or build a git repo on the fly to keep history (we do this from Dropbox I think). Probably simpler to not support that.

So high level, we kind of want the same as what msdeploy provides, but with plain zip.

I am going to start prototyping this, starting with the push scenario, as you called out.

Linking PR: https://github.com/projectkudu/kudu/pull/2570

Hi
If the problem persists and is related to running it on Azure App Service, please open a support incident in Azure:
https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request
This way we can better track and assist you on this case
Thanks,
Joaquin Vano
Azure App Service


local installation of node exporter

Hello,
As our systems do not have any internet connectivity, installation must be done by local available files.
Node Exporter was installed with option node_exporter_binary_local_dir.
With v0.20.0 commit 3c5d710 "refactor(node_exporter): delegate common tasks to _common role" this has been removed.
How can local installation be performed after this change?
BR
Christian

If you are mirroring the binaries locally then you can modify the node_exporter_binary_url variable to point to your mirror.
Or you can use the --skip-tags node_exporter_download or --skip-tags download if you place the files in the directory of node_exporter_local_cache_path, either by using the default dir or you can modify the variable and use a custom directory.

@gardar But can't that only be applied from the command line and at the risk of impacting other tasks/roles that use the same tag, doesn't it?
Is there a straightforward way to install it in an airgap environment similar to the removed local_dir option?

@gardar Is there a way to define this in the playbook?

Perhaps by adding the ANSIBLE_SKIP_TAGS or ANSIBLE_RUN_TAGS environment vars to the include role task, although I haven't tried it myself.
environment:
  ANSIBLE_SKIP_TAGS: node_exporter_download

@gardar doesn't work unfortunately. Could we bring back the ability to install from a local package please?

Thanks for the suggestion @gardar. That doesn't work unfortunately.
I suggest reintroducing the option to just pass the location of the downloaded archive. I'm developing a playbook now and I'm facing difficulties making this work with the role.

Just to confirm, I got it working exatcly as desribed by @gardar.
For the ansible-playbook command I´ve added the option --skip-tags node_exporter_download on command line.
And inside the role as options: node_exporter_local_cache_path: directory_on_controller where the node_exporter file was placed.


start_date and end_date widget working for project/activity

I still think the fieldname of project_activity should be changed to start_date instead of date(consistency!)

Example of a jQuery UI widget using widget factory:
https://github.com/nursix/eden/blob/master/static/scripts/S3/s3.ui.hierarchicalopts.js#L12
...and how it is injected:
https://github.com/nursix/eden/blob/master/modules/s3/s3widgets.py#L6285
There are many more examples in static/scripts/S3 and static/scripts/ui - some are less, some are more complex. Datepicker itself is a UI widget. The principle is always the same, so there's plenty of examples...

Example of a jQuery function (not a UI widget, but still well encapsulated):
https://github.com/nursix/eden/blob/master/static/scripts/S3/S3.js#L1282
...and how it is injected:
https://github.com/nursix/eden/blob/master/modules/s3db/req.py#L638
This wouldn't have the this.element context, though - so the widget pattern seems better for this case.

So all injections like these should be changed accordingly:
https://github.com/flavour/eden/blob/master/controllers/project.py#L246

@gauravmittal1995: ^ I think the above two comments will help you

@nursix  and @raj454raj : Thanks :)


Bug: Weapons with Thrown property not considering DEX as bonus

Kiwi4BBQ said:

I just noticed that the ranged attack column does not treat thrown spears as ranged attacks for the purpose of +1 to Ranged Attacks and Damage, nor does it allow me to use Dexterity for the purpose of throwing the spear either. As you can see, it doesn't apply the +1 to damage, but it does apply the +1 to attack rolls.

As per the latest core rules PDF. Thrown weapons can use STR or DEX bonus when attacking at range.


Make app.js and executable script

Add #!/usr/bin/env node, and make it have execute permission. Also add "test": "./app.js < test/in.txt > test/out.txt" to package.json scripts to execute it. Add out.txt file to .gitignore.

Merged with master, closing.


fix: ux improvement on docs page

Fixes Issue
Closes #6096

Changes proposed

Check List (Check all the applicable boxes)

[X] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[X] All new and existing tests passed.
[X] This PR does not contain plagiarized content.
[X] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

Thank you for your contribution
Please remove generated files, this might be because you have enabled GitHub actions on your fork

I have removed the generated files now


Use of exclamation mark breaks will be encoded to the wrong base64

When a password for a client contains a exclamation mark the base64 will be like "Test%21" instead of "Test!".

Used old implementation


对没有加引号的属性没有高光效果

我看看能不能自己改改看。

目前使用 element UI 的时候, 也遇到了这个问题, 请问你解决了么?

This is working properly now. We will be releasing a new version soon which should have this included.
I'm closing this issue now, please feel free to re-open the issue if you continue experiencing problems.


[md/mdx] More MDX to Markdown page

New or updated content

Another pass bringing more MDX to the forefront, including renaming the page title. Also some small edits throughout.
It's not the canonical source for all the MDX info, but it's more like the "quick start" version to show it can be used pretty much just like standard Markdown files, with lots of links to all the integration details and the differences. It's a good "first place" for people to be exposed to the MDX option, alongside reading about Markdown, because so many of the "built-in" basics work the same.

Hi @sarah11918, one thing I really like about MDX is that you can pass custom components for default html elements (h1/6, img, a, code, pre, etc.) with export const components = {}. The names comes from the Table of Components for MDX.
There's an example of it here, but could be nice to highlight in the docs: https://stackblitz.com/github/withastro/astro/tree/latest/examples/with-mdx?file=src%2Fpages%2Findex.mdx
Would you welcome an additional section in the MDX integration guide?

Hey @kylebutts! Can you make a Docs Issue asking this (since, as you've already noted, we're keeping most of the non-basic MDX stuff on the Integrations page itself, not here on this page) and tag Ben "bholmesdev" on it? I'd like him to weigh in on this, since he's doing all the MDX stuff right now (and I don't want to bother him with a ping to this PR. That's the best way to keep this conversation organized! Thanks!

Ok, @delucis @Yan-Thomas, after incorporating this with the multiple changes this page has gone through, I think the PR now just adds "and MDX" in all the appropriate places where I felt it should be prominent.
Other than one existing phrase that it sounds like we could improve ("In Astro...."), does this otherwise serve that purpose of just bringing more MDX to the party? More Markdown/MDX planning/discussion to come separately!


Plugin creation fails for pnpm

Describe the bug
Create fails for pnpm due to missing version constraint for the package manager field in the package.json
Error:
✖ Running `pnpm install`..
file:///Users/xxx/.npm/_npx/ca700ea613ccf9d4/node_modules/execa/lib/error.js:59
		error = new Error(message);
		        ^

Error: Command failed with exit code 1: pnpm install
Usage Error: Invalid package manager specification in ../../package.json; expected a semver version

$ pnpm ...
    at makeError (file:///Users/xxx/.npm/_npx/ca700ea613ccf9d4/node_modules/execa/lib/error.js:59:11)
    at handlePromise (file:///Users/xxx/.npm/_npx/ca700ea613ccf9d4/node_modules/execa/index.js:119:26)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async S (/Users/xxx/.npm/_npx/ca700ea613ccf9d4/node_modules/@storyblok/field-plugin-cli/dist/main.cjs:1:1594)
    at async R (/Users/xxx/.npm/_npx/ca700ea613ccf9d4/node_modules/@storyblok/field-plugin-cli/dist/main.cjs:7:885)
    at async Pe (/Users/xxx/.npm/_npx/ca700ea613ccf9d4/node_modules/@storyblok/field-plugin-cli/dist/main.cjs:15:77)
    at async Te (/Users/xxx/.npm/_npx/ca700ea613ccf9d4/node_modules/@storyblok/field-plugin-cli/dist/main.cjs:17:401)
    at async Command.<anonymous> (/Users/xxx/.npm/_npx/ca700ea613ccf9d4/node_modules/@storyblok/field-plugin-cli/dist/main.cjs:20:3468) {
  shortMessage: 'Command failed with exit code 1: pnpm install',
  command: 'pnpm install',
  escapedCommand: 'pnpm install',
  exitCode: 1,
  signal: undefined,
  signalDescription: undefined,
  stdout: 'Usage Error: Invalid package manager specification in ../../package.json; expected a semver version\n' +
    '\n' +
    '$ pnpm ...',
  stderr: '',
  failed: true,
  timedOut: false,
  isCanceled: false,
  killed: false
}

To Reproduce
Steps to reproduce the behavior:

run npx @storyblok/field-plugin-cli@latest
Select pnpm
Select multirepo, vue 3 (looking at the code this problem probably exists for multiple templates)
See error

Expected behavior
Pnpm install starts and succeds.
Desktop (please complete the following information):

OS: macOS (13 and 14)
Versions: Node 18.15.0 with pnpm 8.6.5

Hello @hoersamu Thanks for reporting this issue.
I just tested it and it actually worked on my machine.

standalone + vue 3 template
monorepo + vue 3 template

both worked. I'm using Node 18.16.0 with pnpm 8.6.7, which isn't that different from yours.
Maybe could you post your package.json that possibly could've caused this issue of Invalid package manager specification in ../../package.json; expected a semver version error"?

Hey @eunjae-lee
I'll post the package.json later today. I tested it on two MacOs devices (one with nvm and corepack and one with "normal" node and pnpm installations). I'll try it with my Win PC later today and update my report.

Hey @eunjae-lee
Sorry for the delay. This is the root package.json file:
package.json
I can't reproduce the polyrepo problem but the monorepo problem is still reproducible.
I asked my collegues to test this too:
Node 18.15.0 + pnpm 8.12.0 -> No Problem
Node 18.15.0 + pnpm 8.14.0 -> Error
Node 18.15.0 + pnpm 8.6.11 -> Error
Node 18.15.0 + pnpm 8.6.5  -> Error
There is also a schema warning in the package.json:
String does not match the pattern of "(npm|pnpm|yarn|bun)@\d+\.\d+\.\d+(-.+)?".

I looked up the spec (https://nodejs.org/api/packages.html#packagemanager) and the officially need name@version.

Hm this issue might be related to corepack.
Most of my organization has corepack enabled so this might explain why we can all reproduce it with various pnpm versions.

@hoersamu Oh, I don't have corepack enabled. It might be the reason why I cannot reproduce it.
Do you think if we update the package.json to include<EMAIL_ADDRESS>instead of pnpm, will it solve your problem?

@eunjae-lee Honestly i would remove it. This field in the package.json is marked as experimental and corepack specific.
I would recommend to set the engines field instead: https://docs.npmjs.com/cli/v10/configuring-npm/package-json#engines
If you want to keep it you could also set it to * (or latest or stable).

@eunjae-lee Honestly i would remove it. This field in the package.json is marked as experimental and corepack specific.
If you want to keep it you could also set it to * (or latest or stable).

Thanks for the feedback. Then could you give it a test by removing that field, and see if it works for you?

Hey @eunjae-lee
* Apparently star also doesn't work but I created a PR where I set the pnpm version to the latest stable release. This fixes the issue.


Developer documentation updates

This adds instructions on running tests in other browsers and instructs people to use Node 8.  The package-lock.json means we get the same version of dependencies everywhere.

I think that if we add package-lock.json, we also should enable greenkeeper-lockfile otherwise gk will only update the package.json

Good call. Please create a pull request.

I think that if we add package-lock.json, we also should enable greenkeeper-lockfile otherwise gk will only update the package.json

We're running into the same issue described in greenkeeperio/greenkeeper-lockfile#44 (see https://travis-ci.org/openlayers/openlayers/builds/265595019 for example).  I tried to troubleshoot but think it is not worth the effort at this point.
I'll remove the package-lock.json until more people are using an updated npm and things are more stable.


Replication do not sync after changed

Hi all,
I've two Harbor 0.4.5, A and B. "A" is replicating a Project on "B".
After replication is completed, all images in Project are copied. But, if I remove one image replicated on "B", this image is no more replicated again. I hopped that Harbor "A" would be copied this image once again and keep replicated all images, but didn't. I've waited for 3 days, and nothing happen.
However, If I restart (disable/enable) the Replication job, the Image from Harbor "A" is copied to "B".
Is that a normal feature or a Issue? thanks.

It is working as design.

Should not the Source maintain a "Replica" similar to it? Even though a user have removed accidentally a Image in Destination?
So in that case, the Source would send a new Image to Destination.

We call it replication policy because it's uni-directional.
So source will not know what happen to destination.

Would it be better if the Replication reapply the Policy from time to time, like a crond entry? Rather than disable and enable the Replication Policy and a new Image be copied to the Destination again?

The destination is not supposed to delete the image in a one-way replication scenario. It is not realistic for the source to check periodically whether the destination has deleted some images. This not only wastes bandwidth, but also it is hard to predict the behavior of the replication. Stop and restart the policy helps resolve this issue.
Since this is working as design, closing it for now. Please reopen if there is a need.


Bump ember-cli-version-checker version 🚀

In order to fix deprecation messages as described in https://github.com/ember-cli/ember-cli/issues/7408, we need to update to the latest version of ember-cli-version-checker.
This change also fixes a bug in test-framework-detector where root property was never passed in. In ember-cli-version-checker@2+, we stopped falling back to this.project.root property.

@twokul looks like CI is unhappy since it's still running on Node 0.12, merging as the others seem okay. If you have some time could you update the Node versions?

Can we get a release with this change? I would like to PR ember-cli to use this.
The version of ember-cli-legacy-blueprints that is is currently in ember-cli is pulling an old ember-cli-version-checker into every app, and that version checker breaks yarn workspace support.

@ef4 unsure if I have release right but let me try.

@ef4 it should be deployed soon, pushed a new tag https://github.com/ember-cli/ember-cli-legacy-blueprints/tree/v0.2.0