(operate) feat: update availableOn for contribute contracts

Proposed changes
adds links to contribute for contribute staking contracts

Types of changes
What types of changes does your code introduce?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Should it be “0”? or would “n/a” work?

yes agreed, should be 0


Data flow write up

I have done three things in this PR:

Added a write-up of the things that have been spoken about in the forums surrounding data flows, which I could not find in any docs.
Added links to a whole lot of orphaned pages, to make the left navigation more complete, and pages more findable.
Removed a couple of pages that were totally blank.

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


Interaction decomposition

Implement projection to homology classes via local iFFT
H(x) = sum_k h(k) x(k)

where x(k) = prod_i ei^(ki xi)

This extends the representation of local observables as polynomials in the binary case, +-1 being replaced by Nth-roots of unity.

In practice this corresponds to a large batch of small FT transforms: best implemented as a sparse matrix

Note that we have then:
h(k) = sum_x H(x) k(x)

where k(x) = prod_i ei^(ki xi) / Ni

with mass factor Ni


Draw hercules art

Add a cool and funny doodle! 🎨
It would be nice if the art could be associated/symbolise strength and power in an abstract way. 💪
This is an open doodle/drawing challenge rather than a technical one.
So, draw something up on a piece of paper and share it in the comments.
Prize: If the winner is studying at KGP, they get a GitHub Octocat sticker and a dinner treat!
Voting: Use 👍 if you like a doodle.
Please do not use 👎 as this be discouraging for others.
Deadline: Thursday, 25th October

Inspired by Mr.Doodle

cc @xypnox

Fact :  A neamus lion was strangled by Hercules. Thus, his skin was worn by Hercules as a symbol of strength

Some reference to Hercules' 12 labours would be super cool. 😃

Eleventh Labour: Golden Apples of the Hesperides

Eleventh Labour: Golden Apples of the Hesperides

Too late but here is my rendition of strength/power.  I almost forgot.
Based on the current vote count, we will add @nupurgunwant's artwork as the logo. 😄
Thanks a lot!


DO cluster provisioning fails on master build

Rancher Version: Master
root@soumyatestserver:~# sudo docker images
REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE
rancher/rancher     master              7a2ec2a14308        14 hours ago        439.5 MB
Steps:

Create a cluster using Digital Ocean provider nodes
Cluster creation fails.
The nodes are getting recreated as ssh fails .
Error message below:

Happens with EC2 as well.  Not just a DO issue.  Looks like it's all of RKE.

Tested with master build from Nov 28. Created cluster using Digital Ocean nodes.
Cluster provisioning was successful.


Removed statement about no conflicts in line 41

Removed statement as per @lomayor
Related to issue #5636

@lomayor - PR is ready for final review. This is based on issue #5636.
Thank you.
cc: @kenwith


AttributeError: '_RSAPrivateKey' object has no attribute 'sign'

I am want test usb dfu example in zephyr, but imgtool.py report that error. may be I installed the wrong version cryptography?
~/debug/port/github-os/mcuboot/scripts/imgtool.py sign \
> --key ~/debug/port/github-os/mcuboot/root-rsa-2048.pem \
> --header-size 0x200 \
> --align 8 \
> --version 1.2 \
> --included-header \
> ./zephyr/zephyr.bin \
> signed-zephyr.bin
Traceback (most recent call last):
  File "/home/qianfan/debug/port/github-os/mcuboot/scripts/imgtool.py", line 148, in <module>
    args()
  File "/home/qianfan/debug/port/github-os/mcuboot/scripts/imgtool.py", line 145, in args
    subcmds[args.subcmd](args)
  File "/home/qianfan/debug/port/github-os/mcuboot/scripts/imgtool.py", line 85, in do_sign
    img.sign(key)
  File "/home/qianfan/debug/port/github-os/mcuboot/scripts/imgtool/image.py", line 136, in sign
    sig = key.sign(bytes(self.payload))
  File "/home/qianfan/debug/port/github-os/mcuboot/scripts/imgtool/keys/rsa.py", line 92, in sign
    return self.key.sign(
AttributeError: '_RSAPrivateKey' object has no attribute 'sign'

try reinstalling:
pip install --force-reinstall cryptography

I suspect this might be due to some native built module, which stops working after OpenSSL is updated locally.

seems i confused python2 and python3. I had changed my default py to python3 and reinstall cryptgraphy and its depends, it works


fix: improve chain name typing

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Implemented Copy and Debug for ShaderParam::Link

Fixes #521

Self-merging since no-one is around.


[Backport 17.06] Overlay fix for transient IP reuse

Backport of the PR: https://github.com/docker/libnetwork/pull/1935
Squashed all the commits into single one and added 2 dependecies to avoid conflict resolution

Given the dates, it looks like it's not in 17.06.2. Is 17.06.3 planned?


WebView subject to SSL policy of of iOS makes loading non https impossible

RN0.33 When I try to load a non ssl domain inside a WebView, I get the same non secure domain exception that I get when I try to fetch a non secure domain that is not in the exceptions list.
Perhaps this is due to the use of the simulator (haven't tried 'live' yet), but in any case, WebView should not be subject to the same policy that prevents non secure fetching from a source not in the exceptions list.

I think all requests are subject to ATS settings, perhaps with the exception from those made with SFSafariViewController.
It looks like in iOS 10 there is a new setting NSAllowsArbitraryLoadsInWebContent but this along with other settings are controlled in your Info.plist.

Ok, good to know. I'll give that a go, thanks


option to show timestamps with logs

What is the goal / desired outcome?
see when certain output came from (particularly important for people still learning pach's semantics eg. did my datum actually get re-processed after i pushed my updated code? when did that retry happen? etc.)
If there is a way to accomplish this today via workaround, what does that require?

make sure to log verbosely and always include your own timestamps. this only works for your own log lines, not for pach-generated log lines

view raw logs, but this makes the output super noisy and hard-to-read

(Optional) What is your proposal for a feature to solve this?
a command-line flag to output lines prefixed with a human-readable timestamp (for bonus points, accept an optional user-defined date format string)
Note: This was one of the warts mentioned in @szeitlin's blog post

The --raw option on pachctl logs does this, it shows other stuff too so it's not quite as nice, but I'm not totally sure that we could add something that would be nicer than formatting the logs yourself using jq or something like it.

These are now shown


Custom hooks with docker throwing an error

When trying to run jazzer docker image by specifying --custom_hooks flag it throws the following error.
ERROR: com.example.ExampleFuzzer must define exactly one of the following two functions:
public static void fuzzerTestOneInput(byte[] ...)
public static void fuzzerTestOneInput(FuzzedDataProvider ...)
Note: Fuzz targets returning boolean are no longer supported; exceptions should be thrown instead of returning true.

Steps to reproduce -

Build a jar containing https://github.com/CodeIntelligenceTesting/jazzer/blob/main/examples/src/main/java/com/example/ExampleFuzzer.java, https://github.com/CodeIntelligenceTesting/jazzer/blob/main/examples/src/main/java/com/example/ExampleFuzzerHooks.java
Run the following command docker run --rm -v $(pwd):/fuzzing cifuzz/jazzer --cp=<path to jar> --target_class=com.example.ExampleFuzzer --custom_hooks=com.example.ExampleFuzzerHooks
Error is thrown.

If you run the same command without --custom_hooks flag it works fine.
I have not tried running jazzer with release binary

Custom hooks need to be packaged into separate JAR files (see https://github.com/CodeIntelligenceTesting/jazzer/blob/main/docs/advanced.md#custom-hooks, although this arguably shouldn't be hidden in the last paragraph of that section). The JAR files that contain them are added to the bootstrap class path and if that happens to your fuzz target, FuzzedDataProvider will be loaded twice in different class loaders.
Could you try whether moving the hook to a separate jar file resolves the issue?

When I tried running the following command with release binary it worked - ~/tools/jazzer --cp=~/tools/jazzer_standalone.jar:build/libs/hooks_examples-uber.jar --target_class=com.example.ExampleFuzzer --custom_hooks=com.example.ExampleFuzzerHooks
I can try with separate jars but since above command worked I'm guessing it might be an issue with the docker image

Hi @r00tdaemon !
We actually went down this root with another prodsec team. Jazzer didn't end up being the right solution for them and they pivoted to our closed source fuzzer. It was easier and they found bugs.
Want to discuss more?
david[dot]merian [at] code-intelligence[dot]com


VimEnter,DirChanged instead of BufReadPre

Wouldn't it make more sense to load configs based on actual current working directory (getcwd()) instead of what files are loaded?
Here is how I did it in my plugin:
  autocmd VimEnter * call s:Source()
  if exists("#DirChanged")
    autocmd DirChanged * if v:event['scope'] ==# 'global' | call s:Source() | endif
  endif

That's what I initially had, but I'm kind of all over the place when it comes to what I want loaded, so it didn't work out too well for how I work.
For example, I'm working on a web application that has a python backend and a bunch of typescript for the frontend. I have two separate confs for those since I don't really want to configure a python language server when I'm working on typescript and vice-versa.
So one example where this doesn't work when based off of cwd is if I'm writing some api call on the frontend, realize I need to make a quick edit to the response server-side, so I do a quick :vsplit ~/path/to/python/code because the config for that likely won't be in my cwd.
So tl;dr it kind of just loads what you need as you need it.
I can certainly imagine scenarios where this can clutter the conf of your current session though. Maybe it would make sense to make this a setting? e.g. g:autosource_by_cwd = 1
Also https://github.com/jenterkin/vim-autosource/issues/7 should support this via custom autocmds.

Without the v:event['scope'] ==# 'global' check you could use :lcd for window or :tcd for tab.

Oh yeah, this isn't really a problem for me since I set autochdir, I just more meant that I don't know that I want to have users have to set that or similar options to achieve this kind of flow, since setting those options can have wider effects.
My current thoughts are that most users would expect this plugin to source from $HOME to the file they are editing (though there's unfortunately no way of validating this hunch right now), so I think the current functionality makes sense as a sane default, at least for now.
I'll add in the g:autosource_by_cwd option and put it in the readme so that it's easily configurable without users having to write their own autocmds.

I've given this a bit more thought. I think I'm going to hold off on adding an option for this since support for disabling the autocmd and creating custom autocmds landed. I think what exists is a good default, but will definitely change if there's a significant number of users with a use-case where it doesn't work.


Example program doesn't compile; complains about alloc needing to be enabled

This trivial program doesn't compile:
use did_key::Fingerprint;

fn main() {
    match did_key::resolve("did:key:z9Bg7Lbpq3RzgN8RkgEuZqLDF4nT1ZzobJe9ZPbS6HJpQ") {
        Ok(k) => println!("{:?}", k.fingerprint()),
        Err(e) => println!("{:?}", e),
    }
}

The output is:
❯ cargo run
   Compiling form_urlencoded v1.2.1
error: the `alloc` feature must currently be enabled
  --> /home/harm/.cargo/registry/src/index.crates.io-6f17d22bba15001f/form_urlencoded-1.2.1/src/lib.rs:24:1
   |
24 | compile_error!("the `alloc` feature must currently be enabled");
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

error[E0277]: the trait bound `Cow<'_, _>: From<PercentDecode<'_>>` is not satisfied
  --> /home/harm/.cargo/registry/src/index.crates.io-6f17d22bba15001f/form_urlencoded-1.2.1/src/lib.rs:72:55
   |
72 |     decode_utf8_lossy(match percent_decode(&replaced).into() {
   |                                                       ^^^^ the trait `From<PercentDecode<'_>>` is not implemented for `Cow<'_, _>`
   |
   = help: the following other types implement trait `From<T>`:
             <Cow<'a, CStr> as From<CString>>
             <Cow<'a, CStr> as From<&'a CStr>>
             <Cow<'a, CStr> as From<&'a CString>>
             <Cow<'a, str> as From<&'a str>>
             <Cow<'a, str> as From<String>>
             <Cow<'a, str> as From<&'a String>>
             <Cow<'a, [T]> as From<&'a [T]>>
             <Cow<'a, [T]> as From<Vec<T>>>
             <Cow<'a, [T]> as From<&'a Vec<T>>>
   = note: required for `PercentDecode<'_>` to implement `Into<Cow<'_, _>>`

For more information about this error, try `rustc --explain E0277`.
error: could not compile `form_urlencoded` (lib) due to 2 previous errors

Adding the form_urlencoded crate explicitly fixes the error:
 ❯ cargo add form_urlencoded
    Updating crates.io index
      Adding form_urlencoded v1.2.1 to dependencies.
             Features:
             + alloc
             + std

I doubt this is expected behaviour. Notably I was able to run the test of this repo without this issue and no mention of alloc was made anywhere.
Crate version 0.2.1.

Same thing here. For a simple example project with just did-key dependency, it does not compile. I get the same error as OP.
However, in a more complex project, it works. With some investigation, the complex project has another dependency that also depends on form_urlencoded with the alloc feature enabled, and given how cargo feature unioning works it makes sense that it works.


#3397 Resovles broken Axes labels and ticks on inverted axes

This pull request resolves issue #3397
The issue stems from the use of terms Min and Max, which are not numerically minimum and maximum values when axes are inverted.
The fix was to find where the assumptions were in correct and locally calculate a "trueMin" or "trueMax" value.
I believe the proper fix would be to have IAxes retain Min and Max properties, but make them a true numeric minimum and maximum. This woul dbe augmented by an "Inverted" property.
Meanwhile, IXAxis would inherit Min, Max and Inverted, and could add Left and Right properties for convenience.
Similarly, IYAxis would inherit Min, Max and Inverted properties, but could add Top and Bottom peroperties for convenience.
Unfortunately that change would require extensive changes and careful planning and woud likely introduce breaking code changes for some users.
I believe my changes are safe for existing code.
Note that this pull request is dependant on pull request #3400 (I needed the inverted axes to be functioning to test all four scenarios (X/Y axes inverted with rotation)
Test code below.
using System;
using System.Linq;
using System.Windows;
using ScottPlot;

namespace Sandbox.WPF;

public partial class MainWindow : Window
{
    public MainWindow()
    {
        InitializeComponent();
        double[] Xs = Enumerable.Range(1, 5000).Select(i => (double)i).ToArray();
        var signal = WpfPlot1.Plot.Add.SignalXY(Xs, Generate.Sin(count: 5000, oscillations: 4));
        //Test with normal X axis
        //WpfPlot1.Plot.Axes.SetLimitsX(left: 100.1, right: 5100);

        //Test with reversed X axis
        WpfPlot1.Plot.Axes.SetLimitsX(left: 5100, right: 100.1);

        //Test with rotated SignalXY plot on normal Y axis
        //signal.Data.Rotated = true;
        //WpfPlot1.Plot.Axes.SetLimitsY(bottom: 100.1, top: 5100);

        //Test with rotated SignalXY plot on reversed Y axis
        //signal.Data.Rotated = true;
        //WpfPlot1.Plot.Axes.SetLimitsY(bottom: 5100, top: 100.1);

        //test with generic data type (not double) on normal X axis
        //int[] Xs = Enumerable.Range(1, 5000).Select(i => (int)i).ToArray();
        //int[] Ys = Enumerable.Range(1, 5000).Select(i => (int)i).ToArray();
        //var signal = WpfPlot1.Plot.Add.SignalXY(Xs,Ys);
        //WpfPlot1.Plot.Axes.SetLimitsX(left: 100.1, right: 5100);

        //test with generic data type (not double) on reversed X axis
        //int[] Xs = Enumerable.Range(1, 5000).Select(i => (int)i).ToArray();
        //int[] Ys = Enumerable.Range(1, 5000).Select(i => (int)i).ToArray();
        //var signal = WpfPlot1.Plot.Add.SignalXY(Xs,Ys);
        //WpfPlot1.Plot.Axes.SetLimitsX(left: 5100, right: 100.1);

    }
}

Unfortunately that change would require extensive changes and careful planning and woud likely introduce breaking code changes for some users.

You made some great observations, and I'm really happy with the implementation you suggested in this PR - thanks so much!
To be honest I didn't even realize that the cookbook example on https://scottplot.net/cookbook/5.0/AdvancedAxis/InvertedAxis/ was currently broken 🤦 Thanks for identifying the issue and fixing it!

Current recipe
Recipe after this PR


History file missing.

There are breaking changes between version 2 and 3.
Could you be so kind to create version.txt that will cover differences (so users can migrate more easily between versions).
Thanks

Added with acc0f96 https://github.com/amweiss/dark-sky-core/blob/master/CHANGELOG.md


private_path extension

I want to make a second private_path for the ROS topic path equivalent to the normal one.
I made the following changes:
In app.py :
def mqtt_bridge_node():
mqtt_private_path2 = mqtt_params.pop("private_path2", "")
...
config = create_config(mqtt_client, serializer, deserializer, mqtt_private_path, mqtt_private_path2)

def create_config(mqtt_client, serializer, deserializer, mqtt_private_path, mqtt_private_path2):
    private_path_extractor = create_private_path_extractor(mqtt_private_path, mqtt_private_path2)

In bridge.py:
class RosToMqttBridge(Bridge):
        def __init__(self, topic_from, topic_to, msg_type, frequency=None):
        self._topic_from = self._extract_private_path(topic_from)

In mqtt_client.py:
def create_private_path_extractor(mqtt_private_path, mqtt_private_path2):
    def extractor(topic_path):
        if topic_path.startswith('~/'):
            return '{}/{}'.format(mqtt_private_path, topic_path[2:])
        elif topic_path.startswith('v/'):
            return '{}/{}'.format(mqtt_private_path2, topic_path[2:])
        return topic_path

Unfortunately it doesn't work if I write something like that in my demo_params.yaml file:
topic_from: v/something
whereas this works:
topic_to: v/something
Any ideas what's missing?

Found the problem myself:
In the class RosToMqttBridge:
       rospy.Subscriber(topic_from, msg_type, self._callback_ros)
should change to:
       rospy.Subscriber(self._topic_from, msg_type, self._callback_ros)
In the class MqttToRosBridge:
self._mqtt_client.subscribe(topic_from)         self._mqtt_client.message_callback_add(topic_from, self._callback_mqtt)
should change to:
self._mqtt_client.subscribe(self._topic_from)         self._mqtt_client.message_callback_add(self._topic_from, self._callback_mqtt)


Options body view state is not updated like actions body view state

Description
I am trying to implement dependent external selects inside a modal but I am having problems passing the state of the first dropdown to the second. I can see the state I need inside the app.action listener but I am not getting the same state inside the app.options listener.
What type of issue is this? (place an x in one of the [ ])

[ ] bug
[ ] enhancement (feature request)
[x ] question
[ ] documentation related
[ ] example code related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x ] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[ x] I've read and agree to the Code of Conduct.
[ x] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
package version: ^3.6.0
node version: 14.18.0
OS version(s): hosted on Heroku
Steps to reproduce:

Click dropdown for first external select (case type)
Select a value for first external select (case type)
First external select (case type) Action listener fires logging updated state body.view
Click dropdown for second external select (case subtype)
Second external select (case subtype) Option listener fires. Notice/log old state values in body.view

Expected result:
After a value is selected for the case type, I would expect the view state values to be updated for the next listener call for case subtype.
Actual result:
Original/Old state values are being pulled back for the body.view variable under app.options -> body.view . I only see this state updated under app.actions -> body.view
Attachments:
body.view.state inside app.action("case_types"). I specifically need the case_create_case_type_block state.
  "state": {
    "values": {
      "case_create_user_select_block": {
        "case_create_selected_user": {
          "type": "users_select",
          "selected_user": "U01R3AE65GE"
        }
      },
      "case_create_case_type_block": {
        "case_types": {
          "type": "external_select",
          "selected_option": {
            "text": { "type": "plain_text", "text": "Incident", "emoji": true },
            "value": "Incident"
          }
        }
      },
      "case_create_case_subtype_block": {
        "case_subtypes": { "type": "external_select", "selected_option": null }
      },
      "case_create_case_owner_block": {
        "case_owners": { "type": "external_select", "selected_option": null }
      },
      "case_create_subject_block": {
        "case_create_case_subject": {
          "type": "plain_text_input",
          "value": null
        }
      },
      "case_create_description_block": {
        "case_create_case_description": {
          "type": "plain_text_input",
          "value": null
        }
      }
    }
  },

body.view.state inside app.options("case_subtypes")
  "state": {
    "values": {
      "case_create_user_select_block": {
        "case_create_selected_user": {
          "type": "users_select",
          "selected_user": "U01R3AE65GE"
        }
      }
    }
  },

I did also try to update the view myself hoping it would update the state variables inside app.action({ action_id: "case_types" })
    //need to update view with new values
    try {
      // Call views.update with the built-in client
      const result = await client.views.update({
        // Pass the view_id
        view_id: body.view.id,
        // Pass the current hash to avoid race conditions
        hash: body.view.hash,
      });
      console.log("Case Type View Update result:");
      console.log(JSON.stringify(result));

      //await ack();
    } catch (error) {
      console.error(error);
      //await ack();
    }

Hi @jaredjacob667 👋🏻
Thank you for the detailed description!
🐛 I believe you may be experiencing a server-side issue with external_state states. Does this issue https://github.com/slackapi/bolt-js/issues/660#issuecomment-706452626 sound similar to what you've experiencing? In the issue, we offer a few workarounds where you may need to capture the state from the action or submission.
🗒 I'd like to recreate your issue so that I can report it internally to the Slack API team. I really appreciate all of your code snippets and I'll try to piece together a small app from it. However, if you have a small app (based on the slackapi/bolt-js-getting-started-app, for example) then I'd greatly appreciate it if you could upload a zip. It would save me some time 🙂
Happy to work with you until we find a workaround as well!

I am experiencing a similar issue. When I update my view with an action (when I select an item in an external_*_select, I update some checkboxes in the view), then click my Submit button on the view, I am not seeing the correct state. If I manually check a checkbox, I do see the correct state. The Submit button uses a callback_id, which is wired up like so: app.view('callback_id', async () => {}). Not sure what other info would be needed beyond what's been mentioned above. I can provide a more detailed explanation with a code example if needed.

This was the workaround my team went with:
https://github.com/slackapi/bolt-js/issues/1073#issuecomment-903599111


setting joint limits

Hello all,
It is currently difficult to write to Joint limits. I suppose the only way available is if I change the Eigen::VectorXd elements available in Model class (lowerPositionLimit, upperPositionLimit ...), though it doesn't feel clean to do that
Is it possible to get a writable expression in these? Currently the visitor in joint-visitor.hpp returns only a readable value.
Thanks,
Rohan

You can access to this quantities in data via lowerPositionLimit and upperPositionLimit. They are both in read and write mode.

Thanks. I was mainly worried that changing limits might require some other changes as well.

Your welcome. I will close the issue.


Update README.md

After a conversation with the team, it was decided this required more time and thought. Closing this PR and will revisit at a later time.


Signing in with email provider (v4) fails with TypeError: getUserByEmail is not a function

Description 🐜
I'm trying to make NextAuth.js v4 work with the NextAuth Prisma adapter. As soon as I click the Sign in with Email button

I'm getting the following error:
TypeError: getUserByEmail is not a function

I'm testing it using the official next-auth-typescript-example repo and followed the tutorial available at https://next-auth.js.org/adapters/prisma to setup the database models. All required environments have been set in .env: NEXTAUTH_URL, EMAIL_SERVER, EMAIL_FROM, DATABASE_URL, SECRET
I think the issue is related to:
https://github.com/nextauthjs/next-auth/blob/a2c4046772d77754dffee1254e8321c263096537/src/server/routes/signin.js#L42
adapter variable is actually a function returning a Promise:
https://github.com/nextauthjs/adapters/blob/main/packages/prisma/src/index.ts#L6-L14
Shouldn't this Promise be resolved as in the main branch:
https://github.com/nextauthjs/next-auth/blob/main/src/server/routes/signin.js#L37-L40
or am I missing something ?
Is this a bug in your own project?
No
How to reproduce ☕
It's basically running the next-auth-typescript-example. The only bits of code I changed is:
diff --git a/pages/api/auth/[...nextauth].ts b/pages/api/auth/[...nextauth].ts
index 8f4a241..827dec3 100644
--- a/pages/api/auth/[...nextauth].ts
+++ b/pages/api/auth/[...nextauth].ts
@@ -7,9 +7,13 @@ import GithubProvider from "next-auth/providers/github"
 import GoogleProvider from "next-auth/providers/google"
 import TwitterProvider from "next-auth/providers/twitter"

+import { PrismaAdapter } from "@next-auth/prisma-adapter"
+import { PrismaClient } from '@prisma/client'
+const prisma = new PrismaClient()
 // For more information on each option (and a full list of options) go to
 // https://next-auth.js.org/configuration/options
 export default NextAuth({
+  adapter: PrismaAdapter(prisma),
   // https://next-auth.js.org/configuration/providers
   providers: [
     EmailProvider({

Screenshots / Logs 📽
Server Error
TypeError: getUserByEmail is not a function
This error happened while generating the page. Any console logs will be displayed in the terminal window.
Call Stack
Object.signin
node_modules/next-auth/server/routes/signin.js (51:0)
NextAuthHandler
node_modules/next-auth/server/index.js (202:0)
processTicksAndRejections
node:internal/process/task_queues (94:5)
async eval
node_modules/next-auth/server/index.js (251:0)
async Object.apiResolver
file:/next-auth-typescript-example/node_modules/next/dist/server/api-utils.js (101:9)
async DevServer.handleApiRequest
file:/next-auth-typescript-example/node_modules/next/dist/server/next-server.js (770:9)
async Object.fn
file:/next-auth-typescript-example/node_modules/next/dist/server/next-server.js (661:37)
async Router.execute
file:/next-auth-typescript-example/node_modules/next/dist/server/router.js (205:32)
async DevServer.run
file:/next-auth-typescript-example/node_modules/next/dist/server/next-server.js (841:29)
async DevServer.run
file:/next-auth-typescript-example/node_modules/next/dist/server/dev/next-dev-server.js (355:20)

Environment 🖥
System:
    OS: Linux 5.8 Ubuntu 20.04.2 LTS (Focal Fossa)
    CPU: (12) x64 Intel(R) Core(TM) i7-10850H CPU @ 2.70GHz
    Memory: 1.11 GB / 31.14 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 15.14.0 - ~/.nvm/versions/node/v15.14.0/bin/node
    Yarn: 1.22.10 - ~/.nvm/versions/node/v15.14.0/bin/yarn
    npm: 7.15.1 - /home/linuxbrew/.linuxbrew/bin/npm
  Browsers:
    Chrome: 91.0.4472.114
    Firefox: 89.0.2
  npmPackages:
    next: ^11.0.0 => 11.1.2
    next-auth: 4.0.0-beta.2 => 4.0.0-beta.2
    react: ^17.0.2 => 17.0.2
    @next-auth/prisma-adapter: ^0.5.4 => 0.5.4
    @prisma/client: ^3.0.2 => 3.0.2
    prisma: ^3.0.2 => 3.0.2

Contributing 🙌🏽
Yes,  I am willing to help solve this bug in a PR

check the migration guide https://next-auth.js.org/getting-started/upgrade-v4

I missed the warning section. From the migration guide, this solves the issue:
yarn add @next-auth/typeorm-legacy-adapter@next

Hi, I am still seeing this issue while trying to use the Prisma Adapter for postgres usage. I have gone through the migration guide and have the following dependencies installed:
"dependencies": {
"@next-auth/prisma-adapter": "^0.5.2-next.19",
"@next-auth/typeorm-legacy-adapter": "^0.1.2-next.19",
"@prisma/client": "^3.4.1",
"mongodb": "^4.1.4",
"next": "12.0.3",
"next-auth": "^4.0.0-beta.6",
"nodemailer": "^6.7.0",
"pg": "^8.7.1",
"react": "17.0.2",
"react-dom": "17.0.2"
},
I am wondering what I might be missing here.
Thanks!


implement new bib rule feature: AlternativeMapping

https://github.com/folio-org/mod-inventory/commit/5a328c8f4331d700d51283e1c16bac8fec538bac


Always auto name and create new workspaces from oldDot

@TomatoToaster pinging you for review since we discussed this PR.
Details
Removes the workspace/new page completely since we always want to auto name and create workspaces for N6.
Slack thread for more context, but in N6 we always want to auto name and create the workspace for the user, so the workspace/new page is no longer needed.
Also removed the success growl per this issue.
Fixed Issues

$ https://github.com/Expensify/Expensify/issues/173349
$ https://github.com/Expensify/Expensify/issues/173338
Tests
Tested through oldDot Inbox flow.

Log into an account on oldDot and show all hidden inbox cards
Find the inbox card below and select only Get Expensify Card then click Submit

Verify you are taken to /workspace/<policyId>/card

QA Steps
Same as tests
Tested On

[x] Web
[ ] Mobile Web
[ ] Desktop
[ ] iOS
[ ] Android

Web
https://user-images.githubusercontent.com/3387421/128938529-9ca25e13-5942-4c79-8bd6-1807b4693b1e.mov

Sorry Bondy for the pings, was trying to get pullerbear to pick someone else...

Ok @TomatoToaster HOLD removed and ready for one more review before it can be merged.

Self merging since tests are passing and this is approved.

🚀 Deployed to staging by @timszot in version: 1.0.83-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
cancelled 🔪

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by @isagoico in version: 1.0.85-9 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Undefined method reload_server_js_every_request

Nice work on the 1.0 release guys. Really appreaciate the work you guys have done to make running React and Rails easier.
We're currently running into an issue with the generator where it gives the following config option but it doesn't appear to be defined anywhere.
config.reload_server_js_every_request = Rails.env.development?

Should this be the following instead?
config.development_mode = Rails.env.development?

I just got the same error minutes ago.

Thanks for the heads up.

about to push 1.0.1 which will fix this.

Cheers @justin808

Fixed!


It would be nice to filter by the existence of a video

We have video urls in the dataset - and also after import from JSON.
Clicking the video filter empties the map. It does not match with anything.
Debugging this when I have time.

Works.


[Suggestion] Private Rooms and Voice Chats

So what about having the option for private rooms where the creator decides on a password and anyone with the password can access the room. In addition since the mozilla program persona has been shut down it might be best to just do something similar to Candid where your id will be a serious of words or names of animals.
As for voice chat there is a very good WebRTC powered application https://github.com/mikeal/roll-call that could be easily implemented into the program. It works off of a room based protocol as well so you can assign the room of the voice channel to match that of the share space.

Hi have been looking for others interesting in hosting files...
I run a 12TB server now & a good VPS to help/play around with..
I also been admin on private trackers... http://imgur.com/a/p2YtR


Deployment and production docs

Expands the documentation with:

Deployment instructions up to date with the new https://www.npmjs.com/package/vite-plugin-imba
Production advice for PM2
Split between full stack and static site builds

Reads well to me


'az ad app list --display-name' uses wildcard instead of exact match

Related command
az ad app list --display-name 'MYAPP'
Describe the bug
When multiple apps/service principals with similar names are present like: MYAPP, MYAPP2, MYAPP3 multiple apps are returned when running the command mentioned
To Reproduce
When running the command az ad app list --display-name 'MYAPP' returns all the apps mentioned above (like a wildcard)
Expected behavior
I expect the '--display-name' argument to behave like an exact match operator
Environment summary
apt-get / 2.37.0 / Linux (Debian-based) / bash -> pwsh
Additional context
Workaround is available, but is somewhat cumbersome: use the filter argument: az ad app list --filter "displayname eq 'MYAPP'"

@jiasli for awareness

This logic of listing with --display-name as prefix has been there since 2016-07-29:
https://github.com/Azure/azure-cli/blob/33cbd01f75c7d4c3814de5a1cbf6f42de7890467/src/azure-cli/azure/cli/command_modules/role/custom.py#L748-L749
https://github.com/Azure/azure-cli/blame/33cbd01f75c7d4c3814de5a1cbf6f42de7890467/src/azure-cli/azure/cli/command_modules/role/custom.py#L748-L749

I am not sure if changing the behavior is a good choice...

it feels illogical to return more than one object when specifying --display-name, don't you agree?

Even though when creating an app, Azure CLI checks if there is an existing app with the specified --display-name:
https://github.com/Azure/azure-cli/blob/33cbd01f75c7d4c3814de5a1cbf6f42de7890467/src/azure-cli/azure/cli/command_modules/role/custom.py#L617-L627
The truth is displayName is not an identifier in Graph service and you may have multiple apps with the same display name!
> az ad app list --display-name myapp1 --output table
DisplayName    Id                                    AppId                                 CreatedDateTime
-------------  ------------------------------------  ------------------------------------  --------------------
myapp1         5607c536-27be-4e5b-97b9-65afaa553bd5  285149de-9e22-4410-85b9-38b2d2c0553d  2022-06-30T03:38:01Z
myapp1         b3781aac-6ee1-4e12-88e2-efdb9f01fd0e  8700fdad-f6ab-4d38-9909-7bae2c62cf31  2022-06-30T03:38:44Z

So my recommendation is to always use appId or id to uniquely identify your application.

The truth is displayName is not an identifier in Graph service and you may have multiple apps with the same display name!

@jiasli, Cool, that's very clear. Thanks! Closing this issue


More reliable native loading

This finally resolves some lingering compatibility issues with alternate classloaders that my fork handles correctly. Once this is merged, I will deprecate my fork since all functionality will be included here.
It also removes the dependency on JNA, opting instead to simply check the results of System.mapLibraryName.

I see, however currently (as of 9.1) Java distribution is limited to the three cases I implemented. Additionally, the current solution is still limited by JNA support: https://github.com/java-native-access/jna/issues/1309.
I will see how JNA and LWJGL bootstrap their native libraries and try to emulate that, since they seem to be the best-supported/most popular Java libraries that bundle native code.

May fix https://github.com/google/or-tools/issues/2621

Most likely, this will never been merged.


Don't set progressView to null

progressView is intended for reuse so don't set it to null.
See the comment at https://github.com/turbolinks/turbolinks-android/blob/a2c89a4abfcfed75c68a5b8c8ded5c1d4cd749bd/turbolinks/src/main/java/com/basecamp/turbolinks/TurbolinksSession.java#L755
Currently, the progressView must be configured before every visit or the default progressView settings are used. This change fixed that problem.
For example:
TurbolinksSession.getDefault(this).progressView(LayoutInflater.from(this).inflate(com.basecamp.turbolinks.R.layout.turbolinks_progress, turbolinksView, false), com.basecamp.turbolinks.R.id.turbolinks_default_progress_indicator,Integer.MAX_VALUE);
TurbolinksSession.getDefault(this).visit(locationA);
TurbolinksSession.getDefault(this).visit(locationB);

Currently, that will use the customized settings for visiting locationA but the default progress view (including the default delay) for visiting locationB. This behavior seems incorrect and surprising.

@lateplate any thoughts on this?

bump

bump


How to send a message with url link preview?

It is possible to send a url link and the recipient receives the render url preview?
In Whastsapp API: "preview_url": false | true
Thanks and regards!

I believe there is no way for that, this happened on the device!

here is an example of how this can be done https://github.com/Rhymen/go-whatsapp/issues/370


Headers parser now supports multi-segment buffers

I went back to the original implementation using vectorized IndexOf. Initially I did not want to do it because I thought it would not be best for ReadOnlyBytes, but then it turns out it works quite well. The bonus is that now the implementation is very similar to the original implementation.
I added some handler overloads taking by ref handlers. This allows handlers to be structs.
All tests from https://github.com/aspnet/KestrelHttpServer/blob/200d8debc005bac2c15424b20c6b7bb4a50483cc/test/Microsoft.AspNetCore.Server.KestrelTests/HttpParserTests.cs except for skipped ParseHeadersConsumesBytesCorrectlyAtEnd test and logging test (logging is not supported) are passing.
The skipped test is skipped because the semantics it tries to enforce are very strange. The parsing routine fails (returns false) yet the tests wants the parser to return non-zero consumedBytes.
The current perf results are pretty good. "Suffix "Rb" means ReadableBuffer, "Rob" means ReadOnlyBytes", and "Ref" means handler struct passed by ref.
 Test Name                         | Metric                | Iterations |    AVERAGE |    STDEV.S |        MIN |        MAX
:--------------------------------- |:--------------------- |:----------:| ----------:| ----------:| ----------:| ----------:
 HttpParserBench.FullRequestLegacy | Duration              |    101     |     13.542 |      3.466 |     12.616 |     47.936
 HttpParserBench.FullRequestLegacy | Instructions Retired  |    101     | 8.944E+007 | 7.293E+006 | 8.850E+007 | 1.620E+008
 HttpParserBench.FullRequestLegacy | Branch Mispredictions |    101     |  11152.475 |  87817.168 |      0.000 | 8.847E+005
 HttpParserBench.FullRequestLegacy | Cache Misses          |    101     |   7380.911 |  31870.038 |      0.000 | 3.236E+005
 HttpParserBench.FullRequestRb     | Duration              |    101     |     14.906 |      1.142 |     14.225 |     25.685
 HttpParserBench.FullRequestRb     | Instructions Retired  |    101     | 1.462E+008 | 4.444E+006 | 1.456E+008 | 1.904E+008
 HttpParserBench.FullRequestRb     | Branch Mispredictions |    101     |   8597.545 |  32944.192 |   4096.000 | 3.359E+005
 HttpParserBench.FullRequestRb     | Cache Misses          |    101     |   7340.356 |  19205.976 |      0.000 | 1.966E+005
 HttpParserBench.FullRequestRob    | Duration              |    101     |     11.449 |      1.016 |     10.570 |     19.461
 HttpParserBench.FullRequestRob    | Instructions Retired  |    101     | 1.121E+008 | 4.019E+006 | 1.115E+008 | 1.521E+008
 HttpParserBench.FullRequestRob    | Branch Mispredictions |    101     |   5637.069 |  27954.121 |      0.000 | 2.826E+005
 HttpParserBench.FullRequestRob    | Cache Misses          |    101     |   9327.525 |  23771.758 |      0.000 | 2.417E+005
 HttpParserBench.HeadersRb         | Duration              |    101     |     19.093 |      0.387 |     18.369 |     20.433
 HttpParserBench.HeadersRb         | Instructions Retired  |    101     | 2.154E+008 |  99980.196 | 2.152E+008 | 2.156E+008
 HttpParserBench.HeadersRb         | Branch Mispredictions |    101     |  15167.366 |   1968.174 |  12288.000 |  20480.000
 HttpParserBench.HeadersRb         | Cache Misses          |    101     |   7259.248 |   2830.759 |   4096.000 |  16384.000
 HttpParserBench.HeadersRob        | Duration              |    101     |     14.984 |      2.853 |     13.532 |     41.352
 HttpParserBench.HeadersRob        | Instructions Retired  |    101     | 1.702E+008 | 3.744E+006 | 1.695E+008 | 2.073E+008
 HttpParserBench.HeadersRob        | Branch Mispredictions |    101     |   7259.248 |  26181.619 |      0.000 | 2.662E+005
 HttpParserBench.HeadersRob        | Cache Misses          |    101     |  10138.614 |  18414.644 |   4096.000 | 1.843E+005
 HttpParserBench.HeadersRobRef     | Duration              |    101     |     13.530 |      0.606 |     12.602 |     16.314
 HttpParserBench.HeadersRobRef     | Instructions Retired  |    101     | 1.601E+008 | 1.101E+005 | 1.599E+008 | 1.608E+008
 HttpParserBench.HeadersRobRef     | Branch Mispredictions |    101     |   4298.772 |   2118.566 |      0.000 |  16384.000
 HttpParserBench.HeadersRobRef     | Cache Misses          |    101     |   6448.158 |   3679.409 |   4096.000 |  20480.000
 HttpParserBench.RequestLineRb     | Duration              |    101     |      8.992 |      0.604 |      8.176 |     12.394
 HttpParserBench.RequestLineRb     | Instructions Retired  |    101     | 7.180E+007 | 1.461E+006 | 7.130E+007 | 8.630E+007
 HttpParserBench.RequestLineRb     | Branch Mispredictions |    101     |   5150.416 |  17699.777 |      0.000 | 1.802E+005
 HttpParserBench.RequestLineRb     | Cache Misses          |    101     |   5434.297 |   5216.861 |      0.000 |  49152.000
 HttpParserBench.RequestLineRob    | Duration              |    101     |      8.064 |      1.015 |      7.289 |     15.555
 HttpParserBench.RequestLineRob    | Instructions Retired  |    101     | 5.745E+007 | 3.204E+006 | 5.700E+007 | 8.930E+007
 HttpParserBench.RequestLineRob    | Branch Mispredictions |    101     |   6813.149 |  31120.314 |      0.000 | 3.154E+005
 HttpParserBench.RequestLineRob    | Cache Misses          |    101     |   6732.040 |  17315.805 |      0.000 | 1.720E+005

Up the iterations? 101 seems small?

e.g. Legacy has a high max which will pull up the average, not sure the benchmark discards the jit

It's actually 101 * 10K * unrolled loop (~10) = ~10M parses. i.e. The 101 is from "outer iterations"

@dotnet-bot test this please


Is Android platform supported?????

i found,when i use it on android,it must be crash

Yes, Android is supported. It is tested on each commit in CI.

Hello, do i need specific features to be enabled

openssl is missing for me


CSS EASY

Pull Request Type
What kind of change does this PR introduce?
Solved an issue/task
What is the current behavior?
Added red color
Issue Number: [#1595]
What is the new behavior?
Added red color

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out our forkcommitmerge.io website repository. The repository contain real issues that you can help to resolve or create some of your own if you see any bugs or want to add new features to the site, etc. You can also check out the Influences section in the README to find more projects similar to this one.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!


Fix #63. Add --input-meta parameter to explicitly specify the jsonl field dtypes

When reading jsonl files with Dask, the dataframe datatypes are inferred unless explicitly specified.
Inferring the data types can lead to several issues, such as incorrect type inference, degradation of performance and increased memory usage among others.
I think we could mitigate those issues if we would add a --input-meta parameter, which would receive a dictionary of datatypes.
That parameter would be optional, and be similar to the --meta parameter available here: https://docs.dask.org/en/latest/generated/dask.dataframe.read_json.html.

After sleeping on it, I do have one last nit. I think the argument for all the read_* functions should be meta. The argparse arguments can still be --input-meta. I want to try and keep the arguments and behavior as close to Dask as possible.

After sleeping on it, I do have one more nit. I think the argument for all the read_* functions should be meta. The argparse arguments can still be --input-meta. I want to try and keep the arguments and behavior as close to Dask as possible.

Hi @ryantwolf , thank you for all your feedback.
I am addressing all the comments you have made. My first thought about the name of the parameter was to name it meta, but then I thought that, in the near future, we may want to also specify the output-meta parameter, where we may want to specify specific formats for the output files.
Even if I think it is very likely that meta might work for both use-cases, I thought it would be clearer to differentiate them.
Looking forward to your thoughts. Thanks!!!

Thanks for the changes! Left a few suggestions, but generally looks good.
In addition to the changes, is it also possible to add a couple of tests, that attempt to use DocumentDataset.read_json with the input_meta param set both as a string and a dict, and verify that the result dtypes are what we'd expect.

I have just added a test_io.py file to start incorporating IO tests in that file.


& appears as & in next/previous episode links

Ampersands are not displayed correctly in the navigation links to next/previous episode pages, appearing instead as "&". See https://librarycarpentry.org/lc-sql/04-ordering-commenting.html for an example, where the link to the next episode appears as "Aggregating &..."

Thank you for opening this. It is definitely a bug. I'll see what I can do.

I was going through old issues and I realize this is a bug from {varnish}, not {sandpaper}. Specifically, this is caused by the Mustache templating escaping values.
So any place that contains {{forward_title}} or {{back_title}} needs to be changed to either include an ampersand or triple curlies (see https://mustache.github.io/mustache.5.html)

Thanks for raising this @tobyhodges ! @zkamvar and I went through this today and I've added the triple curly braces fix (e.g. {{{forward_title}}}) to not escape characters in the navigation titles. This fix will be in the upcoming varnish 0.3.2 release.

Just a note, Rob created the release 20 minutes ago and it is now live on the R universe: https://carpentries.r-universe.dev/varnish


Update webhook processor

Add sync webhook handling

@estepan thanks for this. That sync hook definition is untidily non-standard...whatever!
Merging now..

@tardate thank you!

@estepan np! btw, if possible, it would be great if you could contribute some (real) "sample" payloads - just send them in another P/R if you can (redacted as you wish).
The existing files in spec/fixtures/webhook_examples/sync_blacklist.json,sync_whitelist.json are ones I just "made up" based on the API docs. But shouldn't really assume the API docs are 100% correct.

@tardate np. As soon as I get this feature tested in my staging env.


Update hosted

Bringing updates on changelogs and minor fixes.

Once I am on it, I 'll wait for #1436 too


Replaced bootstrap-tour with introJs tour library in Sprint Math Activity

I have migrated Sprint Math activity tutorial from bootstrap-tour to IntroJs
Issue: https://github.com/llaske/sugarizer/issues/1090

Nice. Thanks.


Translatable ignore casts

Version information

Laravel: v5.8.30
Voyager: v1.2.6
PHP: 7.3.7
Database: MariaDB 10.4.6

Description
Translatable trait does not handle casts
If we have a column that has a casts set for it, it is not casted after translation is loaded
Steps To Reproduce
Steps to reproduce the behavior:

create a model with at least one text field.
set protected $casts = ['field' => 'array']; on the model.
add use Translatable; trait.
Translate model $model = $model->translate(app()->getLocale(), 'en').

Expected behavior
dd($model->field), expected array, received string.
I will try to PR this.

+1
Any idea for a workaround?


What is the status of this project?

@pyykkis ,
Can we get an official statement on the status of this project? There has not been any activity for sometime.  I realize that available time and interests change; I am just looking to understand what the future holds for this project.
A few specific questions...

Do the maintainers just not have time for this project?
Do they not see project this as a useful tool anymore?
Is there a popular fork that is taking over new features/bug fixes?

There is also a similar question Google Groups here:
https://groups.google.com/forum/#!topic/transparencyjs/qIjEfdHkQ4w
This is not meant to be a demanding message. I thank all the maintainers for a great project!

Hi all,
The project is coming alive again. @rikukissa volunteered to be another maintainer, and we are looking for others. Anyone with accepted pull request will get commit access.
There's one urgent issue, #130, otherwise I believe development will just focus on occasional bug fixes.
I have some plans for larger composition of GUI libraries, borrowing some ideas from React.js, but looking for more simple API and internal implementation. However, I'm currently focusing on completely different domain, and not planning to do any significant MV* library development in the next 12 months or so.

Also, the project is looking for new maintainers: https://github.com/leonidas/transparency/blob/master/README.md#community
Let me know, if anyone is interested. Existing fork and further development is a bonus.

@pyykkis I would love to be a maintainer, but I would end up rewriting it in a functional approach. :cry:


[WB-5745]: Launch - better error handling and UX

https://wandb.atlassian.net/browse/WB-5745
Description
Adds better error messages for several api calls, shows the docker steps while building the docker container.
Testing
Tested by breaking stuff on purpose along launch and launch-agent workflows

Great idea Chris! There's still a bit more to be done here. I want to add handling for attempting to push to projects you don't have access to, and handle docker client issues more cleanly.


Not getting date/time on console log

I have tried setting CA to all combinations of development/production, debug/not and in no case do I end up seeing date/time stamps in the console log. What am I doing wrong here? Thanks

CA itself does (very) simple print statement logging, no additional information is automatically added. When running as a service, the systemd service provides the time-stamping, etc. That's why when viewing with jounalctl, you get time-stamps.

Thanks. That explains what I see perfectly. On my own CA install, I can run via systemd. On another recent install for a friend, I am running a chroot'ed Linux on Android and there is no systemd support - only sysv. And there is where I was not seeing the date/time stamps. Sorry for the bother...

I solved this problem outside of callattendant by using a classic Unix utility called 'ts' that prepends a date stamp to all records of output. See:
https://github.com/roycewilliams/callattendant-resources/blob/main/run-with-logging.sh

I solved this problem outside of callattendant by using a classic Unix utility called 'ts' that prepends a date stamp to all records of output. See:
https://github.com/roycewilliams/callattendant-resources/blob/main/run-with-logging.sh

That is freaking fantastic, Royce! I had to apt-get install moreutils to get ts but that wasn't too hard once I discovered that is where the command lives. Thanks so much! Wow!

@whitedavidp Great! And I've also added a comment to the script to help folks locate ts faster in the future - thanks for the nudge! :D

'ts' is usually pare of the 'moreutils' package.


Only append inline handlers for an element once

We set the raw event body to null if compiling the source fails,
which previously led to us re-appending when we set another inline
attribute.
Fixes #1948.

Re event-handler-spec-example:
eventHandlerArgCoercion is boxing the primitives to null, which then causes the handler to not get appended and so the ordering is wrong. Haven't checked the spec yet if we should be doing that this way.

Okay, fixed. eventHandlerArgCoercion wasn't at fault, I just got confused with the test failures.
Basically, when accessing the IDL attribute (el.onclick), we'd compile. If that failed, we'd set the internal eventHandlers tracker to null, thereby allowing scripts to re-add the inline handler in the handler list.

Do you see a way to do this without an additional Set, e.g. using in checks or undefined?
If not, LGTM and feel free to merge :)

No, sadly has to be this way since we only want to mark in cases where handler !== null, but _eventHandlers[event] is always set.


Form in dialog doesn't send the Request.

Hello,
i have a little Problem.
so thats my Code:
    <Dialog open={open} onOpenChange={setOpen}>
      <Form {...form}>
        <form onSubmit={form.handleSubmit(onSubmit)}>
          <DialogContent className="sm:max-w-[425px]">
            <DialogHeader>
              <DialogDescription>
                Make changes to your profile here. Click save when youre done.
              </DialogDescription>
            </DialogHeader>

            <FormField
              control={form.control}
              name="full_name"
              render={({ field }) => (
                <FormItem>
                  <FormLabel>Name</FormLabel>
                  <FormControl>
                    <Input placeholder="Name" {...field} />
                  </FormControl>
                  <FormMessage />
                </FormItem>
              )}
            />
            <DialogFooter>
              <Button type="submit">Submit</Button>
            </DialogFooter>
          </DialogContent>
        </form>
      </Form>
    </Dialog>

That looks like

The Problem now is, that the Form doesnt send the Request. It should be, or am i wrong ?
When i move the <Form> into the <DialogContent> the Form works but the styles are wrong

I have a similar setup, but I've separated the Form into its own component and nested it into the Dialog as shown below:
"use client"

/* a bunch of imports you don't care about */

export function TableDialogCustom() {

  return (
    <Dialog>
      <DialogTrigger asChild>
        <Button variant="outline">Add Table</Button>
      </DialogTrigger>
      <DialogContent className="sm:max-w-[425px]">
        <DialogHeader>
          <DialogTitle>Add a Table</DialogTitle>
          <DialogDescription>
            Add a table name and a read-only API key from AirTable
          </DialogDescription>
        </DialogHeader>

            <TableForm />

      </DialogContent>
    </Dialog>
  )
}

"use client"

/* a bunch of imports you don't care about */

export function TableForm() {

    /* a bunch of resolver/onclick stuff you don't care about */

    return (
        <Form {...form}>
            <form onSubmit={form.handleSubmit(onSubmit)} className="space-y-8">
            <FormField
                control={form.control}
                name="table_name"
                render={({ field }) => (
                <FormItem>
                    <FormLabel>Username</FormLabel>
                    <FormControl>
                        <Input placeholder="Table Name" {...field} />
                    </FormControl>
                    <FormDescription>
                    Enter your table name here.
                    </FormDescription>
                    <FormMessage />

                </FormItem>

                )}
            />
            <FormField
                control={form.control}
                name="api_key"
                render={({ field }) => (
                <FormItem>
                    <FormLabel>API Key</FormLabel>
                    <FormControl>
                        <Input placeholder="API Key" {...field} />
                    </FormControl>
                    <FormDescription>
                    Enter your API Key here.
                    </FormDescription>
                    <FormMessage />

                </FormItem>

                )}
            />
            <Button type="submit">Submit</Button>
            </form>
        </Form>
        )
}

It ends up looking like this:

same error

@daddotmn
use button onClick  and dispatch submit event with bubbles true
  <Form {...form}>
          <form ref={formRef} onSubmit={form.handleSubmit(onSubmit)} className="space-y-8">
              ...
          </form>
  </Form
  ...
  <Button
    onClick={() => {
      if (formRef.current) {
        formRef.current.dispatchEvent(new Event('submit', { bubbles: true }));
      }
    }}
  >
    Continue
  </Button>

@daddotmn use button onClick and dispatch submit event with bubbles true
  <Form {...form}>
          <form ref={formRef} onSubmit={form.handleSubmit(onSubmit)} className="space-y-8">
              ...
          </form>
  </Form>
  ...
  <Button
    onClick={() => {
      if (formRef.current) {
        formRef.current.dispatchEvent(new Event('submit', { bubbles: true }));
      }
    }}
  >
    Continue
  </Button>

This works fine... but this should work without this workaround.

If you are rendering the form outside the Dialog.Content, what is happening is that the button is being portaled to the body and as it is not inside the form element the submit will not work. what you can do is:

Move the form into Dialog.Content
Use the form attribute on the submit button

what to do if in case we have a long form containing various fields..
in my case the dialog just scatter height wise due to large no. of fields. i somehow want to adjust the dialog on the screen and scroll the form fields.
note: scrollarea isn't working at all in this case.

@daddotmn use button onClick and dispatch submit event with bubbles true
  <Form {...form}>
          <form ref={formRef} onSubmit={form.handleSubmit(onSubmit)} className="space-y-8">
              ...
          </form>
  </Form>
  ...
  <Button
    onClick={() => {
      if (formRef.current) {
        formRef.current.dispatchEvent(new Event('submit', { bubbles: true }));
      }
    }}
  >
    Continue
  </Button>

even this doesn't work for me. anybody has a solution for this?

I found this: https://github.com/react-hook-form/react-hook-form/issues/566#issuecomment-612328736
There seem to be several solutions.

If you have access to handleSubmit() function in the component which includes your submit button:  invoke it directly handleSubmit(onSubmit)(). this seems easiest and solved my problem.
You can set an id on your <form id="my-form" >, and add this id to the form attribute of your submit button: .

However option 2 triggered a full page refresh/rerender so it didn't work for me..

To resolve this I moved the <Form {...form}/> component to wrap the entire <Dialog> component and placed the submit button inside the <DialogContent>.
Here's the code:
const formSchema = z.object({
  is_business: z.boolean().default(false),
  // more schema here...
});

export default function NewCxDialog({ open, onOpenChange }) {
  const { handleSubmit, control, ...form } = useForm({
    resolver: zodResolver(formSchema),
    defaultValues: {
      is_business: false,
     // default values here...
    },
  });

  function onSubmit(e) {
    function closeDialog() {
      onOpenChange(false);
    }

    const submitData = async (e) => {
      try {
        const response = await fetch("/api/new/cx", {
          method: "POST",
          cache: "no-store",
          body: JSON.stringify(e),
          headers: {
            "Content-Type": "application/json",
          },
        });
      } catch (error) {
        throw error;
      }
    };

    // I use sonner for toasts
    toast.promise(submitData(), {
      loading: "Cargando...",
      success: () => {
        router.refresh();
        closeDialog();
        return "Cliente Creado Exitosamente";
      },
      error: (e) => {
        console.error(e);
        return "Hubo un error. Intenta nuevamente.";
      },
    });
  }

  return (
    <Form {...form}>
      <Dialog
        open={open}
        onOpenChange={() => {
          form.reset();
          onOpenChange();
        }}
      >
        <DialogContent className="max-w-2xl">
          <form onSubmit={handleSubmit(onSubmit)}>
            <DialogHeader>
              <DialogTitle className="!text-primary">
                Crear Nuevo Cliente
              </DialogTitle>
              <DialogDescription>
                Llena el formulario con la información de tu cliente.
              </DialogDescription>
            </DialogHeader>

                <FormField
                  control={control}
                  name="first_name"
                  render={({ field }) => (
                    <FormItem>
                      <FormLabel>Nombre</FormLabel>
                      <FormControl>
                        <Input {...field} />
                      </FormControl>
                      <FormMessage />
                    </FormItem>
                  )}
                />
                <FormField
                  control={control}
                  name="last_name"
                  render={({ field }) => (
                    <FormItem>
                      <FormLabel>Apellido</FormLabel>
                      <FormControl>
                        <Input {...field} />
                      </FormControl>
                      <FormMessage />
                    </FormItem>
                  )}
                />
               // more code here...

            <DialogFooter>
              <Button type="submit">Crear Cliente</Button>
            </DialogFooter>
          </form>
        </DialogContent>
      </Dialog>
    </Form>
  );
}

If you are rendering the form outside the Dialog.Content, what is happening is that the button is being portaled to the body and as it is not inside the form element the submit will not work. What you can do is:

Move the form into Dialog.Content
Use the form attribute on the submit button

Cleanest explanation. Works as expected now.

If you are rendering the form outside the Dialog.Content, what is happening is that the button is being portaled to the body and as it is not inside the form element the submit will not work. What you can do is:

Move the form into Dialog.Content
Use the form attribute on the submit button

Cleanest explanation. Works as expected now. Ty @joaom00

It's not working

To resolve this I moved the <Form {...form}/> component to wrap the entire <Dialog> component and placed the submit button inside the <DialogContent>.
Here's the code:
const formSchema = z.object({
  is_business: z.boolean().default(false),
  // more schema here...
});

export default function NewCxDialog({ open, onOpenChange }) {
  const { handleSubmit, control, ...form } = useForm({
    resolver: zodResolver(formSchema),
    defaultValues: {
      is_business: false,
     // default values here...
    },
  });

  function onSubmit(e) {
    function closeDialog() {
      onOpenChange(false);
    }

    const submitData = async (e) => {
      try {
        const response = await fetch("/api/new/cx", {
          method: "POST",
          cache: "no-store",
          body: JSON.stringify(e),
          headers: {
            "Content-Type": "application/json",
          },
        });
      } catch (error) {
        throw error;
      }
    };

    // I use sonner for toasts
    toast.promise(submitData(), {
      loading: "Cargando...",
      success: () => {
        router.refresh();
        closeDialog();
        return "Cliente Creado Exitosamente";
      },
      error: (e) => {
        console.error(e);
        return "Hubo un error. Intenta nuevamente.";
      },
    });
  }

  return (
    <Form {...form}>
      <Dialog
        open={open}
        onOpenChange={() => {
          form.reset();
          onOpenChange();
        }}
      >
        <DialogContent className="max-w-2xl">
          <form onSubmit={handleSubmit(onSubmit)}>
            <DialogHeader>
              <DialogTitle className="!text-primary">
                Crear Nuevo Cliente
              </DialogTitle>
              <DialogDescription>
                Llena el formulario con la información de tu cliente.
              </DialogDescription>
            </DialogHeader>

                <FormField
                  control={control}
                  name="first_name"
                  render={({ field }) => (
                    <FormItem>
                      <FormLabel>Nombre</FormLabel>
                      <FormControl>
                        <Input {...field} />
                      </FormControl>
                      <FormMessage />
                    </FormItem>
                  )}
                />
                <FormField
                  control={control}
                  name="last_name"
                  render={({ field }) => (
                    <FormItem>
                      <FormLabel>Apellido</FormLabel>
                      <FormControl>
                        <Input {...field} />
                      </FormControl>
                      <FormMessage />
                    </FormItem>
                  )}
                />
               // more code here...

            <DialogFooter>
              <Button type="submit">Crear Cliente</Button>
            </DialogFooter>
          </form>
        </DialogContent>
      </Dialog>
    </Form>
  );
}

Doesn't this render an empty form in place until the Dialog renders a Portal?

IF YOU ARE USING ANY KIND OF FORM RESOLVER:
Apart from this above solutions on form there might be issue in your zod schema.If you forgot to add an required field zod schema in the form then there would'nt be any error in form but internally zod stop you from submitting the form.

IF YOU ARE USING ANY KIND OF FORM RESOLVER: Apart from this above solutions on form there might be issue in your zod schema.If you forgot to add an required field zod schema in the form then there would'nt be any error in form but internally zod stop you from submitting the form.

This solution works for me. Thank you @Yogesh070

2. form="my-form"

Thank you! Solved it, there is no need to wrap around Dialog box. There was a problem with zod resolvers in my case and that fixed the problem.

@kgaurav152 did ya manage to solve that issue?

Worked for me too. i was not having an input component for a schema field and that's why it was invalid every time i submitted the form but i wasn't getting any error as i didn't have registered that schema field with any input component.
after making that schema field optional, i got it working.
Thanks everyone.

I faced the same issue myself, what I did is I wrapped the  with my  component and separated my  into a separate component
`<Form {...form}>

 // This is where my form lies (you can easily infer type with Zod from the schema)
 <ApplicationForm form={form} />

`

I encountered the same issue. moved from using  to using useForm handke submit function
  return (
    <Dialog>
      <DialogTrigger asChild>
        <button className="w-full text-start">Edit</button>
      </DialogTrigger>
      <DialogContent>
        <DialogHeader>
          <DialogTitle>Edit tag</DialogTitle>
          <DialogDescription>Edit tag information</DialogDescription>
          Name
          <Input
            placeholder="Birthday"
            id="name"
            type="text"
            {...register("name", {
              required: { message: "Tag name is required", value: true },
              maxLength: {
                value: 30,
                message: "Tag Name cannot be grater than 30",
              },
            })}
          />
        </DialogHeader>
        <DialogFooter>
          <Button
            type="button"
            onClick={handleSubmit(handleEditTag)}
          >
            Update
          </Button>
        </DialogFooter>
      </DialogContent>
    </Dialog>
  );

Same issue with form not firing submit event when inside a Dialog:
Changed from this :
       <form onSubmit={submitData}>   ---> from here
       <Dialog>
       <DialogTrigger asChild>
       <Button variant="outline">Add New Item</Button>
       </DialogTrigger>
      <DialogContent className="sm:max-w-[500px] w-[700px] ">

      ....

To this :

      <Dialog>
      <DialogTrigger asChild>
      <Button variant="outline">Add New Item</Button>
      </DialogTrigger>
      <DialogContent className="sm:max-w-[500px] w-[700px] ">
      <form onSubmit={submitData}>    ----> to here
       ....

<Button onClick={async (e) => {
          e.preventDefault();
	  const values = form.getValues(); // we can get form values like this
          const res = await updateFn(values).unwrap();
	  if (res) {
               toast.success('Successfully updated your data');
          }
          }}
>
{isLoading ? 'Saving Changes' : 'Save Changes'}
</Button>

Please follow the method below to solve the problem.
<Dialog onOpenChange={setOpen} open={open}>
       <DialogContent>

                <DialogHeader>
                  <DialogTitle>
                    Are you absolutely sure to reject the request?
                  </DialogTitle>
                  <DialogDescription>
                    This action cannot be undone. This will permanently delete
                    your account and remove your data from our servers.
                  </DialogDescription>
                </DialogHeader>
                <Form {...form}>
                  <form onSubmit={form.handleSubmit(onSubmit)} className="space-y-12">
                    <fieldset >
                      <FormField
                        control={form.control}
                        name="rejectComment"
                        render={({ field }) => {
                          return (
                            <FormItem>
                              <FormLabel>Reject comment</FormLabel>
                              <FormControl>
                                <Input placeholder="Reject comment" {...field} />
                              </FormControl>

                              <FormMessage />
                            </FormItem>
                          )
                        }}
                      />
                      <DialogFooter>
                        <Button className="my-2" type="submit">Save changes</Button>
                      </DialogFooter>
                    </fieldset>
                  </form>
                </Form>

              </DialogContent>
 </Dialog>

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.


[fix] Fix scroll on newer versions of Chrome (>=61) + remove unused code

Newer versions of Chrome use the same way of Firefox to handle scrolling.
Also remove some trailing spaces.

Good to hear are still alive man!  Hi from me and Peter

From: Egil Möller<EMAIL_ADDRESS>Sent: Monday, 25 June 2018 9:05 am
To: redhog/ep_cursortrace
Cc: Subscribed
Subject: Re: [redhog/ep_cursortrace] [fix] Fix scroll on newer versions of Chrome (>=61) + remove unused code (#13)
Merged #13https://github.com/redhog/ep_cursortrace/pull/13.

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/redhog/ep_cursortrace/pull/13#event-1698263296, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AANewAxFOoR7Zxhuk2s_qzcaAAr0tBEyks5uAJphgaJpZM4Uyemn.

Heyas! Sure I'm alive :) Say hi to Peter! We should meet up again some time! I'm however living near the north pole nowdays - https://www.google.com/maps/place/Tromsø/@69.6652941,18.8477109,12z/data=!3m1!4b1!4m5!3m4!1s0x45c4c4526c3b71fd:0x23dca858e6ebed3!8m2!3d69.6492047!4d18.9553238

Bump me through an email, john dot mclear dot co dot uk and we can organize a meet!
Secret, Proprietary & Confidential
This electronic message transmission contains information which is proprietary and confidential. The information is intended solely for the intended recipient, and use by any other party is not authorized.

From: Egil Möller<EMAIL_ADDRESS>Sent: 25 June 2018 11:47
To: redhog/ep_cursortrace
Cc: John McLear; Comment
Subject: Re: [redhog/ep_cursortrace] [fix] Fix scroll on newer versions of Chrome (>=61) + remove unused code (#13)
Heyas! Sure I'm alive :) Say hi to Peter! We should meet up again some time! I'm however living near the north pole nowdays - https://www.google.com/maps/place/Tromsø/@69.6652941,18.8477109,12z/data=!3m1!4b1!4m5!3m4!1s0x45c4c4526c3b71fd:0x23dca858e6ebed3!8m2!3d69.6492047!4d18.9553238

You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/redhog/ep_cursortrace/pull/13#issuecomment-399910292, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AANewCvLF4bcWOeDQfwH7NT5NSWR_Ikkks5uAL-mgaJpZM4Uyemn.


fixed React.PropTypes deprecation warning

Fixes #39.
Warning: Accessing PropTypes via the main React package is deprecated. Use the prop-types package from npm instead.
From https://facebook.github.io/react/docs/typechecking-with-proptypes.html:

Note: React.PropTypes is deprecated as of React v15.5. Please use the prop-types library instead.

Thanks!


Implement draft-06 changes

[x] -1. Add draft-06 tests

[ ] 0. Use $schema keyword to identify the version of a used specification

[ ] 1. Check and change if necesarry if boolean values could be a valid schema

Boolean values are equivalent to the following behaviors:
 true  Always passes validation, as if the empty schema {} |
 false  Always fails validation, as if the schema { "not":{} }

[ ] 2. Optionally check for $schema in the root, and warn about presence in subschemas

The "$schema" keyword SHOULD be used in a root schema.  It MUST NOT appear in subschemas.

[ ] 3. Use $id instead of id

9.2.  The "$id" keyword

[ ] 4. Check other keywords

all core keywords prefixed with "$"

[ ] 5. Add contains keyword validation

The value of this keyword MUST be a valid JSON Schema.
An array instance is valid against "contains" if at least one of its

[ ] 6. Add propertyNames keyword validation

If the instance is an object, this keyword validates if every property name in the instance validates against the provided schema. Note the property name that the schema is testing will always be a string.

[ ] 7. Change exclusiveMaximum, exclusiveMinimum from boolean to number

[ ] 8. Add const keyword validation

The value of this keyword MAY be of any type, including null. An instance validates successfully against this keyword if its value is equal to the value of the keyword.

[ ] 9. Add examples keyword validation (warning)

The value of this keyword MUST be an array.  There are no  restrictions placed on the values within the array.

[ ] 10. Change format uriref -> uri-reference
[ ] 11. Add format uri-template
[ ] 12. Add format json-pointer
[ ] 13. Check and fix change if necessary

Allow empty "required" and "dependencies" arrays

[ ] 14. Check and fix change if necessary

Fixed "type" reference to primitive types

https://github.com/korzio/djv/issues/17

http://json-schema.org/draft-06/json-schema-migration-faq.html

Implemented changed include everything except id - that part will be fixed in https://github.com/korzio/djv/issues/41

https://github.com/korzio/djv/pull/47/files
This MR will exist until the fixes for state are introduced and all tests are passing. As soon as the branch is ready, there will be a new release introduced with a major version change.


Can't use the colourscheme

I'm installing it using paq.nvim. The plugin was able to succesfully install, but vim.cmd[[colorscheme dracula]] in my init.lua and  :colorscheme dracula both don't work.

I can not  reproduce it. Can you provide some more details?

I've switched to packer and it seems to work. I believe paq was causing the issue.


🚀 Feature: Monorepo workspaces support

Bug Report Checklist

[X] I have tried restarting my IDE and the issue persists.
[X] I have pulled the latest main branch of the repository.
[X] I have searched for related issues and found none that matched my issue.

Overview
This plugin is not working when using bun or yarn workspaces and importing a module from another package in the workspace that contains declaration files. I originally created a bug ticket for typescript-eslint and they were able to rule out any issues on their end. I created a repo to reproduce the issue.
Additional Info
No response

👋 sorry for the slow response @daniel-nagy! Thanks for filing both issues & creating a standalone repro, that's really helpful. 🙂
As for this reproduction: very interesting. A few notes:

Quick summary: this is purely using Yarn workspaces ("workspaces": ["packages/*"]), not any TSConfig paths or similar. b/package.json includes "dependencies": { "a": ... }.
Removing EXPERIMENTAL_useProjectService does not fix the error or change anything
The actual here is what includes const _copy: any: https://github.com/JoshuaKGoldberg/eslint-plugin-expect-type/blob/bf98512136f299226120c20abe578c5b337cef67/src/rules/expect.ts#L648-L659

...I'd guess this is an issue with the created TS language service: https://github.com/JoshuaKGoldberg/eslint-plugin-expect-type/blob/bf98512136f299226120c20abe578c5b337cef67/src/rules/expect.ts#L92-L94
Accepting PRs!

@all-contributors please add @daniel-nagy for bug.

🤖 Beep boop! This comment was added automatically by all-contributors-auto-action.
Not all contributions can be detected from Git & GitHub alone. Please comment any missing contribution types this bot missed.
...and of course, thank you for contributing! 💙


[Bug] Default Qwik City starter is broken.

Qwik Version
v0.0.34
Operating System (or Browser)
macOS Ventura 13.0
Node Version (if applicable)
v18.2.0
Which component is affected?
Qwik City v0.0.13
Expected Behaviour
The default Qwik City starter launches properly (no errors) when using Cloudflare Pages.
Actual Behaviour
Works fine when in dev mode (with Vite) but errors when the built version is run via wrangler pages dev or on Pages.
Callstack:
QWIK ERROR Error: Expected '' === 'html'.
    at logError$1 (/Users/isaac/Projects/qwik/server/entry.cloudflare.js:1768:52)
    at logErrorAndStop$1 (/Users/isaac/Projects/qwik/server/entry.cloudflare.js:1773:3)
    at assertEqual (/Users/isaac/Projects/qwik/server/entry.cloudflare.js:1807:11)
    at smartUpdateChildren (/Users/isaac/Projects/qwik/server/entry.cloudflare.js:3158:7)
    at visitJsxNode (/Users/isaac/Projects/qwik/server/entry.cloudflare.js:3055:12)
    at render$1 (/Users/isaac/Projects/qwik/server/entry.cloudflare.js:4662:9)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at renderToString (/Users/isaac/Projects/qwik/server/entry.cloudflare.js:24460:3)
    at onRequestGet2 (/Users/isaac/Projects/qwik/server/entry.cloudflare.js:25578:20)
    at next (/Users/isaac/.config/yarn/global/node_modules/wrangler/templates/pages-template-worker.ts:129:22)
    at ServiceWorkerGlobalScope.[kDispatchFetch] (/Users/isaac/.config/yarn/global/node_modules/@miniflare/core/src/standards/event.ts:359:13)
    at Server.<anonymous> (/Users/isaac/.config/yarn/global/node_modules/@miniflare/http-server/src/index.ts:290:20)

Seems to be an error inside smartUpdateChildren, specifically the line assertEqual(ch[0].$type$, "html"); which is failing because ch[0].$type$ is empty.
Additional Information
Default starter selected (with Cloudflare Pages). Nothing modified or changed.

This should be resolved with the next Qwik City drop, which is in the works....


Update documentation with conda instructions

Codecov Report

Merging #94 into master will not change coverage.
The diff coverage is n/a.

@@         Coverage Diff          @@
##           master   #94   +/-   ##
====================================
  Coverage      92%   92%
====================================
  Files           4     4
  Lines         775   775
  Branches      174   174
====================================
  Hits          713   713
  Misses         39    39
  Partials       23    23

Continue to review full report at Codecov.

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


don't throw error if a line with no spaces is too long

Here is an example code that can throw an error:
# NOTE this 2 lines are a hack to make numba work:
# https://numba.readthedocs.io/en/stable/user/troubleshoot.html#my-code-has-an-untyped-list-problem

The code in the second line can't be trimmed down but ruff still outputs a bug of "line too long"

I thought we did allow this, I'll take a look.

So I'm not able to reproduce an E501 error on that code. ruff --isolated --select E501 foo.py produces no output. (If I add some spaces within the URL, I do get an error as expected.) Are you able to reproduce?

Correct it was some other problem on my side.
Thnaks!


Unable to process template language expressions in action 'Check_if_site_exists_-_SP_API'

Hi folks!
I've re-done this install four times, verifying the settings every time. We're getting 502 errors when running the "Check Team Availability" flow. When we click, "check availability" after typing a search string, Teams displays an error:
CheckTeamAvailability. Run failed:
{ "error":
{ "code": 502, "source": "msmanaged-na.azure-apim.net", "clientRequestId": "4cff9922-c272-45d7-9af1-15732b45632c", "message": "BadGateway", "innerError": { "error": { "code": "NoResponse", "message": "The server did not received a response from an upstream server. Request tracking id '08585948111646717307560557965CU07'." } }
}
}

Viewing the logs on the app, the step, 'Check_if_site_exists_-_SP_API' shows an error:
InvalidTemplate. Unable to process template language expressions in action 'Check_if_site_exists_-_SP_API'
inputs at line '1' and column '2304':
The template language expression 'json(decodeBase64(triggerOutputs().headers['X-MS-APIM-Tokens']))['$connections']['shared_sharepointonline_1']['connectionId']' cannot be evaluated because property 'shared_sharepointonline_1' doesn't exist, available properties are 'shared_sharepointonline'. Please see https://aka.ms/logicexpressions for usage details

Any tips you could give us on this would be greatly appreciated. I'm a relative novice to this stack but I'm certain I did everything right.
Code view of the flow looks like:
{
"inputs": {
"host": {
"connection": {
"name": "@json(decodeBase64(triggerOutputs().headers['X-MS-APIM-Tokens']))['$connections']['shared_sharepointonline']['connectionId']"
}
},
"method": "post",
"body": {
"method": "POST",
"uri": "_api/SP.Site.Exists",
"headers": {
"accept": "application/json"
},
"body": "{\n"url":"@{variables('SiteURL')}"\n}"
},
"path": "/datasets/@{encodeURIComponent(encodeURIComponent('https://URL/RequestaTeamAppFour'))}/httprequest",
"authentication": {
"type": "Raw",
"value": "@json(decodeBase64(triggerOutputs().headers['X-MS-APIM-Tokens']))['$ConnectionKey']"
}
},
"metadata": {
"flowSystemMetadata": {
"swaggerOperationId": "HttpRequest"
}
}
}

@bungmaster If you check further down in the flow inside the 'Check site exists response' condition you will find another SharePoint action. Can you make sure this is updated too to point at your site URL and also the 'Teams Requests' list.

I just encountered this same issue. Seems like there's a few more buried SharePoint actions that aren't called out in the documentation, but once I changed those to match my SharePoint site - everything started working just fine.

I just encountered this same issue. Seems like there's a few more buried SharePoint actions that aren't called out in the documentation, but once I changed those to match my SharePoint site - everything started working just fine.

Hello @bungmaster ,
I had this issue as well. I got it resolved by exporting the flow (saving a ZIP to your desktop) and uploading it again as a new flow.
Source: https://powerusers.microsoft.com/t5/Building-Flows/property-shared-office365-doesn-t-exist/td-p/129667

Hello @bungmaster ,
I had this issue as well. I got it resolved by exporting the flow (saving a ZIP to your desktop) and uploading it again as a new flow.
Source: https://powerusers.microsoft.com/t5/Building-Flows/property-shared-office365-doesn-t-exist/td-p/129667


git: Build error 2.4.0 after e3147f2

I suspect that the fix in commit e3147f2 broke the build for those of us that don't have perl installed via linuxbrew.
The build fails on line 139 in Library/Formula/git.rb:
pod = Pathname.new Dir[lib/"*/*/perllocal.pod"][0]

with the error
Error: no implicit conversion of nil into String

Please see https://gist.github.com/RobertThz/54cb2c78e879c02b9dd5 for the full error message.
If I install the brew version of perl first, git builds just fine.

Woops. Thanks for the bug report, Robert.


Add support for the type attribute to the button element

Description
I'm submitting a ...

feature request

@jstarry I would like to work on this feature. Could you please tell me where to start ?

@captain-yossarian sure! Here's the key piece: https://github.com/yewstack/yew/blob/master/src/virtual_dom/vtag.rs#L304
Note that we alias "type" as "kind" internally because type is a rust keyword

@jstarry Every time, when I run cargo test I'm getting next error:
error: linking with cc failed: exit code: 1
I've tried all suggestions from this thread ->  rust-lang/rust#25289
I have:

installed all required packages from CONTRIBUTION.md
tried it on Ubuntu 18 and Windows 10
asked on yew chat - unfortunately nobody answered
also updated rust to last version.

If I run run_tests.sh from ci dir, I see new cmd window for 5 sec, then nothing.
Nothing don't work
Could you please tell me what I'm doing wrong?

@jstarry I'm trying to debug my changes but it hard to figure out how to make things happen.
For example, I've cnahged this line of code to
pub fn add_class(&mut self, class: &str) {
        let cl = "class";
        self.classes.push(cl);
    }

But class of my button component did not change.
Also, it is looks like that set_kind method already exists, but I dont know how to use it properly.

@captain-yossarian oh no, sorry to hear that! Did you go through all of the instructions here:
Contributing - Test  Setup
What happens when you run:
cargo test --target wasm32-unknown-unknown --features wasm_test

@jstarry Thanks a lot!

@jstarry I have linked my app to latest yew version and I'm getting next errors:
cargo build --features std_web

error: linking with `link.exe` failed: exit code: 1120
  |
  = note: "C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\BuildTools\\VC\\Tools\\MSVC\\14.24.28314\\bin\\HostX64\\x64\\link.exe" "/NOLOGO" "/NXCOMPAT" "/LIBPATH:C:\\Users\\sergi\\.rustup\\toolchains\\stable-x86_64-pc-windows-msvc\\lib\\rustlib\\x86_64-pc-windows-msvc\\lib" "D:\\rust\\yew-app\\target\\debug\\deps\\yew_app.14se02tsg9vgppee.rcgu.o"

AND
cargo build --features web_sys

error: failed to run custom build command for `yew v0.13.2 (D:\rust\yew)`

Caused by:
  process didn't exit successfully: `D:\rust\yew-app\target\debug\build\yew-f300a951e60e9aaf\build-script-build` (exit code: 101)
--- stderr
thread 'main' panicked at 'Selected target `x86_64-pc-windows-msvc` is not compatible with web-sys', D:\rust\yew\build.rs:28:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

warning: build failed, waiting for other jobs to finish...

@captain-yossarian I think you need to add target so it will build only to webassembly like this
cargo build --target wasm32-unknown-unknown --features web_sys

@fadhlika It works, thank you!

@jstarry @fadhlika
When I'm trying to run either
cargo test --target wasm32-unknown-unknown --features wasm_test std_web
OR
cargo test --target wasm32-unknown-unknown --features wasm_test web_sys
OR
cargo test --target wasm32-unknown-unknown --features wasm_test
I'm receiving:
thread 'main' panicked at 'Yew requires selecting either the `web_sys` or `std_web` cargo feature', build.rs:9:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

When if I run:
cargo test --target wasm32-unknown-unknown --features  std_web

I'm getting:
no tests to run

cargo test --target wasm32-unknown-unknown --features wasm_test std_web

You're telling cargo to run all tests named something with std_web while activating the feature wasm_test. You need to specify the features with --features wasm_test --features std_web or --features wasm_test,std_web.

@jplatte event with either
cargo test --target wasm32-unknown-unknown --features wasm_test --features web_sys

or
cargo test --target wasm32-unknown-unknown --features wasm_test --features std_web

or
cargo test --target wasm32-unknown-unknown --features wasm_test, std_web

I'm getting:
     Running target\wasm32-unknown-unknown\debug\deps\yew-c2b3c4287cf48ca8.wasm
thread 'main' panicked at 'unknown descriptor: 87', C:\Users\sergi\.cargo\registry\src\github.com-1ecc6299db9ec823\wasm-bindgen-cli-support-0.2.58\src\descriptor.rs:145:22
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.
error: test failed, to rerun pass '--lib'

Try updating wasm-bindgen-cli
On Thu., Mar. 12, 2020, 12:17 a.m. yossarian<EMAIL_ADDRESS>wrote:

@jplatte https://github.com/jplatte event with either
cargo test --target wasm32-unknown-unknown --features wasm_test --features web_sys
or
cargo test --target wasm32-unknown-unknown --features wasm_test --features std_web
or
cargo test --target wasm32-unknown-unknown --features wasm_test, std_web
I'm getting:
 Running target\wasm32-unknown-unknown\debug\deps\yew-c2b3c4287cf48ca8.wasm

thread 'main' panicked at 'unknown descriptor: 87', C:\Users\sergi.cargo\registry\src\github.com-1ecc6299db9ec823\wasm-bindgen-cli-support-0.2.58\src\descriptor.rs:145:22
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace.
error: test failed, to rerun pass '--lib'
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/yewstack/yew/issues/750#issuecomment-597728087, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIGXMPRAD36RH73C4NGJITRG62THANCNFSM4JPJQIZQ
.

@jstarry thank you, it helped

I think this issue can now be closed.

Thanks for the ping, I think this can stay to indicate that stdweb support isn't done yet. I'll update accordingly

@jstarry   Once stdweb approve my PR, I will finish my Yew PR

They haven't specifically said that it's no longer maintained. I think it's fine to leave this open until it's confirmed. We still have devs using stdweb

Agreed!


CI: Use cortex-a72

Closes https://github.com/hermitcore/rusty-loader/issues/99.

bors r+

bors retry


remove testling & travis build status from readme?

thanks for the great package!
just curious whether it'd make sense to remote the status badge images pointing to testling & travis, since they both seem unused (testling is saying that it's not working right now -- unsure if this is a semi permanent state or just a glitch)
cheers!

Yes, it would, I’ll do that today.


When getting to end of document, Reader should automatically remove the note from the 'Recently Read' list, providing v.easy way to undo

[ ] Implement API call to handle remove request
[ ] Implement API call to handle undo request


[FR]: Produce an archive file for a py_binary that packages the virtualenv

What is the current behavior?
No response
Describe the feature
This is useful to get a deployment target which matches the python expectation to resolve at runtime
Fund our work

[ ] Sponsor our open source work by donating a feature bounty

Would you expect it to package the interpreter? If so, perhaps we could leverage py oxidizer.

I think https://github.com/aspect-build/rules_py/blob/main/docs/pex.md satisfied the original intent here. It does not include an interpreter, but we're not intending to replace the python_zip_file feature
If someone wants more from rules_py here, please open another issue.


Widen PHP support

I know PHP 7.2 is already EOL but hear me out
This PR widens PHP support for the formatter to match requested PHPStan version 1.12.4, which supports PHP ^7.2|^8.0
The updates are the absolute minimum necessary to allow PHP 7.2 support, no behaviour is altered, added or removed
Given supported PHPStan version supports 7.2 I think this PR could be a reasonable change

Could you setup a CI matrix that tests all versions?

Thanks.
Do you think it would be good to also include a unit test? If you're up to it that would be great. 🙌

@juliangut would you be up for that?

sorry, at this moment I was interested only on the PHP version support, don't think I have the time to create a test suite but I think it's a good idea of course


Add: ROADMAP.md

Change Overview

Pull request type
Please check the type of change your PR introduces:

[ ] :construction: Work in Progress
[ ] :rainbow: Refactoring (no functional changes, no api changes)
[x] :hamster: Trivial/Minor
[ ] :bug: Bugfix
[ ] :sunflower: Feature
[x] :world_map: Documentation
[ ] :robot: Test

Issues

fixes #issue-number

Test Plan

[x] :muscle: Manual
[ ] :zap: Unit test
[ ] :green_heart: E2E

Obsoleted by #2126 roadmap branch.


Hope I can Learn from you

Hi friend,
Which tools you use to draw these so beautiful architecture diagrams?
Tks,
Cong

Hi @congzhangzh please use GitHub discussions for this kind of questions... (It on main tab)
To your question:  I used no tools for this just plain vector or chart editor... You need to build it from scratch..

Tks:)