Add a test for 8.2.3391: Resizing a window crashes with showbreak and breakindentopt

thanks!

Hi Bram,
On Thu, Sep 2, 2021 at 11:05 AM Bram Moolenaar @.***>
wrote:

Thanks for creating this test.
There is another check for n_extra becoming negative, and if I comment it
out no test fails.
Perhaps you can manage to write a test for that one too?
This is in line 1215 of src/drawline.c
I created a test that exercises this line. But I ran into some bugs.
If you source the following script:

10new
20vnew
call setline(1, repeat('aa ', 200))
setlocal breakindent breakindentopt=shift:4 linebreak showbreak=>>
setlocal number
set cpo+=n
normal 12gj
redraw!
normal $
redraw!
You will see that the cursor is positioned a few characters before the end
of the line and it cannot be moved to the end of the line. Also, if you move
the cursor to the left by pressing "h" quite a few times (to cause the
screen
to scroll down), you will see the cursor can be positioned on the
'showbreak' characters.

Yegappan

Thanks for creating this test.
There is another check for n_extra becoming negative, and if I comment it
out no test fails.
Perhaps you can manage to write a test for that one too?
This is in line 1215 of src/drawline.c

I created a test that exercises this line. But I ran into some bugs.
If you source the following script:

10new
20vnew
call setline(1, repeat('aa ', 200))
setlocal breakindent breakindentopt=shift:4 linebreak showbreak=>>
setlocal number
set cpo+=n
normal 12gj
redraw!
normal $
redraw!
You will see that the cursor is positioned a few characters before the end
of the line and it cannot be moved to the end of the line. Also, if you move
the cursor to the left by pressing "h" quite a few times (to cause the
screen
to scroll down), you will see the cursor can be positioned on the
'showbreak' characters.

It looks like this happens because the " >>" in the first line is not
counted, thus when w_skipcol is non-zero.  It's also strange that there
is a space before ">>".  Perhaps Christian knows what needs to change to
fix this.
--
The budget process was invented by an alien race of sadistic beings who
resemble large cats.
(Scott Adams - The Dilbert principle)
/// Bram Moolenaar -- @.*** -- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///


Pattern for pulling user from JWT

If consumers follow JWT standards, Warthog should make things really easy.  For instance:

If using JWTs
...and JWT comes in through authorization header
...and the header is of form Bearer <token>
...and we assume the JWT has an id field in it that is the user's ID

Then we should be able to:

Pull the token out and put it in context
Pull the user ID out and put it in context
Provide middleware to grab the token
Provide middleware to grab the user Id
Provide middleware that will pull the full user record from the DB
Provide JWTRequired middleware that will kill a request with no JWT

You could go one step further and support OpenID Connect tokens.

Good suggestion.  Have you set this up in Node before?


npx electron-forge import errors

Pre-flight checklist

[X] I have read the contribution documentation for this project.
[X] I agree to follow the code of conduct that this project uses.
[X] I have searched the issue tracker for a bug that matches the one I want to file, without success.

Electron Forge version
6.2.1
Electron version
25.3.2
Operating system
win 10
Last known working Electron Forge version
No response
Expected behavior
PS G:\repo\test\test-electron-native> npx electron-forge import
✔ Checking your system
✔ Locating importable project
❯ Processing configuration and dependencies
  ✖ Installing dependencies
    › Failed to install modules: ["electron-squirrel-startup"]

    With output: Command failed with a non-zero return code (1):
    yarn add electron-squirrel-startup
    yarn add v1.22.19
    i…
  ◼ Copying base template Forge configuration
  ◼ Fixing .gitignore
◼ Finalizing import

An unhandled rejection has occurred inside Forge:
Error: Failed to install modules: ["electron-squirrel-startup"]

With output: Command failed with a non-zero return code (1):
yarn add electron-squirrel-startup
yarn add v1.22.19
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

error G:\repo\test\test-electron-native\node_modules\electron: Command failed.
Exit code: 1
Command: node install.js
Arguments:
Directory: G:\repo\test\test-electron-native\node_modules\electron
Output:
RequestError: connect ETIMEDOUT <IP_ADDRESS>:443
    at ClientRequest.<anonymous> (G:\repo\test\test-electron-native\node_modules\got\dist\source\core\index.js:970:111)
    at Object.onceWrapper (node:events:626:26)
    at ClientRequest.emit (node:events:523:35)
    at origin.emit (G:\repo\test\test-electron-native\node_modules\@szmarczak\http-timer\dist\source\index.js:43:20)
    at TLSSocket.socketErrorListener (node:_http_client:495:9)
    at TLSSocket.emit (node:events:511:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1574:16)
error G:\repo\test\test-electron-native\node_modules\electron: Command failed.
Exit code: 1
Command: node install.js
Arguments:
Directory: G:\repo\test\test-electron-native\node_modules\electron
Output:
RequestError: connect ETIMEDOUT <IP_ADDRESS>:443
    at ClientRequest.<anonymous> (G:\repo\test\test-electron-native\node_modules\got\dist\source\core\index.js:970:111)
    at Object.onceWrapper (node:events:626:26)
    at ClientRequest.emit (node:events:523:35)
    at origin.emit (G:\repo\test\test-electron-native\node_modules\@szmarczak\http-timer\dist\source\index.js:43:20)
    at TLSSocket.socketErrorListener (node:_http_client:495:9)
    at TLSSocket.emit (node:events:511:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1574:16)
at exports.default (G:\repo\test\test-electron-native\node_modules\@electron-forge\core\dist\util\install-dependencies.js:52:19)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Task.task (G:\repo\test\test-electron-native\node_modules\@electron-forge\core\dist\api\import.js:168:29)
    at async Task.run (G:\repo\test\test-electron-native\node_modules\listr2\dist\index.cjs:978:11)
    at async G:\repo\test\test-electron-native\node_modules\p-map\index.js:57:22

Actual behavior
.
Steps to reproduce
.
Additional information
No response

Similar issue, access GitHub IP(<IP_ADDRESS>:443) timeout, need set up terminal proxy or adjust host IP.

But what makes me curious is, why does the make phase(npm run make) also require access to GitHub?


Installing plugin breaks Ionic browser production build

After attempting to install the branch-cordova-sdk plugin in my Ionic 3 project, the browser production build breaks and returns the console error: "TypeError: window.clientInformation is undefined"
Steps to reproduce:

Add plugin directive and branch configuration in config.xml
re-compile browser app with --prod switch ionic cordova build browser --prod
Bootstrap browser app (In this case, with a docker container)

I have published the broken version of the app with the Branch plugin installed to the following address:
https://branch-debug.azurewebsites.net/
Compare that to our production dashboard, which does not have the plugin installed:
https://dashboard.boostup.com
After bringing this issue up on Twitter, I was told by support account to submit this ticket. Thanks for you help!

@djmeph we're able to see the  error on Firefox.  window .client information is not supported on Firefox, that's why it's returning undefined. We are working on a fix and will be release in 2-3 days

Yes, I'm using Firefox. Understandable why this was overlooked. Thanks for looking into it, sounds like the fix will be ready just in time for our next sprint!

@djmeph We have fixed this issue. Please check.
We are closing it, please re-open if you are facing any issue.


Stateless Validation Improvement Proposal

Stateless Validation Improvement Proposal
Currently, stateless validation is incomplete and unnecessarily complex, following design for stateless validation is proposed, which aims to simplify the interface and add consistency:

Remove FieldValidation class - all its members become free functions

Add validation function for all classes.

For an object which expresses polymorphic behavior (e.g command or query), implement validator class and use it inside validate function.

FieldValidator Before:
class FieldValidator {
     public:
      FieldValidator(time_t future_gap = default_future_gap);

      void validateAccountId(
          ReasonsGroupType &reason,
          const interface::types::AccountIdType &account_id) const;

      void validateAssetId(ReasonsGroupType &reason,
                           const interface::types::AssetIdType &asset_id) const;

...
}

After
Error validateAccountId(const interface::types::AccountIdType &account_id);

Error validateAssetId(const interface::types::AssetIdType &asset_id);

...

Validation of Model Classes
Error validate(const interface::interface::Peer &peer);

Error validate(const interface::interface::Account &account);

Error validate(const interface::interface::Amount &amount);

About Passing Validator via Template Argument
Fieldvalidator was designed as a class, so it would be easy to pass it as template argument. This allows mocking in tests, to bypass validation. I propose to explicitly remove that ability, by getting rid of the class. Justification is that stateless validation represents invariant of every object in the model. Since all objects are immutable, we may assume that after their creation, invariant stays true through entire object's lifetime.
This property of objects means that generally, every component of Iroha may assume the correct state of every model object it operates on. This allows not to check for stateless validity in every part of Iroha, which improves performance and keeps components simpler. This also means that object does not have to correctly handle invalid objects. However, when we introduce the ability to replace field validator, we allow the creation of invalid objects.
One place where this might be used are tests - we may wish to skip validation to make code shorter. However, this represents contradiction with the statement in the previous paragraph - by bypassing validation in tests we expect components to react correctly given incorrect data, which is wrong. That is why I propose getting rid of that ability and require tests to always instantiate correct objects. By removing the ability to pass any validator to builders, we enforce the correctness of invariants.

However, when we introduce the ability to replace field validator, we allow the creation of invalid objects.
It is a requirement

Can you provide an example of such test?

About free functions for stateless validation.
I'm not sure that this approach suitable for stateless validation cause it leads to redundant complexity. For example, we want to build up stateless validation for the transaction. On the client side we need to check the schema of the transaction - boundary values for commands, a schema of the accounts an so on. But on the Iroha side, we need to validate schema and signatures.
With free function approach, we will write combine by our self. But in fact, it is just a combination of validators.
About template arguments.
In terms of the design shared model objects are same dependency as others. Thus, we require mocks shared model object for testing purposes. And in this case, it very convenient way to use an explicit template parameter for testing purposes.
But maybe we need to come up with the improvement that able to handle calls unregistered in the builder and throw the exception.
Also, I can not understand from the report why composable way is not applied in the stateless validation. And what about auto checking via getters?

I'm not sure that this approach suitable for stateless validation cause it leads to redundant complexity. For example, we want to build up stateless validation for the transaction. On the client side we need to check the schema of the transaction - boundary values for commands, a schema of the accounts an so on. But on the Iroha side, we need to validate schema and signatures.
With free function approach, we will write combine by our self. But in fact, it is just a combination of validators.

I do not understand what do you mean by redundant complexity? We cannot trust the client to send correct data, so we every time we accept a new transaction, we need to validate everything. With free functions, this will be as easy as calling validate(transaction)

In terms of the design shared model objects are the same dependency as others. Thus, we require mocks shared model object for testing purposes. And in this case, it very convenient way to use an explicit template parameter for testing purposes.

Can you please provide an example where we need to mock object with invalid data? I assume that we expect all components of Iroha to work only with correct values (that's why we do not perform stateless validation on each step of the pipeline)

redundant complexity
I mean there is need to write different functions of the combine by yourself.

we need to validate everything
Sure u are totally correct. But this issue unrelated to my ideas.

Can you please provide an example where we need to mock object with invalid data?
Just shallow search:

https://github.com/hyperledger/iroha/blob/def7bc4f7efdf0c2d1c3caecccd2cf3efe0c889e/test/module/irohad/ordering/ordering_service_test.cpp#L121
https://github.com/hyperledger/iroha/blob/def7bc4f7efdf0c2d1c3caecccd2cf3efe0c889e/test/module/irohad/consensus/yac/peer_orderer_test.cpp#L58
https://github.com/hyperledger/iroha/blob/def7bc4f7efdf0c2d1c3caecccd2cf3efe0c889e/test/module/irohad/ametsuchi/ametsuchi_test.cpp#L185

But in fact, there are a lot of usages of mock objects in tests. And this is the convenient and correct approach.

Just shllow search

That solved via Test*Builder as in your example, there's no usage of FieldValidator here

Updated proposal to include features for builders. Features for validators are WIP and will be added later

Builder prototype is at #1306


Extend ecological analysis / include bounded rationality

To make roundwise and summary comparisons comparable, look at sample size as a common metric and measure of effort.


Allow calling classes to change properties on the Label

Super simple and small change to allow anybody using the framework to be able to customize the label.

👍🏼Looks good. I won’t be able to push the pod update for a while though so you’ll have to set a manual target for this commit/branch.
Cheers! 🍻


Initial work to support Cross Workspace Dependencies (would fix #4)

A Breadth First Search finds all path dependencies & adds any necessary workspace manifests.

Relies on "manifest.package.workspace" to traverse through to workspace manifests

Still rough in places, some polishing to come, however this has successfully run against a simple example!

*Issue #, if available:
https://github.com/LukeMathWalker/cargo-chef/issues/4
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Let me know when it's a good time for me to have a look!

Let me know when it's a good time for me to have a look!

Ready for a look now. The recent addition of "cargo manifest" simplified what was necessary here 👍

I'm a bit swamped this week, but I'll try to have a look!

gone stale, I'll bring it back later


[docs] fix docstring of scaler application mentioned in #136

The docstring for project is wrong. It should say that the projection is applied before the scaling.

I have forked and corrected this and submitted a pull request.

Thank you!


[Event Hubs Client] Ttrack Two: Third Preview (AMQP Foundation)

Summary
The intent of these changes is to continue building out the AMQP foundation, focused on connections, common messages, and management operations.
Goals

Handle processing and transformation of data for error scenarios and management operations between the client and service
Allow for creation of an AMQP connection, based on the options provided to the EventHubClient
Enable management operations by providing the needed infrastructure for them
Create an AMQP transport EventHubClient that makes use of the track two infrastructure

Last Upstream Rebase
Thursday, August 29, 2019 5:37pm (EDT)
Related and Follow-Up Issues

[Epic] Release Event Hubs Track 2 Library Preview 3 for .Net (#7141)
AMQP Foundation (Connection, Session, Common Infrastructure) (#7187)
AMQP Foundation (Links) (#7188 )
AmqpEventHubClient (#7190)

//cc: @chrisjbarr


Fix DropdownMenu does not rematch initialSelection when entries have changed

Description
This PR makes DropdownMenu rematching the initialSelection when the entries are updated.
If the new entries contains one entry whose value matches initialSelection this entry's label is used to initialize the inner text field, if no entries matches initialSelection the text field is emptied.
Related Issue
Fixes DropdownMenu.didUpdateWidget should re-match initialSelection when dropdownMenuEntries have changed.
Tests
Adds 3 tests.

I will probably wait for https://github.com/flutter/flutter/pull/155252 to land (I will solve the conflicts on my side).


Invoke HandleSettings(o, SettingsAction.Saving) on plugin settings window close

Currently, saving is only called when the script execution is ended. This is a bit confusing, could you please add a save every time the settings window is closed?

Yeah, I'm using this. Gui is rendered correctly. I'm talking about cases when settings are edited without starting plugin (before starting or after stopping). Settings are visually updated, but they are not saved to disk:

Open the settings
Change something
Close settings
Close the player

In this case nothing will be saved to disk (but you can open the settings window as many times as you like while app is running). To save it, you need to start and stop the plugin before closing the player.
If this is the way it's designed, okay. I'll just add a note to the plugin instructions to start and stop it for save settings

Hmm yea looking at it now it does indeed work very weirdly.
It looks like you can only change settings after starting the plugin, otherwise they get overwritten from disk.
I'll change this to make more sense, thanks for bringing this up.


Refactor/benchmarking visualizer

Summary
Implements a new script, benchmark/benchmarks_visualizer.py, that substitues the functionality provided by current benchmark/benchmarks_visualizer.ipynb. Resolves #211 .
Details
$ python3 benchmarks_visualizer.py --help
usage: benchmarks_visualizer.py [-h] --kernel-name KERNEL_NAME --metric-name METRIC_NAME --kernel-operation-mode KERNEL_OPERATION_MODE [--display] [--overwrite]

options:
  -h, --help            show this help message and exit
  --kernel-name KERNEL_NAME
                        Kernel name to benchmark
  --metric-name METRIC_NAME
                        Metric name to visualize (speed/memory)
  --kernel-operation-mode KERNEL_OPERATION_MODE
                        Kernel operation mode to visualize (forward/backward/full)
  --display             Display the visualization
  --overwrite           Overwrite existing visualization, if none exist this flag has no effect as one are always created

Testing Done

Hardware Type:
[ ] run make test to ensure correctness
[ ] run make checkstyle to ensure code style
[ ] run make test-convergence to ensure convergence

cc @ByronHsu, here's the draft that I thought of, feel free to say any notes, if so, will properly document/redo it tommorow.

lgtm

Okay, will cleanup the code, add comments, resp. adjust CONTRIBUTING.md and should be marked as ready.

@ByronHsu should be ready to merge, did docstrings and edited contributing guidelines to reflect the new version.


Using together CITEXT and LIKE problem

Spring Boot 3.3.3 (hibernate 6.5.2). PostgreSQL 14.2, hypersistence-utils 3.8.2.
SELECT e
FROM SomeEntity AS e
WHERE s.textField LIKE :search

@Entity
@Table(name = "table_name")
// ...
SomeEntity {

   @Type(PostgreSQLCITextType.class)
   @Column(name = "text_field", columnDefinition = "CITEXT")
   private String textField;

   // ...
}

The exception is thrown from here:

the cause is that PostgreSQLCITextType returns SlqTypes.OTHER which type returns .isStringLike() = false.
The same code was working before migration from Spring 2.7.18.
What can we do to use LIKE with CITEXT columns?
Thanks.

PostgreSQLCITextType should use something like Types.VARCHAR instead of Types.OBJECT.

Fixed.


[question] [Sveltekit] How to validate on submit?

Hello, Great package btw,
The behavior I'm trying to achieve is to show the validation errors after the user submit the form, the default behavior is validating on keydown as soon as the input is touched.
Here is the solution that i tried:

{#each Object.entries($errors) as [label, message]}
		{#if message}

Error: {label} is invalid

{message}

		{/if}
{/each}

<form use:form>
        /.../
           </form>

I hope this is not a duplicate, Thanks in advance.

@pablo-abc This feature is important to prevent this behavior:
https://github.com/pablo-abc/felte/assets/6722075/c19e22f7-f5d5-4187-9b71-cf5a0c6aa687

This would be very useful. Is there a way to implement it? @m0nm @stefanosandes have you found the solution?

Hello, useForm has the mode prop which does this, maybe it can be added here to.
https://react-hook-form.com/docs/useform#mode

Love it, a big plus from myself:
I think this is related:
https://github.com/pablo-abc/felte/discussions/129
https://github.com/pablo-abc/felte/discussions/129
https://github.com/pablo-abc/felte/issues/289


build(deps): bump github.com/cockroachdb/pebble from v0.0.0-20231114155657-6682fd5e8763 to v1.1.0

Current dependencies on/for this PR:

main

PR #705   👈

This stack of pull requests is managed by Graphite.


Should we remove "No Data" if there is no grey on the map?

how difficult is this change? i would make it low priority.

closing... seems like not-needed and would clog up the code a bit


Radar: Initial record selection

When viewing the radar visualisation on the review page, there is often a lot of data (potentially around 52 series). This is very noisy when people visit it.
To reduce this, initially when the page is viewed, if there are more than 3 records, only 3 records will be shown:

the first ever record
the most recent record
the second most recent record

This gives the user a sense of progression since the start of their intervention and recent progression. Users should then be able to toggle any of the records to add or remove from the radar like currently.
(this has been requested from a user)

Tested that a hidden attribute against a dataset will make the series inactive when the chart is shown. This can be used to achieve this objective without rewriting the legend. More details at https://github.com/chartjs/Chart.js/issues/689.


index.ejs ---

There are no ejs-instructions in index.ejs
I suppose you wanted either the sign-up part or the login-part ...
However twitter provides the login-screen for you.

@MatthiasLiszt  Thanks! The use of ejs was only for testing basic stuff in the backend. I will remove it when the frontend is finished ;)


Questions about Form Validation and Issue with "clear button" ...

ember.js @ 1.13.1
semantic-ui-ember @ 0.0.1-rc.6
I have the following form code:

    {{t signUp.header}}

  <form class="ui form">

      {{input id="username" name="username" type="text" placeholder=usernamePlaceholder}}

      {{input name="email" type="text" placeholder=emailPlaceholder}}

      {{input name="password" type="password" placeholder=passwordPlaceholder}}

Submit

Clear

  </form>

However, the clear button is not working, as per the Semantic UI Form Validation examples found here.
Also, I have no idea where I would place the actual validation set-up code, like the following:
$('.sign-up form').form({
  fields: {
    name: {
      identifer: 'username',
      rules: [
        {
          type: 'empty',
          prompt: "You must provide a user name!"
        }
      ]
    }
  },
  inline: true,
  on: 'blur'
});

Note, if I paste the above into the Chrome console, the validation is not working, still, but somehow the clear button starts to work!
Any help with this would be greatly appreciated...

Hi @Panoplos , I haven't actually used semantic validations before. The main reason is it breaks the ember models for handling data and bindings. We use in our own projects, https://github.com/dockyard/ember-validations. The better way would be to have an action on clear that then clears your models data through ember.

Clear

Then in the component or controller something like
actions:
  clear: ->
     @setProperties({
         email: null,
         password: null
     })

OK, I was going to ask what the "best practice" with this was... I like SUI's approach to this, as it is very simple to get the error messages to auto-display.

It is easy, but it breaks the approach on everything being data bound in ember. Data down actions up, if you use semantic validations, you have to then tie into the validations and update the data based on semantics events. For example, when semantic clears the inputs, ember doesn't know they cleared, and so your data doesn't represent the dom, causing a disconnect. Which is why i'm assuming you're seeing the problem.


Hardware Donation

To support more device, we need more Hardware. I live in Switzerland and our prices and duties (especially import) are high.
If you have a device which you don't need anymore and will send us or you want donate a small amount for a device, that would be amazing. Feel free to extend this list of hardware.
You can send donation to my paypal account and add a description with the name of you favorite device.
Hardware list

ASUS Tinker Board: 70$ - 100%
Pine64: 30$ - 0%
Rock64: 50$ - 100%
Raspberry Pi 3+: 50$ - 100%
Intel nuc: 130$ - 80%
Orange Pi PC 2: 28$ - 100%
Orange Pi Zero: 18$ - 100%
Orange Pi Zero 2: 28$ - 100%
Odroid C2: 70$ - 0%
ODROID-HC2: 75$ - 0%
Odroid XU4: 85$ - 100%

Paypal<EMAIL_ADDRESS>/ http://paypal.me/pvizeli
Patreon: https://www.patreon.com/pvizeli
For post address, send me a PM on discord.

Any chance to add some Orange Pi models as well?

What kind of OrangePi make sense?

Probably Orange Pi Zero and Orange Pi PC 2. One is a H3 and one is H5. I have the Orange Pi PC 2 but don't know what is currently most popular, as most custom builds used Orange Pi Zero

You should have a Patreon account!

I would support a homeassistsnt patreon account tbh

You can add a donate button on the home page, and anyone can send you optional 5, 10, 15, 20 ... until you can purchase all the hardware you can simple close, or just let it there. I will donate 18$ for Orange Pi Zero

If anyone wants to Donate using Revolut, you can ping me and then I can proxy them to pvizeli as well.

patreon account is in progress

Might be far fetched but have you considered one of these:
https://getchip.com/pages/chippro#undefined4

https://www.patreon.com/pvizeli

I’ve Patreoned $5/mnth and will let it roll for 12 months at least so use that as you choose.

I patreon $10 a month, please continue your hard Dev work ❤
I have run into a Hass.io but with USB serial devices now :( I'm hoping
it's fixed in a future version
On Thu, 21 Jun. 2018, 7:49 am Adrian Rudman<EMAIL_ADDRESS>wrote:

I’ve Patreoned $5/mnth and will let it roll for 12 months at least so use
that as you choose.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/hassos/issues/33#issuecomment-398908730,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF_Q1FU-_VjJxZvmMAg7hdX3NQrLaqTIks5t-sNPgaJpZM4UtSuy
.

@CountParadox make a PR. I run devices over GPIO and usb/serial without problems...

@pvizeli Will you need testing? I own a Rock64 and can test if needed :)

@olskar I order now a rock64. I need no tester ;) We need porting the bootloader to our system...

@pvizeli: would one of these help with serial debugging: http://www.ni.com/hu-hu/shop/engineering-education/portable-student-devices/myrio-student-embedded-device/what-is-myrio.html ?
It has an FPGA that could read serial transmission in real time and you could process that on your PC.
Let me know

Donated 68 dollaroos to the NUC
Will add to next month if i can as well, thanks for all the hard work.

@pvizeli  dontated 40CHF for the intel nuc via paypal!

Odroid HC2 runs the exact same software as the XU4, so if it runs on XU4 it will run on HC2 as well. I have both so I can test them if needed.

@mad-ady they have also a SD slot for OS?

XU4 supports both SD or eMMC (has a selector switch). HC1/HC2 (and MC1) have only SD slot (and HC1/HC2 have SATA for a hard drive). Note that it still needs the SD card to boot (boodloader can't be on SATA), but rootfs can be moved to disk if needed. Not sure if uboot can read kernel/initrd/dtb from SATA - all the examples I've seen do it from the SD and after kernel boots it can mount the rootfs from SATA.

Got paid...just paid 26 Euro for the NUC hopefully that's 100% now
thanks

Sent CHF 50 your way. Use it for whatever you need besides just boards (SD cards, ethernet cables, power adapters).

@pvizeli do you need anything extra to help with automation of deployments/testing?

@pvizeli I test hassos ver 1.7, it is same with ver 1.5, no data transfer.

BeagleBone Black is the board often use by professional,with fast emmc flash, any change you will make hassos work with it?

@dzungpv if you start some donation for it probably will get added to the list so others can help support it.


Added tolerations support for dcgmexporter and neuronmonitor.

Description of changes:
In order to support tolerations for https://github.com/aws-observability/helm-charts/pull/41, I need to update these files in the operator.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

If someone is still using the old CRDs but run with the new operator after these changes, would it start to fail?


Adding SqlKata

Database/SqlKata - SqlKata
SqlKata - Elegant Sql Query Builder, that supports complex queries, joins, sub queries, nested where conditions, vendor engine targets and more

I think that ORM section will be a better fit for the framework. Databases section contains databases and core frameworks to work with databases but SqlKata is a query builder which works on top of standard Sql stack.

I think this project is awesome because

Nice site
Nice documentation
Not that many query builders I know of written for dotnet

My suggestion would be a new category under DB - Database query builders. The reason for this suggestion is that, as @zihotki states, it's not really a great fit for Databases. But, I think the same can be said for ORMs.
If we add this category, we should move another query builders listed.
Thoughts?

Agree with @pleb, a new category for query builders would be more appropriate, since now it cannot be considered as ORM

@ahmad-moussawi can you update the PR pls. I'll merge when placed under new cat

@pleb, updated thanks.


Enabled LibSSH's WITH_SERVER flag

Fixes issue #18.
Quoting myself:

When using a statically built version of libssh with CMake it worked just fine, after a lot of digging and comparing, I've found that this issue shows up when building libssh with the flag WITH_SERVER disabled/off (Enabled by default when building with CMake). After enabling it and adding some modifications to the files list, it worked perfectly (tested on ArchLinux and Windows).

The GLOBAL_BIND_CONFIG flag value ("/etc/ssh/libssh_server_config") was copied from CMake default config, as it was required for the WITH_SERVER flag. Also note that bind_config.c wasn't necessary when building on Linux but it was on Windows.

Thanks for digging in. This issue is weird! My theory is that the ssh_message_reply_default implementation that gets compiled in WITH_SERVER makes the difference here; most of the rest of the code in the added files seems like it wouldn't have an impact on anything.

Not really sure, unfortunately I'm not familiar with libssh but seems possible. Shouldn't the server methods be available in case someone wants to implement SSH from the server side?
The linting has failed so I've pushed one more change to fix it.


When I clear one selection on a multi-select with allowClear set to true, all selections are cleared

Here's an example fiddle :
http://jsfiddle.net/Intrepidd/ytL9s97k/
Try to add several results to the multiple select then remove only one, it will remove everything, and also the clear button appears.
Here's a gif demonstrating the issue :

I understand you should not use allowClear with a multiple select but in some cases you just want to apply select2 to all selects.
A quick fix would be to call select2 two times with the following selectors :
$('select[multiple]').select2({width: '100%'});
$('select:not([multiple])').select2({allowClear: true, width: '100%'});

but this is messy.
IMHO allowClear should be ignored if the select is multiple
thoughts ?

This is definitely a duplicate, but part of the issue is that you are missing placeholder, which is required for allowClear. I think we trigger a warning about that when you have debug: true set.
Until I hunt down the ticket, this one will stay open.

Whilst it may be the current requirement, I don't get why "placeholder" is a requirement for this behaviour, they do not seem related at all.

It's a requirement for single selects, and allowClear was designed with a single select in mind. For a single select, we need to reset it to a specific value instead of just clearing all selections.
In theory, this line could be conditional (default to null if this.placeholder isn't there) which would remove the requirement for multiple selects. But then there would be a configuration difference between single and multiple selects, which is something we are trying to avoid.

This is a duplicate of #3335.  Since @kevin-brown offers some useful insight, I will repost his comments in #3335.


Support for IB live?

Hello,
I just installed zipline-trader in python 3.6 env. I see ZT has alpaca api but nothing for IB. Your doc hints to support IB live trading. Is this true or just a plan?
Sincerely,
fimmu

I downloaded a zip file from the repository and unzipped it in my download folder when I run the pip install -e . command. After a while, it said zipline-trader was installed sucessfully. However, zipline and a few others were still in the download folder with an egg.link poined from the site-package folder in my env. Did I do something wrong? Any suggestion for installation for Windows?
As for the IB question I posted above, I did see a IB test script in the test folder.

Hi.
A Broker is used for 2 things:

Get data for ingestion
Trading

For Trading there is an implementation for both Alapca and IB
For data, we only use the FREE data source from Alpaca

For installation follow one of the options here: https://zipline-trader.readthedocs.io/en/latest/index.html#

Hi, Shlomi:
Thanks for the help. I now have the trader inside site-package folder and zipline inside the trader folder. Is this expected?
Best regards
Sent from my iPhone

On Nov 18, 2020, at 07:23, Shlomi Kushchi<EMAIL_ADDRESS>wrote:

For installation follow one of the options here: https://zipline-trader.readthedocs.io/en/latest/index.html#
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

yes, that is expected

Hi, Shlomi:
I am trying to setup the postgres backend to run the scripts you gave in the doc and having connection issue. Would you mind to point me to a good place where I can find support to set up the backend correctly?
Thank you very much for your help in my process of moving from zipline to ZT.
Happy holiday!
Sean
Sent from my iPhone

On Nov 20, 2020, at 20:44, Shuang @.***> wrote:
Hi, Shlomi:
Thanks for the help. I now have the trader inside site-package folder and zipline inside the trader folder. Is this expected?
Best regards
Sent from my iPhone

On Nov 18, 2020, at 07:23, Shlomi Kushchi @.***> wrote:

For installation follow one of the options here: https://zipline-trader.readthedocs.io/en/latest/index.html#
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

"I just installed zipline-trader in python 3.6 env. I see ZT has alpaca api but nothing for IB. Your doc hints to support IB live trading. Is this true or just a plan?"

Still i don't see that hint in the test folder


App in Loop

Hey @clucs123,
I've found your app through @katiedavis  profile and decided to give it a go as I've been trying for hours to deploy a React Shopify App on Heroku.
Your code explain a bunch of things for me (quite rookie on Shopify here), so thank you so much.
I just have one little question to ask. I installed it successfully on my shopify store, but it seems to be in loop and I cant find the reason for it. (It's literally your app with my .env keys)
When I try to run it for the first time, the app redirects to my store and from my store to the app and so on..
Steps I did:

Cloned your repo
Created a .env file
Run yarn build
Submitted it to Heroku (via heroku cli)
Got the https://desolate-dusk-53030.herokuapp.com/ as a result
Accessed the app
Redirected to my shopify store
Shopify store redirected to my app
Which then redirected back to my store
.... and so on

So the question is, do you know what could potentially be going on here?
Thank you in advance.
:)

Hey Francisco,
The first thing I would do is check the "Config Vars" in Heroku match your
.env file? You'll need to change the *HOST *variable to match your Heroku
URL (https://desolate-dusk-53030.herokuapp.com/) instead of localhost.
Once the app is on Heroku your .env file is redundant as it's not uploaded
to Heroku when you submit. You can add the Heroku "Config Vars" in your app
Settings.
Hope this helps.
If you've already tried this let me know and I'll have another look.
Paul Clucas
On Sat, 7 Mar 2020 at 13:41, Francisco Ruaro Varisco <
<EMAIL_ADDRESS>wrote:

Hey @clucs123 https://github.com/clucs123,
I've found your app through @katiedavis https://github.com/katiedavis
profile and decided to give it a go as I've been trying for hours to deploy
a React Shopify App on Heroku.
Your code explain a bunch of things for me (quite rookie on Shopify here),
so thank you so much.
I just have one little question to ask. I installed it successfully on my
shopify store, but it seems to be in loop and I cant find the reason for
it. (It's literally your app with my .env keys)
When I try to run it for the first time, the app redirects to my store and
from my store to the app and so on..
Steps I did:

Cloned your repo
Created a .env file
Run yarn build
Submitted it to Heroku (via heroku cli)
Got the https://desolate-dusk-53030.herokuapp.com/ as a result
Accessed the app
Redirected to my shopify store
Shopify store redirected to my app
Which then redirected back to my store
.... and so on

So the question is, do you know what could potentially be going on here?
Thank you in advance.
:)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/clucs123/shopify-react-test-v2/issues/1?email_source=notifications&email_token=ADD7MI32PH2EKI5BCSFIOSLRGJFJZA5CNFSM4LDPYSPKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4ITJOS3Q,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADD7MI6FTQAD2GEYU6VHRTDRGJFJZANCNFSM4LDPYSPA
.

Hey @clucs123
Thanks for your prompt answer.
I’ve tried that and it doesn’t seem to have resolved the problem.
These are my heroku config vars:

@xicovarisco for what it's worth, I never condigured the HOST in my local .env var or in the Heroku env vars, and my app worked fine on Heroku.
Note that https://github.com/clucs123/shopify-react-test-v2/blob/d00cb50806241fa278fef93a1665e304653319e3/server/server.js#L19, which is where the environment variables are being extracted from the environment and pulled into the app, makes no mention of HOST.
If that would solve the problem that would be hella interesting.
if you end up getting really stuck ping me back here and I'll try to repro on a fresh dyno, see what gives.

Hey @tomgs, about the HOST variable.. that's what I thought. :) Thanks for clarifying.
I tried running it again and it didn't work :( Still stuck on the redirect problem.
I'm starting to think that it's a problem with Shopify itself.
Would you be able to give it a go and try to run on a fresh dyno?
Cheers

This repo was just a barebones project I did for Shopify support to highlight an issue I was having at the time. I can't find the local copy of this repo so I can't check the .env vars I used. I usually use a HOST variable for my Shopify apps for GraphQl etc but it seems not in this project.
Have you run "heroku logs --tail" in the CLI while the app is authenticating? Any console.logs etc you have will appear in the logs and also any exceptions.

Good to know @clucs123. Didn't know about that.

Thanks

As you can get the app to work locally then versioning probably isn't the problem but I've noticed that this barebones project has some dependencies that are out of date. Below are the dependencies used on one of my published apps. Polaris and apollo-boost are newer versions
"dependencies": {     "@apollo/react-hooks": "^3.1.3",     "@shopify/app-bridge": "^1.16.0",     "@shopify/app-bridge-react": "^1.16.0",     "@shopify/koa-shopify-auth": "^3.1.51",     "@shopify/koa-shopify-graphql-proxy": "^3.3.0",     "@shopify/koa-shopify-webhooks": "^2.2.2",     "@shopify/polaris": "^4.10.2",     "@zeit/next-css": "^1.0.1",     "apollo-boost": "^0.4.7",     "apollo-cache-inmemory": "^1.6.5",     "apollo-link-http": "^1.5.16",     "bull": "^3.12.1",     "copy-to-clipboard": "^3.2.0",     "core-js": "^3.6.1",     "dotenv": "^8.2.0",     "foreman": "^3.0.1",     "gmail-send": "^1.8.10",     "graphql": "^14.6.0",     "highlight.js": "^9.17.1",     "ioredis": "^4.14.1",     "isomorphic-fetch": "^2.2.1",     "js-cookie": "^2.2.1",     "koa": "^2.11.0",     "koa-body": "^4.1.1",     "koa-router": "^7.4.0",     "koa-session": "^5.12.3",     "mailchimp-api-v3": "^1.13.1",     "next": "^9.1.7",     "next-routes": "^1.4.2",     "node-fetch": "^2.6.0",     "papaparse": "^5.1.1",     "pg": "^7.17.0",     "prop-types": "^15.7.2",     "react": "^16.12.0",     "react-apollo": "^3.1.3",     "react-color": "^2.18.0",     "react-csv-reader": "^2.0.2",     "react-dom": "^16.12.0",     "store-js": "^2.0.4",     "throng": "^4.0.0"   },   "devDependencies": {     "babel-eslint": "^10.0.3",     "eslint": "^6.8.0",     "eslint-plugin-react": "^7.17.0",     "eslint-plugin-react-hooks": "^2.3.0",     "koa-webpack": "^5.3.0",     "webpack-dev-middleware": "^3.7.2"   }

I know it's obvious but have you changed the app settings in Shopify, ie the App Url and Callback URL from your ngrok to the Heroku URL?

Unfortunately, this is the only project I can share at the moment. All the rest are published apps.

I know it's obvious but have you changed the app settings in Shopify, ie the App Url and Callback URL from your ngrok to the Heroku URL?

Yeah, I did.

As you can get the app to work locally then versioning probably isn't the problem but I've noticed that this barebones project has some dependencies that are out of date. Below are the dependencies used on one of my published apps. Polaris and apollo-boost are newer versions
"dependencies": { "@apollo/react-hooks": "^3.1.3", "@shopify/app-bridge": "^1.16.0", "@shopify/app-bridge-react": "^1.16.0", "@shopify/koa-shopify-auth": "^3.1.51", "@shopify/koa-shopify-graphql-proxy": "^3.3.0", "@shopify/koa-shopify-webhooks": "^2.2.2", "@shopify/polaris": "^4.10.2", "@zeit/next-css": "^1.0.1", "apollo-boost": "^0.4.7", "apollo-cache-inmemory": "^1.6.5", "apollo-link-http": "^1.5.16", "bull": "^3.12.1", "copy-to-clipboard": "^3.2.0", "core-js": "^3.6.1", "dotenv": "^8.2.0", "foreman": "^3.0.1", "gmail-send": "^1.8.10", "graphql": "^14.6.0", "highlight.js": "^9.17.1", "ioredis": "^4.14.1", "isomorphic-fetch": "^2.2.1", "js-cookie": "^2.2.1", "koa": "^2.11.0", "koa-body": "^4.1.1", "koa-router": "^7.4.0", "koa-session": "^5.12.3", "mailchimp-api-v3": "^1.13.1", "next": "^9.1.7", "next-routes": "^1.4.2", "node-fetch": "^2.6.0", "papaparse": "^5.1.1", "pg": "^7.17.0", "prop-types": "^15.7.2", "react": "^16.12.0", "react-apollo": "^3.1.3", "react-color": "^2.18.0", "react-csv-reader": "^2.0.2", "react-dom": "^16.12.0", "store-js": "^2.0.4", "throng": "^4.0.0" }, "devDependencies": { "babel-eslint": "^10.0.3", "eslint": "^6.8.0", "eslint-plugin-react": "^7.17.0", "eslint-plugin-react-hooks": "^2.3.0", "koa-webpack": "^5.3.0", "webpack-dev-middleware": "^3.7.2" }

I'll try to install these packages to see what happens

Btw.. What commands do you use to 'start' and 'build' your project?
Either locally and on Heroku..

"npm run dev" and "npm run build" locally.
Heroku builds and restarts your app when you push to the git master.
Btw, you don't need to install all the above packages as some are only relevant to the specific project. I know from experience though that there are issues with Polaris and apollo when the wrong combination of versions are used. I don't think that this is your problem here though as you can get it to work locally.
Did you check your App Url and the Whitelist URL is Shopify is using your Heroku URL?

@xicovarisco repro'ing now.

"npm run dev" and "npm run build" locally.
Heroku builds and restarts your app when you push to the git master.
Btw, you don't need to install all the above packages as some are only relevant to the specific project. I know from experience though that there are issues with Polaris and apollo when the wrong combination of versions are used. I don't think that this is your problem here though as you can get it to work locally.
Did you check your App Url and the Whitelist URL is Shopify is using your Heroku URL?

Yeah man, I checked.
Check it out my screenshot:

Ah, interesting, first load of store after install crashed my tab. Console seems pissed at shopOrigin being missing:

So what happens after the authentication flow is complete is:
https://github.com/clucs123/shopify-react-test-v2/blob/master/server/server.js#L35
Meaning it redirects to its own root. If I'm not mistaken, this is the part where I'd expect it throws you back into the store's admin panel, i.e. the app is "locked into" an iFrame.
Let me try to unbrick the tab and see what gives.

But, assuming that the user hasn't left you in this state, and for some bizarre reason attempted to try and use the app from the admin panel (i.e. inside his store) - it does not redirect:

So, in other words, can't repro. Note, by the way, that now the console is angry at the apiKey being missing, and not the shopOrigin.
I'd say, if this is indeed the default output of the shopify-app-cli (which I did not find to be very helpful for my workflow, since it has some nasty bugs), then a bug report is due.
Let's try and figure it out step by step though - I'll compare my working app with this to see where the different lies (I based mine a few months ago on https://shopify.dev/tutorials/build-a-shopify-app-with-node-and-react).

@tomgs  I've experienced a similar problem in the past with retrieving the ShopOrigin and it was the ApolloClient that was the issue. Updating the versions of app-bridge, app-bridge-react and react-apollo sorted it out. I've checked this repo's dependencies and they are older than my current live projects.

This is my Heroku config BTW:

Let me just jot down for a second here some obvious differences from comparing the two pieces of boilerplate code in server/server.js. Below, tut is from the tutorial I mentioned above and cli is from the skeleton shopify-app-cli creates. The order is roughly the same as it appears in the file:

If no port is provided to the app via an environment variable, tut spins up on 3000 and cli spins up on 8081.
The koa-session middleware is provided with secure and sameSite cookie attributes to deal with a recent Chrome update in tut but not in cli.
afterAuth is declared async in cli but not in tut.

That seems to be about it. Also, I literally just saw @clucs123's comment on updating the deps, so I'll do that as well and be back in a blast.

Ah, so app-bridge-react I'm running is actually older than the one in this repo here, and I'm running a later Apollo and a later react-apollo. Let me match those and re-deploy to Heroku.

This is the _app.js file from the project I took above dependencies from. It might help as it's different to the file in this repo. The way to configure the Apollo client is different in more recent versions.
`import App from "next/app";
import Head from "next/head";
import { AppProvider, Frame } from "@shopify/polaris";
import { Provider } from "@shopify/app-bridge-react";
import<EMAIL_ADDRESS>import { ApolloProvider } from "react-apollo";
import React from "react";
import fetch from "node-fetch";
import Cookies from "js-cookie";
import { ApolloClient } from 'apollo-client';
import { HttpLink } from 'apollo-link-http'
import { InMemoryCache } from 'apollo-cache-inmemory';
const link = new HttpLink({
uri: ${Cookies.get("host")}/graphql,
credentials: 'include',
fetch: fetch
});
const client = new ApolloClient({
link,
cache: new InMemoryCache()
});
class MyApp extends App {
render() {
const { Component, pageProps } = this.props;
const config = {
  // eslint-disable-next-line no-undef
  apiKey: API_KEY,
  shopOrigin: Cookies.get("shopOrigin"),
  forceRedirect: true
};

return (
  <React.Fragment>
    <Head>
      <title>APP TITLE GOES HERE</title>
      <meta charSet="utf-8" />
    </Head>
    <Provider config={config}>
      <AppProvider>
        <Frame>
          <ApolloProvider client={client}>
            <Component {...pageProps} />
          </ApolloProvider>
        </Frame>
      </AppProvider>
    </Provider>
  </React.Fragment>
);

}
}
export default MyApp;`

@clucs123 formatting? :)

Ah, so updating the deps gives me a 500 now:
2020-03-08T13:38:09.023801+00:00 heroku[router]: at=info method=GET path="/favicon.ico" host=shopify-react-testing.herokuapp.com request_id=2975d2ce-d691-496a-a54d-a84e59ae918f fwd="<IP_ADDRESS>" dyno=web.1 connect=1ms service=114ms status=302 bytes=296 protocol=https
2020-03-08T13:38:09.222975+00:00 app[web.1]:
2020-03-08T13:38:09.223078+00:00 app[web.1]:   TypeError: option sameSite is invalid
2020-03-08T13:38:09.223079+00:00 app[web.1]:       at new Cookie (/app/node_modules/cookies/index.js:146:11)
2020-03-08T13:38:09.223080+00:00 app[web.1]:       at Cookies.set (/app/node_modules/cookies/index.js:88:16)
2020-03-08T13:38:09.223081+00:00 app[web.1]:       at topLevelOAuthRedirect (/app/node_modules/@shopify/koa-shopify-auth/dist/src/auth/create-top-level-oauth-redirect.js:10:21)
2020-03-08T13:38:09.223081+00:00 app[web.1]:       at /app/node_modules/@shopify/koa-shopify-auth/dist/src/auth/index.js:53:46
2020-03-08T13:38:09.223082+00:00 app[web.1]:       at step (/app/node_modules/tslib/tslib.js:133:27)
2020-03-08T13:38:09.223082+00:00 app[web.1]:       at Object.next (/app/node_modules/tslib/tslib.js:114:57)
2020-03-08T13:38:09.223082+00:00 app[web.1]:       at /app/node_modules/tslib/tslib.js:107:75
2020-03-08T13:38:09.223083+00:00 app[web.1]:       at new Promise (<anonymous>)
2020-03-08T13:38:09.223084+00:00 app[web.1]:       at Object.__awaiter (/app/node_modules/tslib/tslib.js:103:16)
2020-03-08T13:38:09.223084+00:00 app[web.1]:       at shopifyAuth (/app/node_modules/@shopify/koa-shopify-auth/dist/src/auth/index.js:34:24)
2020-03-08T13:38:09.223137+00:00 app[web.1]:

@tomgs have you checked out this page on Shopify regarding the samesite issue.
[https://shopify.dev/tutorials/migrate-your-app-to-support-samesite-cookies]

Thanks for all the tips @clucs123 and @tomgs.
I didn't know we could use the CLI to create new projects, so possibly it's a great start point for me.
Shopify needs to up their game in terms of documentation for developers if they want to have thriving app store, that's for sure.
Will ping you guys here on how it goes

Ok. It's finally working here!! HURRAY 🎉
Honestly, I don't know what's makes the difference between what I have now and I had before.
The fact is, I've started the project differently (Which I wish I knew before). Before I have started my project basing myself on the official react shopify example. Right now I've started the project from the Shopify CLI.
The CLI installed all the dependencies I needed to install to get started (And apparently installed the proper package versions from all the repos).
Steps I did to get that done:

Created the project via Shopify CLI.
Created a new project on Heroku for this new project
Configured the env variables on Heroku pointing to my Shopify Partners App
Changed the whitelisted url and host on my Shopify Partners App
Uninstalled my previous app from my store
Pushed a version of my app to heroku
Installed the app again with my unique link

I'm almost sure you guys know these steps already, but as I'm new to Shopify I wish I had before. :)
But anyway... happy days now :)

@xicovarisco Yes, the CLI is a quick and easy way to get started, I had a play around with it when it was released last year. I'm glad you got it sorted :)

@xicovarisco awesome! Happy you made it happen.
Two points worth mentioning:

The whole npm run dev, npm run start and actually npm run X for every X imaginable are called "Scripts" and are little keywords that are aliases for various commands. They are defined inside pacakage.json and are part of the Node.js + npm ecosystem. Read more about them here: https://docs.npmjs.com/files/package.json#scripts. Specifically, they are editable, and most devs I know either use a bunch of pre-defined ones based on the packages they use (like npm run lint to lint, and npm run test to run a d test suite), and sometimes even write their own if the need arises (like when you want to add a prefix to some command that is not an existing script in your package.json file). The entire Shopify app development process (or, more accurately, the ones they're pushing with the shopify-app-cli) revolves heavily around that ecosystem. Some resources you might find helpful:

The Node.js dev site's Intro to Node.js will give you a path through the woods
Flavio Copes's React and Next books (free!) will get you far enough to become productive

Do not over-use the Shopify's CLI tunnel capabilities, to avoid getting hit with "Too Many Connections" with ngrok - see https://github.com/Shopify/shopify-app-cli/issues/449 for details. I scaffold with the CLI (meaning I let it build the directory) but run ngrok http XXXX myself and not through the CLI. Never once hit the too many connections problem.


Create a mobile (Flutter) Application that leverages the Pay With Wallet functionality on the ChiSpend widget to make an airtime payout.

What should your pr include?

A video show casing the flow till payout.
Screenshots/apk

TIPS AND REFERENCES:

The javaScript channel  for the webview is ChiSpendChannel.
Get api key
More info

Assign this to me @Regedit-msc

I love to work on this. Please assign.

Hi @Mujhtech  and @AbhishekTiwari23 assigned to both of you
Feel free to implement your own versions of the same thing

Hello @uchibeke @Regedit-msc I would love to take it up too


fix(blazor-ui): update toggle button demo title

This Closes: #5433

@Hossein-Mirazimi Thanks for submitting this PR, but the good first issues are only for the first contribution, and resolving more than one of them is not allowed here. So please let the other new contributors take care of the rest.
You can try resolving other issues, especially the up for grabs ones.
I'm sorry but this PR is rejected and I have to close it.


#40 build UI

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 97.79249% with 10 lines in your changes missing coverage. Please review.

Project coverage is 96.60%. Comparing base (c3a18b4) to head (bbf7231).

Files
Patch %
Lines

src/views/NotFound.vue
95.65%
9 Missing :warning:

src/router/index.ts
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##           develop      #61      +/-   ##
===========================================
- Coverage    97.13%   96.60%   -0.53%
===========================================
  Files           19       20       +1
  Lines         1745     1797      +52
  Branches        74       76       +2
===========================================
+ Hits          1695     1736      +41
- Misses          50       61      +11

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


DTAExecutionHost.exe The process was terminated due to an unhandled exception.

I have test VM Windows 7 Professional SP1 and  Microsoft Agents for Visual Studio 2013 v 12.0.40629
I decided move to  the new base-script system (vNext). When I have created new VM and using your "DeployVisualStudioTestAgent" task, I see installed Microsoft Agents for Visual Studio 2015 v 14.025420.1. Everything works excellent. But when I have try to install Test Agent (Interactive mode) on the my old VM I always get two errors in Event logs:
Error 1

Application: DTAExecutionHost.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.MissingMethodException
at Microsoft.VisualStudio.TestService.AgentExecutionHost.Program.Main(System.String[])

Error 2

Faulting application name: DTAExecutionHost.exe, version: 14.98.25331.0, time stamp: 0x574e13b4
Faulting module name: KERNELBASE.dll, version: 6.1.7601.23418, time stamp: 0x5708a7e4
Exception code: 0xe0434352
Fault offset: 0x0000c54f
Faulting process id: 0x290
Faulting application start time: 0x01d1e18e5029f93b
Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\DTAExecutionHost.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 8ddd4ab7-4d81-11e6-a141-005056a545b2

Test Agent becoming in unused state. Right now I see only one way to fix it. It's reinstall my old VM.
I hope you have other ways to fix it. Please assist me with that
Thank you for advance!

@kardinal3000 when you say you are installing the test agent on "your old vm" does it mean you have both the agents on the same VM? That is something we do not support today.
Independent to that the missingmethodexception usually indicates a faulty install. This exception should never occur in a shipping product for obvious reasons.

@allendm-msft after running "Deploy Visual Studio Test Agent". The service Test Agent 2013 disappeared I cant find it in "uninstall a program" and I observe the only one test agent 2015. So, right now I have the only one Microsoft Agents for Visual Studio 2015 v 14.025420.1. update 3 on  my old vm.  Also I tried to make

Reboot VM
Uninstall/Ininstall Microsoft Agents for Visual Studio 2015 v 14.025420.1.. manually
Windows update
Update Framework 4.0, install Framework 4.5, 4.51, 4.6

I still try to find resolving of this problem

ideally a process dump wouldve helped. if you can get a dump of the dtatexecutionhost.exe and share the call stack for the missingmethodexception it would help.

@kardinal3000 do you have any more data for us?

Yes I have, sorry for delay with reply I will send the next week at the moment i have a lot of other issues

Guys, could you please close this issue. It's no more topical question.


Slow connection with HTTP/2

Output of restic version
restic 0.13.1 compiled with go1.18 on linux/amd64
How did you run restic exactly?
restic snapshots

What backend/server/service did you use to store the repository?
rest-server behind https proxy/ssl offloader with http/2 support
Expected behavior
time restic snapshots
... lots of output ...
-----------------------------------------------------------------------------------------------------------
662 snapshots

real    0m1.331s
user    0m0.807s
sys     0m0.045s

Actual behavior
time restic snapshots
... lots of output ...
-----------------------------------------------------------------------------------------------------------
662 snapshots

real    0m31.110s
user    0m0.804s
sys     0m0.099s

Steps to reproduce the behavior
Use RESTIC_REPOSITORY pointing to a proxy as an api-gateway for ssl-offloading with HTTP/2 support
eg export RESTIC_REPOSITORY=rest:https://<user>:<password>:backup.domain.com/repository

Do you have any idea what may have caused this?
This is an issue with GOLANG HTTP support since 1.17.3.
2022/08/13 17:42:24 restic/main.go:96   main.main   1   restic 0.13.1 (v0.13.0-359-gf0bb4f87) compiled with go1.18.3 on linux/amd64
2022/08/13 17:42:24 restic/global.go:690    main.open   1   parsing location rest:https://redacted/
2022/08/13 17:42:24 restic/global.go:673    main.parseConfig    1   opening rest repository at rest.Config{URL:(*url.URL)(0xc00014e900), Connections:0x5}
2022/08/13 17:42:24 debug/round_tripper.go:94   debug.loggingRoundTripper.RoundTrip 1   ------------  HTTP REQUEST -----------
HEAD /jingella/config HTTP/1.1^M
Host: archive.xippy.cf^M
User-Agent: Go-http-client/1.1^M
Accept: application/vnd.x.restic.rest.v2^M
Authorization: **redacted**^M
^M

2022/08/13 17:42:54 debug/round_tripper.go:111  debug.loggingRoundTripper.RoundTrip 1   ------------  HTTP RESPONSE ----------
HTTP/2.0 200 OK^M
Content-Length: 155^M
Content-Security-Policy: upgrade-insecure-requests^M
Date: Sat, 13 Aug 2022 07:42:24 GMT^M
X-Content-Type-Options: nosniff^M
^M

This shows a completely arbitrary 30 second delay between making the request, and receiving the response.
The same request using CURL completes in 200ms.   The api-gateway logs the request immediately (ie, as soon as it is made) but net/http waits 30 seconds before reporting the request complete to restic.
Do you have an idea how to solve the issue?
Rebuilding restic with go 1.17.2 eliminates the issue completely.
restic version
restic 0.13.1 (v0.13.0-359-gf0bb4f87) compiled with go1.17.2 on linux/amd64

This issue occurs with 13.0 (built with go1.18) but not with 12.1 (built with go1.16.6)
This issue also occurs if I manually build with go1.19.
Did restic help you today? Did it make you happy in any way?
always

This was resolved by upgrading the api-proxy (haproxy)

Thanks a lot for sharing the solution, that is always helpful!


Less compilation error

ERROR in ./~/css-loader?{"sourceMap":true,"importLoaders":2}!./~/postcss-loader/lib?{"sourceMap":true}!./~/less-loader/dist?{"sourceMap":true,"strictMath":true}!./~/preact-material-components/Button/style.css
Module build failed:

        .mdc-button.mdc-button--primary::before {
          background-color: color(var(--mdc-theme-primary, #3f51b5) a(12%)); } }
                          ^
Error evaluating function `color`: keyword.toLowerCase is not a function
      in /home/usulix/Development/accountsgui/node_modules/preact-material-components/Button/style.css (line 426, column 28)
 @ ./~/preact-material-components/Button/style.css 4:14-160 18:2-22:4 19:20-166
 @ ./src/lib/FormComponents/LoginButton.js
 @ ./src/components/login/index.js
 @ ./src/components/app.js
 @ ./src/index.js
 @ multi (webpack)-dev-server/client?http://localhost:8080 webpack/hot/dev-server ./index.js

Points me to trying to find the correct css processing configuration for webpack
Currently I have

use: ExtractTextPlugin.extract({
					fallback: 'style-loader',
					use: [
						{
							loader: 'css-loader',
							options: { sourceMap: CSS_MAPS, importLoaders: 2 }
						},
						{
							loader: `postcss-loader`,
							options: {
								sourceMap: CSS_MAPS,
								plugins: () => {
									autoprefixer({ browsers: [ 'last 2 versions' ] });
								}
							}
						},
						{
							loader: 'less-loader',
							options: { sourceMap: CSS_MAPS, strictMath: true }
						}
					]
				})

and the strictMath: true appears to be required to get through a different portion of the css
ERROR in ./~/css-loader?{"sourceMap":true,"importLoaders":2}!./~/postcss-loader/lib?{"sourceMap":true}!./~/less-loader/dist?{"sourceMap":true}!./~/preact-material-components/LayoutGrid/style.css
Module build failed:

  padding: 8px;
  padding: calc(var(--mdc-layout-grid-margin, 16px) - var(--mdc-layout-grid-gutter, 16px) / 2); }
^
Operation on an invalid type
      in /home/usulix/Development/accountsgui/node_modules/preact-material-components/LayoutGrid/style.css (line 21, column 2)
 @ ./~/preact-material-components/LayoutGrid/style.css 4:14-160 18:2-22:4 19:20-166
 @ ./src/components/login/index.js
 @ ./src/components/app.js

I was moving along well.. until this keyword.toLowerCase error popped up.
and it seems to be the inability of the webpack config I have to get a value from
var(--mdc-theme-primary, #3f51b5) a(12%)
what are you doing to support var() in your css processing, please.
Thanks and best regards
Greg

Hi @usulix!
I honestly haven't worked with less for a ong long time. I had similar issues with pre-css because of postcss-custom-properties.
I don't exactly know from what breaks in less from the top of my head, but if there is a repo where i can peep into i'll for sure give it a look.

Thanks prateekbh and I appreciate the response..
I will look into postcss-custom-properties and see if that give me any extra info on my issue.
Regards,
Greg

Any news on this? Are you using or have you tried preact-cli?

I have solved it.  After searching a lot got this issue from less repo.
You have to enable strictMath: true in your webpack less loader option.
The problem is by default less was not supporting math function in css like calc, scale ..etc
{
	loader: 'less-loader',
	options: { strictMath: true}
}

Thanks so much @john1jan u rock 👍 .
@usulix lemme know if this still persist for you.


[Theming] TypeError: context.report() called with a messageId, but no messages were present in the rule metadata.

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Steps:

Current behavior 😯
I have created a theme and added some custom colors but my project breaks on our typescript linters. I am not completely sure why this happens, I think that I have created the theme according to the docs(https://mui.com/material-ui/customization/palette/#customization). However, there are also some legacy code since it's a project in a bigger organisation so I am not sure if all the declarations are correct. I have been trouble shooting for a while and not been able to find the source of the issue.
The error occurs at interface Palette { line of the code (line 13 below).
`declare module "@mui/material/styles/createTheme" {
interface Theme {
name: string;
type: string;
}
interface ThemeOptions {
name?: string;
type?: string;
}
}
declare module "@mui/material/styles" {
interface Palette {
vit: Palette["primary"];
svart: Palette["primary"];
ljusGranit: Palette["primary"];
löv: Palette["primary"];
gräs: Palette["primary"];
äng: Palette["primary"];
mörkHimmel: Palette["primary"];
himmel: Palette["primary"];
mossa: Palette["primary"];
höstlöv: Palette["primary"];
mörkHöstlöv: Palette["primary"];
raps: Palette["primary"];
varning: Palette["primary"];
varningText: Palette["primary"];
rosa: Palette["primary"];
granit: Palette["primary"];
sand: Palette["primary"];
snö: Palette["primary"];
}
interface PaletteColor {
hover?: string;
}
interface PaletteOptions {
vit: PaletteOptions["primary"];
svart: PaletteOptions["primary"];
ljusGranit: PaletteOptions["primary"];
löv: PaletteOptions["primary"];
gräs: PaletteOptions["primary"];
äng: PaletteOptions["primary"];
mörkHimmel: PaletteOptions["primary"];
himmel: PaletteOptions["primary"];
mossa: PaletteOptions["primary"];
höstlöv: PaletteOptions["primary"];
mörkHöstlöv: PaletteOptions["primary"];
raps: PaletteOptions["primary"];
varning: PaletteOptions["primary"];
varningText: PaletteOptions["primary"];
rosa: PaletteOptions["primary"];
granit: PaletteOptions["primary"];
sand: PaletteOptions["primary"];
snö: PaletteOptions["primary"];
}
}`
Has anyone else had a similar issue or am I writing my declarations wrong?
Expected behavior 🤔
No response
Context 🔦
No response
Your environment 🌎

npx @mui/envinfo
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

@ozgurbaserdem Without a minimal reproduction, we cannot take a look. Does the following thread https://github.com/typescript-eslint/typescript-eslint/issues/2451 help?


[Bug] Advancements does not send correctly

Existing Issues Searched

[X] I confirm that I have searched for existing issues before reporting to avoid duplicate reporting.

Simplest Environment Tested

[x] I confirm that this problem still exists with only MCDiscordChat and Fabric API installed.

Docs and Changelog Read

[X] I confirm that I followed the MCDC Docs and read the Changelog, but this problem still exists.

Java Version
17.0.2
Minecraft Version
1.18.2
MCDiscordChat Version
MCDiscordChat 2.0.0-alpha.1
Description
First time making a bug report, forgive me if there are any deficiencies.
Advancements are not sending correctly to the Discord chat. Advancement announcement is being sent of the Discord chat when player hasn't made the advancement in-game. The thing being picked up by the mod is presumably the player adding requirements towards reaching the advancement (in our case, players were setting foot in biomes they haven't found before):

Upon editing the config file by removing the message completely from "advancementChallenge", the server then crashes whenever the mod presumably wants to send a message but finds no text to send and causes and entity ticking crashes. An example (this was the first crash) :
crash-2022-04-17_14.47.18-server.txt
Currently removed the mod from the server to stop the crashes and also because it was sending advancements wrongly.
If possible, I hope there is a way to choose what messages are to be sent to which Discord channel and which ones we can disable. I realize that simply removing the messages completely from the config file causes crashes (config attached is from the one that caused crashes).
To Reproduce
Do actions that will add requirements towards a game advancement and compare the in game advancement announcement vs the Discord chat advancement announcement.
Log
Unfortunately there is no longer any log from the day the advancement issue happened, my apologies.
Config
{
  "generic": {
    "useEngInsteadOfChin": true,
    "botToken": "",
    "botPlayingStatus": "Minecraft",
    "botListeningStatus": "",
    "webhookUrl": "",
    "channelId": "",
    "consoleLogChannelId": "",
    "useUuidInsteadOfName": true,
    "avatarApi": "https://mc-heads.net/avatar/%player%.png",
    "broadcastCommandExecution": true,
    "announceHighMspt": false,
    "msptLimit": 50,
    "excludedCommands": [
      "/tell"
    ],
    "adminsIds": []
  },
  "multiServer": {
    "enable": false,
    "host": "<IP_ADDRESS>",
    "port": 5000,
    "name": "SMP"
  },
  "textsZH": {
    "serverStarted": "**服务器已启动！**",
    "serverStopped": "**服务器已关闭！**",
    "joinServer": "**%playerName% 加入了服务器**",
    "leftServer": "**%playerName% 离开了服务器**",
    "deathMessage": "**%deathMessage%**",
    "advancementTask": "**%playerName% 达成了进度 [%advancement%]**",
    "advancementChallenge": "**%playerName% 完成了挑战 [%advancement%]**",
    "advancementGoal": "**%playerName% 达成了目标 [%advancement%]**",
    "highMspt": "**服务器 MSPT (%mspt%) 高于 %msptLimit%！**",
    "consoleLogMessage": "[%time%] [INFO] %message%"
  },
  "textsEN": {
    "serverStarted": "**Server started**",
    "serverStopped": "**Server stopped**",
    "joinServer": "**%playerName% joined the game**",
    "leftServer": "**%playerName% left the game**",
    "deathMessage": "**%deathMessage%**",
    "advancementTask": "**%playerName% has made the advancement [%advancement%]**",
    "advancementChallenge": "",
    "advancementGoal": "**%playerName% has reached the goal [%advancement%]**",
    "highMspt": "**Server MSPT (%mspt%) is above %msptLimit%!**",
    "consoleLogMessage": "[%time%] %message%"
  }
}

presumably the player adding requirements towards reaching the advancement (in our case, players were setting foot in biomes they haven't found before)

This should be the reason.

If possible, I hope there is a way to choose what messages are to be sent to which Discord channel and which ones we can disable.

If I have a way to fix achievements not sending correctly, do you still need to disable them?

If I have a way to fix advancements not sending correctly, do you still need to disable them?
If it can be fixed, it's not necessary to disable them for the main server chat channel, but might be useful for us to disable it for the logs channel. In another Fabric-Discord chat mod I'm using currently (Fabric-Discord Link), it allows us to choose what message we'd like to disable for the server chat vs the log channel, which is useful just so that chat messages and other things do not drown out other messages that is more relevant in the log channel.

The current MCDC code does not send this kind of messages to the log channel. To keep the Config uncomplicated, I won't do a way to disable them.

Oh? The first time I tested it still sent in game chat messages to the log channel. Here's a screenshot:

I made sure to input the IDs for the server chat and and the log channel separately. Is there something in the settings that I missed?

Oh, I mean advancement messages are not sent, player chats are still sent. This is to keep the log channel and console log with the same content. Chinese?

Ah ok I see, that's fair then.
And yes Chinese, but my Mandarin is not great these days.
Thanks for the response! Looking forward to seeing more development in the mod. :)

Please try the latest build version and see if there is any problem.

Hello! Been a bit busy and missed your latest reply. I've downloaded the latest build (#94) and did some testing, so far the advancements are working fine.
However, I encountered a new issue which I'm not sure how to solve. The Discord messages are not sending to the in game chat and this error appears in the console:

Please check if the Texts of your Config are formatted incorrectly.

Hmmm this is only a temporary solution. I will add markdown escaping to fix this bug so that you can show your nickname in Minecraft.

Hmmm this is only a temporary solution. I will add markdown escaping to fix this bug so that you can show your nickname in Minecraft.

Fixed

Hmmm this is only a temporary solution. I will add markdown escaping to fix this bug so that you can show your nickname in Minecraft.

Fixed

Tested and it works without issues. Thank you! :)


Is "lxde-desktop" target broken?

Hi,
I failed to add "lxde-desktop" target to an existing chroot. Then I tried creating a new chroot with the following command using the latest crouton (version 1-20150404180843~master:66d0393b):
sudo sh ~/Downloads/crouton -n lubuntu -r trusty -t lxde-desktop,chrome
After a few minutes, installation failed with the same error message:
Package 'network-manager' is not installed, so not removed
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
lubuntu-desktop : Depends: network-manager-gnome but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Failed to complete chroot setup.
Did I missing anything or just run into a bug?

@haojiezhu if your existing target was lxde, just apt-get install the missing package that desktop would provide. I wouldn't run network manager in a chroot, since most of the functions won't work well with chrome which owns the network processes. What is it that you want to do in network manager that you can't configure in the Chromium OS host?

@tedm I didn't try to install network manager. Crouton script did it automatically. I'll try to make a new chroot without "chrome" target and see if that helps.

I tried installing "lxde-desktop" target only and still failed with the same "network-manager-gnome" error. It basically says "lxde-desktop" depends on "network-manager-gnome" package, which can't be installed for some reason.

See #1408. Fix is coming soon.

@haojiezhu what you may want to do until the #1408 fix arrives is to just install -t lxde and then apt-get the packages you need.

Fix is in... Just update your chroot.
On Sat, Apr 11, 2015 at 8:09 PM, tedm<EMAIL_ADDRESS>wrote:

@haojiezhu https://github.com/haojiezhu what you may want to do until
the #1408 https://github.com/dnschneid/crouton/issues/1408 fix arrives
is to just install -t lxde and then apt-get the packages you need.
—
Reply to this email directly or view it on GitHub
https://github.com/dnschneid/crouton/issues/1609#issuecomment-91949652.

--
DennyL@GMail


PII detection in Image

superseded by https://github.com/sahajsoft/pii-detection-and-anonymizer/pull/28


Make sure paths can be serialized

This is not yet ready, but the request had to be made to activate Travis testing.  The complete tests works under IntelliJ and Eclipse, but not for sbt.  It complains about DirectedGraph not being accessible during deserialization.  I have yet to understand how that can be.

This change is necessary for Mention serialization, which was broken.  No client seemed to have noticed before Eidos.


configuring runtime verbosity for debugging?

is it possible to increase the runtime verbosity when the PDF generation occurs? I think this would be helpful for troubleshooting complex pages being generated. If it is relatively simple, I can help contribute documentation for it.

This is not a problem. What specific messages would like to see?

great to hear. Starting out out I think a single verbose level of debugging would be helpful noting what steps in converting the HTML to the PDF have occurred. As a user I've primarily want to see the operations are completing successfully and perhaps additional diagnostic info for when assets or other things within the PDF generation aren't occurring. I'm not sure if cef exposes anything here. If they do, i'd probably be fine with whatever they print out.


Join aligner window isn't displaying anymore

Basic information

My operating system and version: Windows 10 Pro 22H2
My MZmine version: 3.4.0

What happened

Since the latest update (MZmine 3.4.0) it is not possible to display the parameter window for join aligner module. So we can not parameter the join aligner module anymore (despite this, the module works anyway and generates an aligned feature list).
This issue also occurs in the batch queue module, i.e., it is not possible to add this module to the queue (and of course to set it up).

Thank you for your kind help !

I found the bug. Thanks for the report. It will work fine if you load it already setup. Its a GUI bug with the parameter component.


Provide unit tests for SslConfigurationProvider.

Starting to unit test and harden everything we have so far.

@kimoonkim @ssuchter for review

Think I want #173 to merge first actually since that PR heavily refactors the class in question.

Please rebase onto branch-2.1-kubernetes and send this PR into that branch instead of k8s-support-alternate-incremental which is now deprecated.

This is likely out of date with V2 submission work.


WfExS workflow warming up - add containers to 5-Safe RO-Crate

WfExS 1.0 release should have container support - we'll need to figure out how/where we deploy the outside WfExS and how it interacts with the existing crates.


Fix interviewee role ordering and deactivate ACC ref code

MIC-483
The order of the involvement should change.
options for “How was the interviewee involved?” read: Perpetrator, Victim, Witness, Other.
MIC-481
On Screen a Referral, there is not an option to “Support through ACCT”
On Make a CSIP Decision, there is not an option to “Support through ACCT”

DECISION_OUTCOME_TYPE already has ACCT deactivated, so in this PR we only deactivate ACCT for Screening Outcome Type

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 87.49%. Comparing base (e91f166) to head (63382ed).

Additional details and impacted files
@@            Coverage Diff            @@
##               main     #130   +/-   ##
=========================================
  Coverage     87.49%   87.49%
  Complexity      701      701
=========================================
  Files           136      136
  Lines          2175     2175
  Branches        147      147
=========================================
  Hits           1903     1903
  Misses          188      188
  Partials         84       84

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add Peking University Info

Add Peking University email info

@yadongcao  Peking University has another official domain. Also, the email domain of  Peking University is often abused by third parties. Therefore, I have to reject this request. Please apply for a free educational license with an official document that proves that you are a student. You can do it using the "OFFICIAL DOCUMENT" tab at https://www.jetbrains.com/shop/eform/students.


Uploaded file ('report.xml?attredirects=0&d=1') does not exist

During the test conversion for issue #51, the following message was raised:
Uploaded file ('/home/douglas/git-repositories/dfhawthorne.github.io/docs/home/12c-ocp-upgrade/section-1-new-features-of-oracle-database-12c/emergency-monitoring-real-time-addm-compare-period-addm-and-active-session-history-ash-analytics/https://dfhawthorne.github.io/home/12c-ocp-upgrade/section-1-new-features-of-oracle-database-12c/emergency-monitoring-real-time-addm-compare-period-addm-and-active-session-history-ash-analytics/perform-emergency-monitoring-and-real-time-addm/report.xml?attredirects=0&d=1') does not exist

The following commands found two (2) occurrences:
find docs -name "*.html" -type f -print0 | \
    xargs -0 grep -l report.xml

The results are:
docs/home/12c-ocp-upgrade/section-1-new-features-of-oracle-database-12c/emergency-monitoring-real-time-addm-compare-period-addm-and-active-session-history-ash-analytics/perform-emergency-monitoring.html
docs/home/12c-ocp-upgrade/section-1-new-features-of-oracle-database-12c/emergency-monitoring-real-time-addm-compare-period-addm-and-active-session-history-ash-analytics/perform-emergency-monitoring-and-real-time-addm.html

No occurrences of report.xml were found as confirmed by teh following command:
find docs -name "*report.xml*" -type f

When issue #56 was resolved, any references to report.xml were removed as uploaded files are not stored in the New Google Sites version of the pages.
This issue is closed as it is no longer relevant.


Allow connection_pool to be set in RedisSettings

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@            Coverage Diff             @@
##             main     #473      +/-   ##
==========================================
- Coverage   96.27%   96.01%   -0.27%
==========================================
  Files          11       11
  Lines        1074     1079       +5
  Branches      209      190      -19
==========================================
+ Hits         1034     1036       +2
- Misses         19       21       +2
- Partials       21       22       +1

Files
Coverage Δ

arq/connections.py
87.50% <100.00%> (-2.57%)
:arrow_down:

Continue to review full report in Codecov by Sentry.

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


No lighthouse report is being generated

Describe the bug
When building the site in repo reinierladan.nl, in the deploy summary I get:
@netlify/plugin-lighthouse ran successfully
Summary for path '_site/': undefined
In the logs I see minimal activity from the Lighthouse plugin. It installs and does this after:
4:08:19 PM:   2. @netlify/plugin-lighthouse (onPostBuild event)
4:08:19 PM: (@netlify/plugin-lighthouse onPostBuild completed in 8ms)
4:08:20 PM: Post processing - header rules

I have the same setup running for repo reinier.fyi and that works pretty well.
There is also no report generated and no Lighthouse UI visible in the Deploy details.

I've setup the netlify.toml here:
https://github.com/reinier/reinierladan.nl/blob/main/netlify.toml
And I've also activated the Lighthouse integration from within Netlify to see if that solves it. It does not unfortunately.

I also have this issue, but only with some of my sites. Some work and some don't - seemingly without reason. I have tried uninstalling and reinstalling the integration - which didn't work.

@reinier I was able to fix this, for at least one of my sites, by specifying an env variable for NODE_VERSION to be higher than 12. In my case, both 14 and 16 worked. I found #500 and that tipped me off that this might work.

I'm not deploying my site with Netlify anymore but here you can see what I meant. The solution was to install the plugin via the netlify.toml file.

Thank you @rodrigoalcarazdelaosa for sharing the additional context! This is really helpful for us to know, even if you are unblocked for now - appreciate you taking the time ❤
I'll go ahead and close this issue, but if anyone has similar trouble in future please don't hesitate to re-open or create a new issue.

Hi @aitchiss, maybe you could check my repo to further investigate. I thought the NODE_VERSION var solved the issue, but it only did it once. My current builds lack any Lighthouse info, even though I think everything is setup correctly.

I get similar behaviour. I have the plugin installed on several sites and it works on all but one. They are all Nextjs and all built with the same commands, yet one of them producs no lighthouse output.

@danieljamesross @jodiedoubleday is it possible to link us to an example deploy, or to your repo (if privacy allows)?

Hi @aitchiss my repo on GitHub is private but if you are part of the Netlify Team then you might be able to see this deployment - https://app.netlify.com/sites/simon-community/deploys/643eb32ba785270008bd29a7

@danieljamesross @jodiedoubleday is it possible to link us to an example deploy, or to your repo (if privacy allows)?

Afraid not, it's completely private

Thank you all for the further details - we'll investigate and try to get to the bottom of this - having the couple of different examples helps so thanks again!

I have the same issue, and my repo is public if you're looking for more data on the source of this issue.

Repo: https://github.com/dylankenneally/http-statuses
NODE_VERSION set in netlify.toml
Plugin set in netlify.toml too
Logs don't seem to be showing anything handy

1 plugin ran successfully

Select for details.

@netlify/plugin-lighthouse
@netlify/plugin-lighthouse ran successfully

Summary for path 'build/': undefined

Thanks again everyone for volunteering debug information ❤
Please can you try upgrading to v4.1.1 of the plugin and checking if your issues have been resolved? I verified the fix locally against a clone of both @reinier and @dylankenneally's repos, but please do re-open this issue if you still encounter the same problems after upgrade.

Just upgraded and re-deployed:

At the moment the lighthouse plugin runs on a static version of the site served on a local express server, which causes lots of challenges with sites where the build process doesn't result in simple static html files in the build directory. However - we do have some experimental functionality in place that will run the audit instead on your live deploy. There are lots of benefits to this (eventually we expect it to become the default plugin behaviour), but I bring it up because if the issues you're seeing are related to relying on SSR the new functionality might solve it.
If you'd like to give that new functionality a spin and see if it unblocks things - check out the instructions here

OK, this works for me now. Thanks very uch for your help!

Hi @aitchiss, thanks for digging into this. I see more happening in my logs, but still no report (repo https://github.com/reinier/reinierladan.nl). This is the part of the build log that covers the lighthouse plugin:
6:29:51 PM:   2. @netlify/plugin-lighthouse (onPostBuild event)
6:29:51 PM: ────────────────────────────────────────────────────────────────
6:29:51 PM: Starting post processing
6:29:51 PM:
6:29:51 PM: Generating Lighthouse report. This may take a minute…
6:29:51 PM: Running Lighthouse on _site/
6:29:51 PM: Post processing - HTML
6:29:51 PM: Error: Could not find local browser
6:29:51 PM:     at getBrowserPath (file:///opt/build/repo/node_modules/@netlify/plugin-lighthouse/src/lighthouse.js:10:11)
6:29:51 PM:     at async runAuditWithServer (file:///opt/build/repo/node_modules/@netlify/plugin-lighthouse/src/lib/run-audit-with-server/index.js:19:25)
6:29:51 PM:     at async runEvent (file:///opt/build/repo/node_modules/@netlify/plugin-lighthouse/src/lib/run-event/index.js:73:9)
6:29:51 PM:     at async onPostBuild (file:///opt/build/repo/node_modules/@netlify/plugin-lighthouse/src/index.js:37:9)
6:29:51 PM: Post processing - header rules
6:29:51 PM:     at async Object.run (file:///opt/buildhome/node-deps/node_modules/@netlify/build/lib/plugins/child/run.js:14:5)
6:29:51 PM:     at async handleEvent (file:///opt/buildhome/node-deps/node_modules/@netlify/build/lib/plugins/child/main.js:28:42)
6:29:51 PM:     at async process. (file:///opt/buildhome/node-deps/node_modules/@netlify/build/lib/plugins/ipc.js:91:24)
6:29:51 PM: Post processing - redirect rules
6:29:51 PM:
6:29:51 PM: (@netlify/plugin-lighthouse onPostBuild completed in 11ms)
6:29:51 PM:
My site is fully static.

@aitchiss 4.1.1 seems to have resolved the issue for our Gatsby site. Thank you.

@aitchiss v4.1.1 has resolved the issue for me too, thank you - it really is appreciated.

@reinier I'm looking at your repo and seeing version of 4.0.7 of the plugin being the resolved version in your yarn.lock - I can see v4.1.1 defined in your package.json though so I'm wondering if the lockfile didn't generate as expected when you upgraded? Can you retry the upgrade of the plugin and make sure the resolved version in the lockfile updates?

@aitchiss the deploy with a clear cache worked great! But your hunch about it not working without cache is true unfortunately. Same "Error: Could not find local browser" when deploying with cache after I did the deploy with a clear cache.

Thank you for confirming! Re-opening this issue so we can investigate the caching problem further - thanks for your patience!

Yep, I want to report the same thing. This plugin doesnt work if deploying without clearing cache

@aitchiss Hi Suzanne- might https://github.com/netlify/netlify-plugin-lighthouse/issues/598 be related to this issue?


It should be possible to override the validate method from the Flow textConnector

The fix of this PR vaadin/vaadin-text-field-flow/pull/116 is supposed to override the validate method of client-side in case when the field is marked as required from the server side so to resolve this issue in here vaadin/vaadin-text-field-flow/issues/104
The problem is that the validate method of client-side is still called when blured. Not sure about the reason why this happens but a guess would be the fact that the blur event is registered with the validate method when the component is being initialized .
A possible solution to this issue IMO is to have the client side validate method changed to this:
   validate() {
      return this.doValidate();
    }
    doValidate(){
      return !(this.invalid = !this.checkValidity());
    }

and after that have the Flow textConnector override the doValidate method instead of validate method.
The whole change will also fix vaadin/flow/issues/3230

The reason why this happens is this line:
https://github.com/vaadin/vaadin-text-field/blob/48147e5163baff3ca0f710b6bd725f13a532e2e1/src/vaadin-text-field-mixin.html#L509
So, instead of using this.validate.bind(this) we should have blurlistener like that:
_onBlur() {
  this.validate();
}

And the line above should be changed like this:
this._boundOnBlur = this._onBlur.bind(this);

That would fix the issue without any extra methods.

Thanks this is really a cleaner solution than the one I was previously suggesting. In this way there is no need to change anything in the Flow component for the fix to be applied


About the always.selected parameter problem

Dear community,
I use the example data from the corehunter package in R and I tried to use always.selected function. Unfortunately, I failed to select particular IDs I want. Can you help me to fix the problem? Thank you!
The code I ran in R as below:
library (corehunter)

dist.file <- system.file ("extdata", "distances.csv", package = "corehunter")
my.data <- distances (file = dist.file)

core.test <- sampleCore(my.fasta, always.selected = integer(1))
core.test2 <- sampleCore(my.fasta, always.selected = character("Bred_0003"))

After I ran the code:
core.test <- sampleCore(my.fasta, always.selected = integer(1))
or
core.test2 <- sampleCore(my.fasta, always.selected = character("Bred_0003"))
The message showed:
Error in .jcall("RJavaTools", "Ljava/lang/Object;", "invokeMethod", cl,  :
  java.lang.IllegalArgumentException: Error while creating subset solution: set of selected IDs should be a subset of set of all IDs.

I see the issue now. always.selected needs to be a vector. So please try the following if you always want to include the first accession.
core.test <- sampleCore(my.data, always.selected = c(1))
For the other fixed indices, simply specify them by index eg.
core.test <- sampleCore(my.data, always.selected = c(1, 3))
Please can you confirm this works for you, and I will close the issue?

Thank you for the reply. Do you mean that I can not use a vector including particular ID for the always.selected parameter? The value that always.selected parameter can detect is only the integer/number, not the character/ID.

I am not really sure why this does not work
core.test2 <- sampleCore(my.data, always.selected = c("Bred_0003"))

Dear Dr. Davenport,
The previous code you suggested can run:
core.test <- sampleCore(my.data, always.selected = c(1))

I also don't know why it's doesn't work about this code:
core.test2 <- sampleCore(my.data, always.selected = c("Bred_0003"))

I will have a look again at the weekend. Looking at the code it should work.

Thank you for the help.


Documentation issue: Documentation

If I click on the edit page button, I get redirect to an 404 page. If I remove the /content part of the url, everything works.

Thanks for the report, I've updated the documentation so this should get fixed very soon.


*add ITeam University to JetBrains

@Klass24 First stage of verification passed, official domain is iteam-univ.tn as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@Klass24 Pull request merged. Thank you.


test: refactor jest test negative test cases - phase 1

Commit to be reviewed
test: refactor jest test negative test cases - phase 1
Primary Changes
---------------
1. Refactored all remaining negative test case exception assertions under cacti/packages Removed try-catch blocks, replaced with declarations through jest-extended's own API.

Fixes #3483

@jagpreetsinghsasan
Should I make a issue to investigate the inconsistencies in deploy-contract-from-json-xdai.test.ts and make this issue dependent on that?

Closing this due to inactivity, please feel free to re-open anytime if/when bandwidth is available to take it to the finish line (some of the checks are failing such as the linter)


Menu Emote system lost and caused plugin bug as well.

The story is that one day I opened Discord by installing better discord earlier, it turned out to be a normal Discord, so I tried uninstalling it and reinstalling it, but there was a menu that didn't appear to be Menu Emotes system, which it should have, and I tried to install the Plugin, so I asked if there was anyone like me.(I tried deleting the file better discord and reloaded but it's still the same please help me at)

It says open but it's like this, what's the bug?

when this update arrives? i have the same problem

The emote system was disabled due to discord updates breaking it, this affects all users.s


Cosmos with CMK in KeyVault, where KV uses Private Endpoint

I'm wondering how you would go about configuring Cosmos to use a CMK pulled from a KeyVault, where the KeyVault uses a Private Endpoint.
Can Cosmos somehow access a KeyVault using Private Endpoint?  Or is this an incompatible scenario?
Can you please add this to your documentation - PE's are becoming increasingly popular.

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

ID: 5d8489d0-7ec1-59bb-053c-014af93c4095
Version Independent ID: ec72532b-c8ac-92c9-5bed-0e497660e4ea
Content: Configure customer-managed keys for your Azure Cosmos DB account
Content Source: articles/cosmos-db/how-to-setup-cmk.md
Service: cosmos-db
GitHub Login: @ThomasWeiss
Microsoft Alias: thweiss

Hello @JohnDelisle
I have assigned the issue to the content author for further review.

@JohnDelisle Thanks for the question. That scenario would indeed be incompatible, as Cosmos DB wouldn't be able to access the Key Vault instance through its private endpoint. We're tracking this gap on our roadmap, but I don't have any ETA to share for now.
I agree that this should be mentioned in our docs and I'm adding this update to our backlog.
#please-close