undefined address when using braavos

Hey there,
We noticed an issue happening with Braavos (it worked fine with argent-x). After reloading the page, the multicall signing panel from braavos doesn't open when clicking on the button which calls the execute. The 'error' printed was Cannot read properties of undefined (reading 'address'). Braavos team told us this could be because the connector was not injected properly (we hardcoded it) or there is a problem in the starknet-execute. We tried to log the account in hooks/execute.js and it was undefined which is strange because window.starknet_braavos was defined. When changing the account value to window.starknet_braavos, it seems to work correctly.
Have a great day,
Thomas

@Th0rgal team is using @starknet-react/core "all in", e.g. not connecting directly with get-starknet or accessing the window injected object directly
they get the info from other hooks correctly (e.g. connected account's address, etc.)
when they call useStarknetExecute - while connected, with a valid callData object - the hook crashes at line 54 -

                    const account = await connector.account();
                    if (account.address === accountAddress) { -> `account` is undefined here, although window.starknet_braavos is valid + connected + have all the required information listed correctly

hey @fracek, any updates on this one?

Sorry, this was fixed in #159. Basically braavos was installed but not connected and so account was undefined and the code tried to access its address property.

@fracek but why did it happen only with Braavos? all starknet wallets have an undefined account value while disconnected?


feat: Add visionOS support

Overview

Add visionOS support to @react-native-clipboard/clipboard. To do so I needed to first:

Use @rnx-kit/align-deps to update the package to React Native 0.73 (minimum required for visionOS support)
Move the test app to react-native-test-app, so that we don't need to add a bunch of boiler plate for a new visionOS app.
Move over the old test app's App.tsx to the new test app

Test Plan
visionOS test app runs. iOS test app runs. macOS test app boots, but seems to error before rendering anything (not sure why).

This PR bumps the required React Native version to v0.73. Will this library no longer support v0.72 and earlier going forward?

Ah, meant to only bump the test app version. No source code changes so it should work with older versions

This PR bumps the required React Native version to v0.73. Will this library no longer support v0.72 and earlier going forward?

Ah, meant to only bump the test app version. No source code changes so it should work with older versions

@Naturalclar i can revert the rn minimum version bump?

@Saadnajmi

@Naturalclar i can revert the rn minimum version bump?

sure :+1:
sorry for not checking throughly :pray:

@Saadnajmi

@Naturalclar i can revert the rn minimum version bump?

sure 👍 sorry for not checking throughly 🙏

https://github.com/react-native-clipboard/clipboard/pull/235
I also fixed an issue with adding Yarn 4 that I noticed in the same PR

Hi,
Is this fixed? I am getting this when installing 1.14.1 (RN 0.71.14)
npm install npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR!  npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react-native npm ERR<EMAIL_ADDRESS>from the root project npm ERR!   peer<EMAIL_ADDRESS>|| ^0.62.3 || ^0.63.2 || ^0.64.2 || ^0.65.0 || ^0.66.0 || ^0.67.0 || ^0.68.0 || ^0.69.0 || ^0.70.0 || ^0.71.0 || ^0.72.0 || ^0.73.0" from<EMAIL_ADDRESS>npm ERR!   node_modules/@react-native-clipboard/clipboard npm ERR<EMAIL_ADDRESS>from the root project npm ERR!  npm ERR! Could not resolve dependency: npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>Thank you


Update civic.json file to new specification

Hi, there! Code for DC is moving to an updated civic.json
specification. This pull request formats your existing
civic.json to the new standard.
Feel free to look it over and make any updates.
The new civic.json spec keeps the required fields from the older
one, but has a number of benefits. It:

removes fields that are hard to maintain and get out of date quickly
combines partner fields to be more broadly applicable
is usable by civic tech projects outside of government, as well as inside

You'll see that DC Government is using this standard in its own repos:
https://github.com/dcgov
You can learn more about the specification requirements here:
http://open.dc.gov/civic.json

Hi Emanuel,
I am going to pull in the request, but I do not know if the Code for DC site supports the new format. So I might roll it back if it breaks our entry on http://codefordc.org/projects
Thanks for updating the spec. It needed attention!

Hey there, please keep the new format. I'll make sure that the site gets updated shortly.

Thanks @stvnrlly. @NSkelsey looks like there's a small mistake in the contacts field (giving the contact name as 'DC Public School Modernization Spending'—it should ideally be a person). If the project is out of the 'Ideation' phase, you should be sure to update that as well.

@emanualfeld, I'll update the fields right now!

:+1:


error: Cannot read properties of undefined (reading 'attributes')

I have integrated strapi-plugin-fuzzy-search "^1.10.0-beta.1", strapi version "4.3.9", set the search permissions from strapi admin panel and when I send request to "http://localhost:1337/api/fuzzy-search/search?query=" + text, I get the above mentioned error. Configuration in config/plugins.js is as follows:
module.exports = ({ env }) => ({
  "fuzzy-search": {
    enabled: true,
    config: {
      contentTypes: [
        {
          uid: "api::product.product",
          modelName: "product",
          queryConstraints: {
            where: {
              $and: [
                {
                  publishedAt: { $notNull: true },
                },
              ],
            },
          },
          fuzzysortOptions: {
            characterLimit: 300,
            threshold: -600,
            limit: 10,
            keys: [
              {
                name: "title",
                weight: 100,
              },
              // {
              //   name: "description",
              //   weight: -100,
              // },
            ],
          },
        },
      ],
    },
  },
});

What am I missing or doing wrong? Thank you.

So I removed version ^1.10.0-beta.1 and installed 1.9.4 and this fixed the issue


Remove preview features

As discussed in the PR when it was on the other project, whether we go with Java 17 minimum or something older, either way we should probably not make use of preview features.

Agreed, @adamkennedy. Do you know of any preview features we're currently using?

There is only one. We use pattern matching in switches several places I believe: https://openjdk.org/jeps/406
For reference, we may be able to use jabel to allow this and still compile to earlier bytecode versions. It only mentions Java 14 in the readme but it seems like work has been merged that supports newer java versions as well.

@jacques-n in the mean time, before jabel can handle it and could be set up, would a PR that just rolls back the pattern matching to vanilla Java 17 be accepted.

Propose it and let's take a look.

Proposed https://github.com/substrait-io/substrait-java/pull/94
Downgrades to java 11 for jar output

Resolved with #94


Add PHP8 to build

Depends on

#3
#4

and an updated imagick-Extension (https://github.com/Imagick/imagick/issues/380)


VSCode will not start--minimist module missing

VSCode Version: Latest (applied update today)
OS Version: Windows 7 SP1

Steps to Reproduce:

Auto-updated VSCode
Got an error saying VSCode failed to install, retried twice and then aborted install
Attempted to run code and same popup window from update appears

Note that 1/5 updates I apply will fail midway with a popup window, and the fix before this was to just abort the install and re-open VSCode and everything worked fine.  Today is the first time that it fails to start.

Next time you get the popup window, take a screenshot and show us in a new issue.
If installation fails, anything goes. If you reinstall successfully, it will work.

Thanks @joaomoreno, I got the same error when re-installing VSCode, so I'll open a new issue right now.


cluster: get latest if update status fail

If updateTPRObject() failed with conflict, delete will keep looping because the version doesn’t get updated.

@xiang90
fixed. PTAL

do you know why ci fails? code change looks good.

@xiang90
Both are known.
Look at the logs

TestS3DisasterRecovery is the same. The cluster is created in APIServer before controller starts listing. Good news is that once the status thing done it would be healed.
TestClusterRestore is new:

cluster (\"test-etcd-t160q\") is dead: fail to wait data copy job completed: timed out waiting for the condition

@etcd-bot retest this please

@etcd-bot retest this please


'put request' failed with octet-stream file

Put Request failed with sending octet-stream file, for example:
Create Session | ${session_name} | http://upload.mytestaddress.com/upload | timeout=60 | max_retries=0
${file_data} | Get Binary File | D:\\\\DSC_6613.jpg
${LocalHeader} | Create Dictionary | Content-type=application/octet-stream
${response}= | Put Request | ${session_name}  | /System/deviceInfo | ${file_data} | headers=${LocalHeader}

which will get error:
FAIL : UnicodeDecodeError: 'utf8' codec can't decode byte 0xff in position 0: invalid start byte

btw, if using Put keyword instead of Put Request, it won't get error.

@vkosuri I tried and got the same error.
I found where that exception came from:
https://github.com/bulkan/robotframework-requests/blob/11baa3277f1cb728712e26d996200703c15254a8/src/RequestsLibrary/RequestsKeywords.py#L816
and I don't understand why the data need to be decoded? Maybe this is unnecessary?

@mangobowl could you try to enable debug flag on create session?


LE Audio: Add broadcast audio samples

Adds broadcast audio samples
fixes https://github.com/zephyrproject-rtos/zephyr/issues/43487

These samples depend on https://github.com/zephyrproject-rtos/zephyr/pull/44075 before being usable.

ping @erikrobstad

There is also https://github.com/zephyrproject-rtos/zephyr/issues/44368 that will add LC3 encoding to these samples


A fix to get the Leap Images to show up in HDRP 2019.3 +

Apologies for not getting to this today.
The code's functionality looks fine, but would you mind fixing the indentation and renaming the PreRender callback to be consistent with the one here?
https://github.com/leapmotion/UnityModules/blob/develop/Assets/Plugins/LeapMotion/Core/Scripts/LeapXRServiceProvider.cs#L244-L247
(You can rename both of them if you like; I'd just like all instances to be similar for consistency)


Simpler option setting

Is there a fundamental reason why we can't do:
hv.Points(data)(color='red'})

instead of:
hv.Points(data)(style={'color':"red"})

I.e., does the distinction between the different types of options need to be something the user worries about in practice?  Couldn't holoviews just take a single list of keyword options and apply it to the plot options, style options, and normalization options in order, giving an error if none of those three were to consume it?  It's unlikely that any of the normalization options will ever match the name of one of the other two types, but of course it's possible that there is a style option that has the same name as one of the plot options.  Even so, (a) if that happens it's going to be very confusing for our users no matter what we do, so it's presumably good to avoid such name clashes, and (b) as long as we clearly define which option type has priority, people can deal with this issue for the very rare cases when it comes up, without having to use such a wordy and awkward syntax the rest of the time.  What do you think?

I can certainly see your suggestion would be convenient (for style options at least) and I would love a more succinct syntax!
The issue is we've designed our option systems to have these different groups (style, plot and norm by default) and they act a little bit like namespaces for options. I agree that ideally keys shouldn't clash but I don't think that means we should get rid of the idea and put all our keywords into a 'global' option namespace. Putting things into a common namespace for convenience makes me think of from pylab import * which we agree isn't a good idea...
So I am in favor of an easier syntax but allowing style, plot and normalization options to mix like this could cause trouble and difficulties down the line (the way global names tend to!).  Here is one suggestion I might consider:  the __call__ method knows the Element it is on and therefore could look up the corresponding style/plot/norm options via the Store. This means maybe you could drop style= or plot= if we can infer that all the keywords are either style or plot appropriately.
In other words, as long as you are only specifying one type of option, we could drop the need for the keywords, but if you want to specify a mixture, you still need to explicitly state what type of group they are in as before. I think this might be a plausible compromise that is safer than putting everything into the same namespace - although I should say that I haven't fully convinced myself that this is a good idea yet!

I'm not proposing to eliminate the distinction between the groups in general; indeed, they do act like namespaces, and the distinction is useful (especially to be able to tell which options are available for all backends, and which are backend-specific).  And in IPython there's a succinct syntax already, which is great.  So I'm not arguing for pooling all options into a single namespace.  Instead, I'm just arguing that the pure-Python user doesn't always need to worry about the distinction, just like one can always do 'import *'.  Thus, if the user wants to do hv.Points(data)(style={'color':"red"}), great -- namespace is respected.  But as shortcut, if the user does hv.Points(data)(color='red'}), it could still work and be quite well defined, with vastly less potential for clashes than "import *" (since the number of backends will surely always be a small countable number).  In obscure cases this will do something confusing (i.e., when the user means to set a style option for which there is a corresponding plot option with the same name), but this will be very rare, and in all other cases it should be much more convenient.
BTW, I'm less convinced that the distinction between plot options and normalization options is useful; I can't think of any case where one would want to separate those two categories.  Seems like just two more plot options, to me.

I'd be happy with this change. There generally shouldn't be any clashes between option groups and we could warn if you're attempting to specify an option that is duplicated across groups. It does go against explicit is better than implicit but I think it's sufficient to warn if there are clashes since in general we would generally advise against duplicating option keywords, simply to avoid confusion.

Warning if it's ambiguous sounds like a very good solution to me; still convenient but they know that they should be more explicit in that case.

If we weren't able to check the sets of keywords in option group, I would definitely be against the idea. However, as we can check the keywords in each option group, we can also ensure that there is no ambiguity in what the user supplies. If we do it this way, I am happy with the overall suggestion although I would prefer to raise an exception instead of issuing a warning: I feel the user should be made to use the explicit syntax in the (rare!) cases where the supplied name is ambiguous.
We will also have to immediately raise an exception if the user tries to use this simplified syntax and mistypes a keyword name: the keyword won't be recognized so there is no way of knowing which group it is supposed to belong to. Note that this feature would (at least initially) be implemented only for __call__ and only on basic Elements (i.e not for containers): the option specification syntax is complicated enough as we already support a huge number of different formats.

I'd be in favor of reducing the number of different option-setting formats supported, as long as there is one completely explicit way, plus this convenient way.  I think we went a little bit crazy with all the permutations currently supported. Even if we don't want to break the API at this point, we could certainly avoid documenting all but one of the other ways, to reduce confusion, being sure to remove all such examples from the tutorials.
Be careful about making option setting raise exceptions, though -- when people switch backends, we want things to keep working as best they can -- getting some plot out is much, much better than getting an error message.  Following the HTML/CSS metaphor that we proposed in the recent paper, we wouldn't even raise such warnings visibly (as browsers are required just ignore stylistic hints that they don't know what to do with), but that's a bit extreme.  We could raise an exception for options not defined for any backend, but even that's not necessarily a good idea -- e.g. it prevents forward compatibility, with the same plot working fine across various HoloViews versions apart from some small stylistic hint that was optional anyway but someone happened to specify because they had a newer HoloViews version than their colleagues.   I'm inclined to think that all option settings should just generate warnings (unless the user explicitly turns on some warnings_as_exceptions flag, e.g. for vetting or debugging), and that the warnings should always be silenceable (so that we could easily put in the right hints for both Matplotlib and Bokeh backends without having to put in lots of special-case code).

Be careful about making option setting raise exceptions, though -- when people switch backends, we want things to keep working as best they can ...

I agree with what you wrote which is why I opened #201 but in this instance this is a separate issue - this is about name clashes which we intend to avoid (and should be able to avoid!) no matter what backend is selected. This isn't quite the same problem as the fact that different backends accept different sets of keywords which is indeed the case we should generate warnings (the issue you describe). Earlier, I stated that we might need to raise an exception if the keyword is not recognized but I now realize this is unnecessary (you only need to check for clashes).
As this particular warning/exception is not supposed to ever happen (assuming the backends are implemented sensibly), simply raising an exception just seems easier to me. Again, if this condition does arise, it can be considered a bug in the backend implementation so it doesn't really matter whether you warn or raise an exception (I would go for the simplest option).

You said:

We will also have to immediately raise an exception if the user tries to use this simplified syntax and mistypes a keyword name

What I'm arguing above is that this policy would prevent forward compatibility -- allowing a plot written for a newer version of HoloViews to come out basically ok in an older version, apart from the warning and whatever that option does not being respected.  The vast majority of such options are, well, optional, such as setting line widths, fonts, specific colors, etc.  Having some plot come out, with a warning, is much more reassuring to a user who is trying to get his colleague's notebook to work on his system than just seeing an exception and no output, unless he's specifically requested warnings as exceptions.
Note that I'm not arguing that I'm certain an exception would never be a good idea for an option setting, but that we should explicitly consider whether we would want to raise such an exception, as a policy, so that we decide on a rational balance of error detection versus issues of forward and backward compatibility.

Oh, and as for name clashes, can we really guarantee they will never happen?  Don't we just pass style options down to the backend, without translation?  Or would we translate such an option if it clashed with our own plot options?

I'm not sure if you're actually disagreeing with this now, given your latest comment...

We aren't disagreeing - in my last comment, I corrected myself when I said we don't need to raise the exception that you quoted.

Don't we just pass style options down to the backend, without translation?

That is correct but we know what those options are ahead of time.

We don't know which backends will be added in the future, but we could commit to forcing any clashes to be filtered/renamed...

I've come to the conclusion that I am strongly in favor of this suggestion, I don't know of any instances where plot and style options clash and where they do I think we could simply raise an error that the options couldn't be disambiguated. Having the user distinguish plot and style options is imo the main source of confusion when using HoloViews and also massively increases verbosity.
I've assigned this to v1.10 so we can pick this discussion up again.

This would be a major API change so I think this is a version 2.0 feature request.

This would be a major API change so I think this is a version 2.0 feature request.

I don't see how this would introduce any backward compatibility concerns so I'm moving back to 1.10.

That doesn't mean it will get addressed for 1.10 of course, but I don't see any reason it couldn't be.

One other option to consider is something like:
image.style(cmap='jet')

Ideally you would have .style and .plot leaving  .opts to handl both when necessary. The problem with this is that .plot sounds like a command (which it is not) and .plotopts is awkward.
I think I would be happy with a .style method just for setting style options and allowing .opts to set plot options if you don't use the style and plot keywords (i.e in the style Jim suggested at the start of this issue).
I think this would make a lot of usage easier without discarding the distinction between these option types, which I believe is important to retain (e.g so users know where they are documented, when switching between plotting extensions etc). I know I would be happier with an approach like this than flattening the namespace.

I really don't see any reason to force users to remember the distinction between the two types. Our docs can keep them straight, which allows us to make the distinction when we need to explain things, but why should users have to remember it just to use them? Plus the verbosity is very irritating. Let's give our users a break!

How would you address setting opts for a particular backend with this suggestion?
An optional backend='matplotlib' argument?

I really don't see any reason to force users to remember the distinction between the two types.

That is how they know whether to look in the holoviews docs, the bokeh docs or the matplotlib docs. I think it is a very important distinction.

Sure, it's a very important distinction for developers to make and to make clear in our docs; users do need to be able to find out which kind it is.  But they really don't need to remember which kind it is to use it. E.g. "height" -- why should they care whether it's a plot or style option?  People can use it just fine without consulting any documentation, and it's just an irritation to have to try one way and then switch it to the other to make it work. There's no deep reason it is a plot vs. a style option, at least not one evident to users, so why force everyone to remember arbitrary information like that, or to use trial and error to get it to work?  It's a very unfriendly policy; we as developers can keep the two types straight all we want without having to require each and every user to do it every time they use them. Why make users jump through pointless hoops, and make all our examples and applications needlessly more verbose?


Update docker.md readme to note memory requirements

Description
When attempting to get druid running inside Docker Desktop via the docker-compose file (both built from source and referencing the 0.17.0 published image), I experienced repeated crashing of the broker process with a 137 error code. 137 indicates an OOM error, so I notched up Docker's memory resource in 1gb increments (I believe the default is 2gb), landing on 6gb as a setting that works reliably.
As a newcomer with little knowledge of druid, it was quite difficult to identify exactly what the issue was initially. A note like this would have helped point me in the right direction.

This PR has:

[x] added documentation for new or modified features or behaviors.

@suneet-s I was able to run just the broker consistently with 4gb. The whole cluster also runs with 4, but crashed occasionally. 6 seems to be the floor for consistency, at least on my machine. Perhaps noting a range of 4-6 would be more appropriate so people don't overshoot if unnecessary.
I'm running the cluster described in the docker-compose file unmodified which includes postgres, zookeeper, coordinator, broker, historical router, and middlemanager.


when i giving the commmand python3 SocialFish.py it giving down error please help

Traceback (most recent call last):
File "SocialFish.py", line 4, in
from flask import Flask, request, render_template, jsonify, redirect, g, flash
ModuleNotFoundError: No module named 'flask'

Try the setup instructions https://github.com/UndeadSec/SocialFish/wiki


Conference: Allow SAC-paper assignments deployment before AC-paper assignments

This PR is for ARR - it checks the assignment invitation to see if the edges are pointing to profiles. If it is not, then allow deployment before the AC assignments and use different logic for overwriting and populating the SAC groups.

I wonder if we would need this changes for API 2 venues too.


[LiveComponent] getComponent is undefined if the controller loads very quickly as explained in the docs

Based on the docs the getComponent method should be called during initialize. Becase it's a Promise the method initialize should be async.
When the component loads very quickly, this.component will be undefined in connect:
import { Controller } from '@hotwired/stimulus';
import { getComponent } from '@symfony/ux-live-component';

export default class extends Controller {
  async initialize() {
    this.component = await getComponent(this.element);
  }

  connect() {
    console.log(this.component); // undefined
  }
}

Adding async connect won't solve the problem. Adding a small delay will solve the problem. Another way is to call getComponent inside async connect. Either way, the documentation is a bit "obscure" about this and devs without a good JavaScript understanding will have the same issue.
I don't know if this is a bug or the way Stimulus work, but I was expecting that connect will be called after initialize resolve.

Any update or workaround? Still in the official documentation...

Instead of using connect there, you should rely on the events dispatched by the LiveComponent

What do you mean @smnandre ? It's the official example in Symfony docs!

The documentation is see
// assets/controllers/some-custom-controller.js
// ...
import { getComponent } from '@symfony/ux-live-component';

export default class extends Controller {
    async initialize() {
        this.component = await getComponent(this.element);

        this.component.on('render:finished', (component) => {
            // do something after the component re-renders
        });
    }
}

And it's a bit... skinny. What if I need component.emit based on some javascript event? Where would you put that logic?
onPaste() {
  this.component.emitSelf("paste", { value });
}

Inside onPaste, happens somtime that this.component is undefined, based on how fast the controller loads.

async initialize() {
        this.component = await getComponent(this.element);

        // THERE

        this.component.on('render:finished', (component) => {
            // do something after the component re-renders
        });
    }

I have this problem in another project, again :cry:
The getComponent inside initialize or connect actually throw (from time to time):

Uncaught (in promise) Error: Component not found for element
.

In my custom Stimulus controller:
  async connect() {
    this.component = await getComponent(this.element);
    this.activate();
  }

The component is rendered as:

Could be an issue related to the fact that MY controller is listed before the live controller (as you can see from the screeshot below)? From the source, I can see that getComponent` will try 10 times every 5ms, for a total time of 500ms.

Is one of your controllers fetched lazily ?

I have this problem in another project, again 😢
The getComponent inside initialize or connect actually throw (from time to time):

Uncaught (in promise) Error: Component not found for element
.

In my custom Stimulus controller:
  async connect() {
    this.component = await getComponent(this.element);
    this.activate();
  }

The component is rendered as:

Hello, I have the exact same issue, and it also happens only "from time to time". I understand this inconsistency is because of the interval inside live_controller.js :
// vendor/symfony/ux-live-component/assets/dist/live_controller.js (l.144) :

const getComponent = (element) => new Promise((resolve, reject) => {
    let count = 0;
    const maxCount = 10;
    const interval = setInterval(() => {
        const component = componentMapByElement.get(element);
        if (component) {
            clearInterval(interval);
            resolve(component);
        }
        count++;
        if (count > maxCount) {
            clearInterval(interval);
            reject(new Error(`Component not found for element ${getElementAsTagText(element)}`));
        }
    }, 5);
});

So, sometimes the component can be found before the tenth attempt, sometimes it can't... but why? I can't figure out the reason why the component cannot be found.
The easiest way for me to reproduce the error is by continuously switching from page A to page B then page B to page A (with both pages using the same component). By doing this on a remote test server, the error happens at almost each page change (like 99% of the time or so). But somehow when I do the same on my local machine, the error is much less frequent (but still there "from time to time" though).
Now I'm just randomly guessing but : could this be related to Turbo?
Like when Turbo temporarily shows the previously cached version of page A while loading its refreshed version.
I wonder if the error we see could be triggered from that temporary displayed, previous version of page A? Which could explain why everything still works as expected after that error?
I mean something like that :

User goes on page A for the first time. Page A wasn't already cached by turbo. Everything is ok.
User goes from page A to page B by clicking a link. Page B wasn't already cached by turbo. Everything ok.
User goes from page A again by clicking a link. Page A was cached by turbo, so turbo immediately shows that cached version then starts refreshing it in the background.
Cached version of page A triggers the error somehow (no idea why), it's displayed in the browser console.
Turbo finishes fetching refreshed version of page A and displays it. Everything works for the user, but the error is still there in the console.

That's just a suggestion based on my own observations, but I'm really sure about nothing here. Like I said I'm just guessing, it's very hard to understand what exactly happens.

I can't reproduce either when/why we get undefined when calling getComponent. I can only quote myself:

Could be an issue related to the fact that MY controller is listed before the live controller (as you can see from the screeshot below)? From the source, I can see that getComponent` will try 10 times every 5ms, for a total time of 500ms.

As a workaround right now I'm doing:
const component = this.element.__component ?? (await getComponent(this.element));

... right before calling my (remote) action from the controller.

I really  would like to help but i don't have enough time right no, so with no reproducer you understand it can be hard.
If i had more time i'd do more but right now i fear i won't be usefull here :|


/api/candidates/:id endpoint

I've never used ruby before, so let me know if I did this right! :)

Looks good, thanks!


Panicked in go_online()

A unit test in my wallet is panicked in _go_online().
Here is a message from the runtime.
thread '<unnamed>' panicked at 'running stored runtime: AppLevel(Database(Io(Custom { kind: Other, error: "could not acquire lock on \"/tmp/shiro-wallet/60ec7707/sled.db/db\": Os { code: 11, kind: WouldBlock, message: \"Resource temporarily unavailable\" }" })))', /home/monaka/.cargo/git/checkouts/rgb-lib-b21a551c0f942d1d/d1de142/src/wallet/mod.rs:1693:42

I found /tmp/shiro-wallet/60ec7707/sled.db/db on the test environment.
Referring to your code, the database is accessed in a other thread.
https://github.com/RGB-Tools/rgb-lib/blob/1028e9aff8e72fe79987a85bda9b2abfa5717883/src/wallet/mod.rs#L1693
I'm not sure but I suppose my unit tests are calling go_online() more than twice.
I think there is room to avoid or reduce panic.
However, I can fix it to reduce calling go_online() for now.
This is a feature request rather than a bug report.

I checked my code again and it may be caused by stored.

my modified code calls go_online() just once.
I got the same error reported above.

I asked about this issue on the stored repository.

I pushed code to reproduce this issue to https://github.com/diamondhands-dev/shiro-backend/tree/reproduction-rgb-lib-issue-15 .
3 failed test test wallet::tests::test_put_bad, wallet::tests::test_put_failed,
and wallet::utxos::tests::test_get have no came here|came here! in logs.
So they don't call go_online().
The last test wallet::utxos::tests::test_get have came here in the log.
It is a first go_online() and it was panicked.

calling go_online() more than once should work and is covered by tests
https://github.com/RGB-Tools/rgb-lib/blob/1028e9aff8e72fe79987a85bda9b2abfa5717883/src/wallet/test/go_online.rs#L16
the success test shows how to call go_online() twice successfully, using the same electrum and proxy URLs
https://github.com/RGB-Tools/rgb-lib/blob/1028e9aff8e72fe79987a85bda9b2abfa5717883/src/wallet/test/go_online.rs#L39
the fail test shows how go_online() returns a specific error (CannotChangeOnline) if called twice with mismatching URLs
it is not supposed to to panic so other issues might be at play

@nicbus @zoedberg Thank you for your comments.
As I commented, I see this issue is caused by my unexpected API calls.
I close this issue. And I raised #18 instead.
I suppose that #18 is an issue under expected calling steps.
I close this issue as invalid. Thank you for your help.

@monaka you're welcome. I've just seen #18 and I think I understand why it's failing. Shortly I will answer there too


fix #1007

variables that start with true/false

Codecov Report

Merging #1010 (d29b77c) into develop (5dd988a) will increase coverage by 0.20%.
The diff coverage is 80.00%.

@@             Coverage Diff             @@
##           develop    #1010      +/-   ##
===========================================
+ Coverage    57.85%   58.05%   +0.20%
===========================================
  Files           74       74
  Lines         4114     4127      +13
===========================================
+ Hits          2380     2396      +16
+ Misses        1734     1731       -3

Impacted Files
Coverage Δ

.../rescript/FunctionRegistry/Library/FR_Pointset.res
86.84% <78.57%> (-4.83%)
:arrow_down:

...rescript/FunctionRegistry/Library/FR_Sampleset.res
82.66% <83.33%> (+6.35%)
:arrow_up:

...script/Distributions/PointSetDist/PointSetDist.res
72.72% <0.00%> (+1.01%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Great, thanks!


Deprecate CU1Gate

U1Gate is deprecated, so it seems sensible that CU1Gate should also be deprecated. I'm looking at the docs, where U1Gate has a deprecation warning but CU1Gate does not:

https://docs.quantum.ibm.com/api/qiskit/qiskit.circuit.library.U1Gate
https://docs.quantum.ibm.com/api/qiskit/qiskit.circuit.library.CU1Gate

This seems sensible - CPhaseGate is a direct replacement.  Fwiw, we didn't deprecate U1Gate and friends formally in code, they're just deprecated by the documentation notice.  The reason is roughly that there's still a lot of extant circuits / OQ2 code / etc out there that uses them, and keeping the gate class around so they can still be represented doesn't really hurt us.
We did deprecate (and remove) the circuit methods u1, u2 and u3, though, and I think deprecating and removing QuantumCircuit.cu1 would be equally appropriate.
There is the awkward question about CU3Gate, though; we don't have a direct replacement for that (CUGate exists, but it's a lot more awkward to use because it breaks the typical controlled-gate flow by adding in a control-phase parameter).

There is the awkward question about CU3Gate, though; we don't have a direct replacement for that (CUGate exists, but it's a lot more awkward to use because it breaks the typical controlled-gate flow by adding in a control-phase parameter).

True, though we're replacing calling CU3Gate directly, which could be (almost) directly replaced with CUGate, no?

Hi @kevinsung  @jakelishman I can work on this

Sounds good @melechlapson, let us know if you want to discuss something -- otherwise @jakelishman's comment above points out some places to start 🙂

@Cryoris Should I add a deprecation warning to MCU1 as well?

Yes, as MCPhaseGate is a direct replacement we can also deprecate MCU1Gate 👍🏻

We did deprecate (and remove) the circuit methods u1, u2 and u3, though, and I think deprecating and removing QuantumCircuit.cu1 would be equally appropriate.

@jakelishman  Isn't already removed and deprecated? It's just the CU1Gate that remains

@Cryoris I opened https://github.com/Qiskit/qiskit/pull/13115 to address this. Could you review when you have time?

make sure you link it to this pull request @melechlapson or else it likely can't be found.

@Cryoris  #13115  was merged, however this issue is still open, is this issue yet to be resolved?

@alphashiv27 it seems we just forgot to link the PR to this issue -- thanks for the reminder!


How to use textures as input?

Hi, I am trying to use these shaders for image processing. I've read in the flutter documentation that sampler2D is a valid uniform as an input to the shader. However I cannot find a way to generate that uniform in dart since it is not just a double. Is there a specific type for that exposed in the API?

I haven't tried it myself, but from documentation you should be able to pass List<ImageShader> into the shader(...) of the FragmentProgram. See: https://api.flutter.dev/flutter/dart-ui/FragmentProgram/shader.html
And ImageShader can be created from an Image, which should be straight forward: https://api.flutter.dev/flutter/dart-ui/ImageShader-class.html
If you are successful, it would be cool to report back your experience or a minimalist example (e.g. link to Git repo).

Thats exactly what I could not find. Thanks a lot. I will report back soon.

I've done it! Thanks a lot. Feel free to use any of thios as an example in your project:
https://github.com/MindStudioOfficial/texshader_test

Oh wow, I didn't even think of that.
But then you would need to overlay the processed image of the ui on top of the ui. Do gestures and such still work behind the ShaderPainter?

Yes you can place AbsorbPointer (https://api.flutter.dev/flutter/widgets/AbsorbPointer-class.html) where you like.


Node layout sizing resets to defaults on workflow update

Describe the Bug with repro steps
When a workflow is resubmitted to the designer after a flow has already been processed, the designer resets all node sizes back to their default values (only in our layout algorithm, not in the actual viewport).
Normally this results in the spacing between nodes becoming much smaller.

Turns into =>

What type of Logic App Is this happening in?
Standard (Portal)
Are you using Preview Designer or GA Designer
Preview
Browser
Chrome

@rllyy97 - Will this help in our rendering in Portal as well or we have to come up with different mechanism to handle this bug.
Current PA team is going to pass an option on designer component on when to not recalculate.


dbt is creating schemas when they already exists because of case-sensitive comparisons

Issue
In Snowflake, DBT is trying to create a schema that already exists.   Because my snowflake role does not have create schema privs, I get an Insufficient privileges to operate on database 'foo' error when dbt tries to create the schema.
Issue description
Stacktrace:
2019-08-01 18:05:01,735 (MainThread): On master: select distinct schema_name
    from CENTRAL_DATA.information_schema.schemata
    where catalog_name ilike 'CENTRAL_DATA'
2019-08-01 18:05:04,211 (MainThread): SQL status: SUCCESS 9 in 2.48 seconds
2019-08-01 18:05:04,223 (MainThread): Creating schema "CENTRAL_DATA"."cdm".
2019-08-01 18:05:04,227 (MainThread): Using snowflake connection "master".
2019-08-01 18:05:04,227 (MainThread): On master: BEGIN
2019-08-01 18:05:04,417 (MainThread): SQL status: SUCCESS 1 in 0.19 seconds
2019-08-01 18:05:04,417 (MainThread): Using snowflake connection "master".
2019-08-01 18:05:04,417 (MainThread): On master: create schema if not exists CENTRAL_DATA.cdm
2019-08-01 18:05:04,727 (MainThread): Snowflake error: 003001 (42501): 018dec4d-0307-9857-0000-0379146884aa: SQL access control error:
Insufficient privileges to operate on database 'CENTRAL_DATA'
2019-08-01 18:05:04,728 (MainThread): On master: ROLLBACK
2019-08-01 18:05:05,336 (MainThread): Connection 'master' was left open.
2019-08-01 18:05:05,337 (MainThread): On master: Close
2019-08-01 18:05:05,953 (MainThread): Sending event: {'category': 'dbt', 'action': 'invocation', 'label': 'end', 'context': [<snowplow_tracker.self_describing_json.SelfDescribingJson object at 0x1080a42e8>, <snowplow_tracker.self_describi
ng_json.SelfDescribingJson object at 0x106d629b0>, <snowplow_tracker.self_describing_json.SelfDescribingJson object at 0x106d62748>]}
2019-08-01 18:05:06,031 (MainThread): Flushing usage events
2019-08-01 18:05:06,031 (MainThread): /Users/edmund.yan/.pyenv/versions/3.6.2/envs/central-data/lib/python3.6/site-packages/dbt/main.py:97: DeprecationWarning: The 'warn' method is deprecated, use 'warning' instead

2019-08-01 18:05:06,031 (MainThread): Encountered an error:
2019-08-01 18:05:06,031 (MainThread): /Users/edmund.yan/.pyenv/versions/3.6.2/envs/central-data/lib/python3.6/site-packages/dbt/main.py:98: DeprecationWarning: The 'warn' method is deprecated, use 'warning' instead

2019-08-01 18:05:06,031 (MainThread): Database Error
  003001 (42501): 018dec4d-0307-9857-0000-0379146884aa: SQL access control error:
  Insufficient privileges to operate on database 'CENTRAL_DATA'
2019-08-01 18:05:06,050 (MainThread): Traceback (most recent call last):
  File "/Users/edmund.yan/.pyenv/versions/3.6.2/envs/central-data/lib/python3.6/site-packages/dbt/adapters/snowflake/connections.py", line 77, in exception_handler
    yield
  File "/Users/edmund.yan/.pyenv/versions/3.6.2/envs/central-data/lib/python3.6/site-packages/dbt/adapters/sql/connections.py", line 60, in add_query
    cursor.execute(sql, bindings)
  File "/Users/edmund.yan/.pyenv/versions/3.6.2/envs/central-data/lib/python3.6/site-packages/snowflake/connector/cursor.py", line 558, in execute
    errvalue)
  File "/Users/edmund.yan/.pyenv/versions/3.6.2/envs/central-data/lib/python3.6/site-packages/snowflake/connector/errors.py", line 97, in errorhandler_wrapper
    cursor.errorhandler(connection, cursor, errorclass, errorvalue)
  File "/Users/edmund.yan/.pyenv/versions/3.6.2/envs/central-data/lib/python3.6/site-packages/snowflake/connector/errors.py", line 73, in default_errorhandler
    done_format_msg=errorvalue.get(u'done_format_msg'))
snowflake.connector.errors.ProgrammingError: 003001 (42501): 018dec4d-0307-9857-0000-0379146884aa: SQL access control error:
Insufficient privileges to operate on database 'CENTRAL_DATA'

Results
https://github.com/fishtown-analytics/dbt/blob/399b33822a85493a8790df787eed59e951aecf6c/core/dbt/task/runnable.py#L306-L324
I believe there is a bug in create_schemas() and case sensitivity.  In Snowflake, list_schemas() will return schema names in upper-case.   However, if you define your schemas in your dbt project or profiles in lowercase, the set subtraction of required_schemas - existing_schemas will not identify that the schema already exists and will re-create it.
When I change my dbt_project.yml and profiles.yml to use only upper-case schema names, it works as expected.
System information
The output of dbt --version:
0.14.0

The python version you're using (probably the output of python --version)
Python 3.6.2

Proposed Solutions

dbt does not support case-sensitive schemas
This looks like the easiest route.  If you look at https://github.com/fishtown-analytics/dbt/issues/1411, we already consider databases to be case insensitive.

dbt supports case-sensitive schemas
If we go this route, I think the default should be case insensitive.  However, if you double quote your schema name, it will evaluate as case-sensitive.  This seems like a better solution, but I'm unsure of all the downstream call points that would need to be updated to support this.

Happy to help submit a patch if you give me some direction on what the correct fix should be :)

Thanks for the report @edmundyan! Casing + quoting on Snowflake can be a bit of a nightmare!
I think it makes sense to make this schema lookup case-insensitive. One good approach could be to just upper-case (or lower-case) the schema names in each set (required_schemas and existing_schemas), then compute the set-difference.
dbt in general will do very undesirable things if users try to have two distinct schema names that are distinguished only in their casing. I think it's ok to continue to assume that users won't (or can't) do that here.
We'd love a PR for this one! Let me know if there's anything I can do to help out. Check out the contributing guide for some info on how to get set up for development with dbt.


Implement Java drop-in lib

I would be very grateful if you could point to any Java documentation on this topic. I've been Googling for a couple days on this topic and have not found anything on how to describe what to push or how to actually do the pushing. The server must need to know what to push, as they do not read minds. Furthermore, if the server is serving index.html when does it even get a chance to execute some code? I am assuming that this only works via servlet but without any documentation I'm mostly just confused.
Thanks for any pointers.

I tried the rather obvious technique of using the appengine-web.xml file for defining this but it does not allow "<" in the value of the http-header tag.
<include path="/index.html" >             <http-header name="link" value="<https://craftycoder-test-space.appspot.com/bower_components/paper-checkbox/paper-checkbox.html>; rel=preload; as=document" />         </include>

I managed to add the Link header by excluding my index.html from the list of static files:
<public-root>/static</public-root>
<static-files>
  <include path="/static/**" />
  <exclude path="/static/index.html" />
</static-files>

And using a Filter to intercept requests, populate the header and finally forward to index.html.
Something like this:
private final static String preloadResources = Joiner.on(",").join(ImmutableList.<String>of(
        "</fonts/roboto/Roboto-Regular.ttf>; rel=preload; as=font",
        "</styles/app-main.css>; rel=preload; as=style",
        "</scripts/app.js>; rel=preload; as=script",
        "</elements/app-main.html>; rel=preload; type=document"
));

@Override
public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws IOException,
        ServletException {

    String scheme = request.getScheme();
    String nopush = request.getParameter("nopush");
    if (null == nopush && "https".equals(scheme)) {
        HttpServletResponse httpResponse = (HttpServletResponse) response;
        httpResponse.addHeader("Link", preloadResources);
    }

    RequestDispatcher rd = request.getRequestDispatcher("/index.html");
    rd.forward(request, response);
}

Ideally this filter would get the assets to push from a json file (like the python drop in does).

The appengine-web.xml file also has a length limit for the value attribute which makes it a poor choice as well. I'll try your idea.

I implemented a filter and it still does not really work. Unless my header value is arbitrarily short, which is impractical sense we need to include the giant domain name for every file, the header just gets dropped. Anyone know if there is a way to configure max header value length in app engine?

I don't know about a "max header value length", but GAE limits the number pushed assets to 10 (I think). Even if you manage to add 50 only the first 10 would be pushed.

BTW, if someone wants to add a Java demo to the examples folder that would
be welcomed :)
On Thu, Jun 16, 2016, 9:09 AM Joshua Oster-Morris<EMAIL_ADDRESS>wrote:

I implemented a filter and it still does not really work. Unless my header
value is arbitrarily short, which is impractical sense we need to include
the giant domain name for every file, the header just gets dropped. Anyone
know if there is a way to configure max header value length in app engine?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GoogleChrome/http2push-gae/issues/8#issuecomment-226533851,
or mute the thread
https://github.com/notifications/unsubscribe/AAOigCwu-QbGvvn8mro4CTjXTr-dOd0Jks5qMXU7gaJpZM4GOB5Y
.

I managed to add all 12KB of file names (by appending multiple link headers), sadly it was still ineffective because it looks like it ignores nearly all the push requests anyway (your 10 number looks about right even though I have not confirmed it). I am now officially confused as to the purpose of this. The I/O talks made it sound like vulcanizing is now an anti-pattern because of http/2 push. If I can only push 10 files, then it is next to useless for a webcomponents project that uses tons of little files by design. Am I misunderstanding something?

@craftyc0der 10 is the limit imposed by GAE right now. That doesn't mean other h2 servers impose the same restriction.
I'm not sure it's advisable to ever push dozens of resources. There's the potential to needlessly eat up bandwidth and actually bottleneck your initial page. What was showed at I/O with the PRPL pattern is pushing a few critical resources (push), render those resources for a fast paint, preload load additional resources for routes, then lazy load them on demand. To set that up, it requires care in how you construct you architect you app.

Just the neon-animation tag is 9 files. Is there a legit way to build a modularized webcomponent page that could actually render with 10 files? I'm trying to understand why we were told that vulcanization is an antipattern if we still basically need to serve files one at a time. Should I just come back to this in 6 months? Am I too early?

That's something the Polymer team needs to figure out. For example, the https://shop.polymer-project.org/ demo uses very few (any?) of the current element set. I think one thing we'll need to explore is elements that don't have 1000s dependencies if the PRPL pattern is going to work well.
My suggestion is to bring this up on the Polymer issue tracker. This project is unrelated to polymer :)
We've gone way off-course from the original issue. Let's keep it focused on a Java example for push on GAE.

Sorry to take us off course. Thanks for taking the time.


chore: repo cleanup

Updates the permissions for some files and organizes them.
Adds a Makefile to install the protonfixes module and build xrandr, which is expected to be built within the Steam Runtime.

Setting up the Steam Runtime environment must be done through a container management framework such as podman or docker. Example through distrobox within the project directory:

distrobox create -n sniper --image registry.gitlab.steamos.cloud/steamrt/sniper/sdk:beta
distrobox enter sniper
git submodule update --init --recursive
make
make install

Edit:
As a result, the distributable ./dist/protonfixes will be created and which will contain the following files:
cabextract  download.py       gamefixes-battlenet  gamefixes-humble   gamefixes-umu           libmspack.so.0      util.py
checks.py   engine.py         gamefixes-ea         gamefixes-itchio   gamefixes-zoomplatform  libmspack.so.0.1.0  verbs
config.py   fix.py            gamefixes-egs        gamefixes-steam    __init__.py             logger.py           winetricks
debug.py    gamefixes-amazon  gamefixes-gog        gamefixes-ubisoft  libmspack.so            steamhelper.py      xrandr

where only cabextract, libmspack.so, xrandr and winetricks will be writable and executable.
TODO:

[x] Build cabextract and libmspack.so.0
[x] Update Makefile in proton-ge-custom
[x] Add Github Action for build

@loathingkernel review on the Makefile would be appreciated.

the Makefile LGTM so far, I'll keep an eye out to look into it again once the PR is ready.

cc @loathingKernel
A second review would be appreciated.

Tested locally by overwriting the relevant binaries and protonfixes directory in GE-Proton9-11 then running the winetricks verbs quartz, wmp11 and cabextract using umu-launcher.
Log: https://gist.github.com/R1kaB3rN/ca8d61973f4cc6fde953b44bdc24c875
Should be ready to merge.


docs: fix broken link

PR checklist

[ ] Addresses an existing issue: #0000
[ ] New feature, bugfix, or enhancement
[ ] Includes tests
[X] Documentation update

Overview of change:
Fix broken links in rule docs,
Example: go to https://palantir.github.io/tslint/rules/promise-function-async/
and click the "Requires Type Info" link
Is there anything you'd like reviewers to focus on?
no
CHANGELOG.md entry:
N/A

Thanks for your interest in palantir/tslint, @larshp! Before we can accept your pull request, you need to sign our contributor license agreement - just visit https://cla.palantir.com/ and follow the instructions. Once you sign, I'll automatically update this pull request.

@larshp thanks!


Insert bibliography entry cited in full length in the text

Hi,
I'd like to get the full length of an entry directly in the text. Is this possible ?
The \bibentry command from the bibentry package does it for bibtex, but I'm usign pandoc-citeproc & pandoc-crossref.
Thanks !

I would also like to add full citations in the text. While we wait to hear from @jgm, you may want to review this similar feature request for implementing the \fullcite biblatex command.

Oh, I had missed it, thanks !


DB migration runner lock bug

  | 2023-05-19T13:18:56.366-07:00 | INFO 2023-05-19T20:18:56.365Z Starting Medplum Server...
  | 2023-05-19T13:18:56.366-07:00 | INFO 2023-05-19T20:18:56.366Z configName: aws:/medplum/prod/
  | 2023-05-19T13:19:01.237-07:00 | INFO 2023-05-19T20:19:01.236Z Run database migration v42
  | 2023-05-19T13:19:04.797-07:00 | error: deadlock detected
  | 2023-05-19T13:19:04.797-07:00 | at Parser.parseErrorMessage (/usr/src/medplum/node_modules/pg-protocol/dist/parser.js:287:98)
  | 2023-05-19T13:19:04.797-07:00 | at Parser.handlePacket (/usr/src/medplum/node_modules/pg-protocol/dist/parser.js:126:29)
  | 2023-05-19T13:19:04.797-07:00 | at Parser.parse (/usr/src/medplum/node_modules/pg-protocol/dist/parser.js:39:38)
  | 2023-05-19T13:19:04.797-07:00 | at Socket.<anonymous> (/usr/src/medplum/node_modules/pg-protocol/dist/index.js:11:42)
  | 2023-05-19T13:19:04.797-07:00 | at Socket.emit (node:events:513:28)
  | 2023-05-19T13:19:04.797-07:00 | at addChunk (node:internal/streams/readable:324:12)
  | 2023-05-19T13:19:04.797-07:00 | at readableAddChunk (node:internal/streams/readable:297:9)
  | 2023-05-19T13:19:04.797-07:00 | at Readable.push (node:internal/streams/readable:234:10)
  | 2023-05-19T13:19:04.797-07:00 | at TCP.onStreamRead (node:internal/stream_base_commons:190:23) {
  | 2023-05-19T13:19:04.797-07:00 | length: 307,
  | 2023-05-19T13:19:04.797-07:00 | severity: 'ERROR',
  | 2023-05-19T13:19:04.797-07:00 | code: '40P01',
  | 2023-05-19T13:19:04.797-07:00 | detail: 'Process 10837 waits for ShareLock on virtual transaction 11/17013777; blocked by process 10838.\n' +
  | 2023-05-19T13:19:04.797-07:00 | 'Process 10838 waits for ExclusiveLock on advisory lock [16400,0,1,1]; blocked by process 10837.',
  | 2023-05-19T13:19:04.797-07:00 | hint: 'See server log for query details.',
  | 2023-05-19T13:19:04.798-07:00 | position: undefined,
  | 2023-05-19T13:19:04.798-07:00 | internalPosition: undefined,
  | 2023-05-19T13:19:04.798-07:00 | internalQuery: undefined,
  | 2023-05-19T13:19:04.798-07:00 | where: undefined,
  | 2023-05-19T13:19:04.798-07:00 | schema: undefined,
  | 2023-05-19T13:19:04.798-07:00 | table: undefined,
  | 2023-05-19T13:19:04.798-07:00 | column: undefined,
  | 2023-05-19T13:19:04.798-07:00 | dataType: undefined,
  | 2023-05-19T13:19:04.798-07:00 | constraint: undefined,
  | 2023-05-19T13:19:04.798-07:00 | file: 'deadlock.c',
  | 2023-05-19T13:19:04.798-07:00 | line: '1146',
  | 2023-05-19T13:19:04.798-07:00 | routine: 'DeadLockReport'
  | 2023-05-19T13:19:04.798-07:00 | }

Cannot repro. More background reading: https://www.cybertec-postgresql.com/en/postgresql-understanding-deadlocks/


Added NLog Layout support for NatsUrl and Subject

NLog Layout allows you to configure NATS-Target options from config-file like NLog.config or appsettings.json.
Would it be possible to change the license for this project from GPL to Apache (Like NATS) or BSD3 (Like NLog) ?

I moved project to Apache 2.0 License

I've updated the version on nuget.org also to 1.0.1, including your commits
and some typo fixes. Thank you.
On Tue, Sep 3, 2024 at 5:43 PM Rolf Kristensen @.***>
wrote:

Thank you for the merge, and approving the suggested change of license.
—
Reply to this email directly, view it on GitHub
https://github.com/Siqsuruq/NLog-Target.Nats/pull/1#issuecomment-2327185222,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANQRLHXGQLWYVCJJTPABS3ZUX7MVAVCNFSM6AAAAABNQYNZ6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRXGE4DKMRSGI
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Thank you for the quick merges. I have added the nuget-package to list of custom NLog Targets here:

https://nlog-project.org/config/?tab=targets


E2E Tests incorrect in default project

El Capitan

bash-3.2$ ng --version
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
angular-cli: 1.0.0-beta.11-webpack.8
node: 6.5.0
os: darwin x64

Create an app using ng new
change the e2e test from

  it('should display message saying app works', () => {
    page.navigateTo();
    expect(page.getParagraphText()).toEqual('app works!');
  });

to
  it('should **NOT** display message saying app works', () => {
    page.navigateTo();
    expect(page.getParagraphText()).toEqual('app **doesnt** works!');
  });

then run ng e2e
output is:
`bash-3.2$ ng e2e
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.

<EMAIL_ADDRESS>pree2e /Users/pooperpig/projects/Angular 2 Projects/cliTest
 webdriver-manager update

[13:56:58] I/update - chromedriver: file exists /Users/pooperpig/projects/Angular 2 Projects/cliTest
/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_2.22mac32.zip
[13:56:58] I/update - chromedriver: unzipping chromedriver_2.22mac32.zip
[13:56:58] I/update - chromedriver: setting permissions to 0755 for /Users/pooperpig/projects/Angula
r 2 Projects/cliTest/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedrive
r_2.22
[13:56:58] I/update - chromedriver: v2.22 up to date
[13:56:58] I/update - selenium standalone: file exists /Users/pooperpig/projects/Angular 2 Projects/
cliTest/node_modules/protractor/node_modules/webdriver-manager/selenium/selenium-server-standalo
ne-2.53.1.jar
[13:56:58] I/update - selenium standalone: v2.53.1 up to date

<EMAIL_ADDRESS>e2e /Users/pooperpig/projects/Angular 2 Projects/cliTest
 protractor "./protractor.conf.js"

[13:56:59] I/direct - Using ChromeDriver directly...
[13:56:59] I/launcher - Running 1 instances of WebDriver
Spec started

  cli-test App
    ✓ should NOT display message saying app works

Executed 1 of 1 spec SUCCESS in 0.02 sec.
[13:57:00] I/launcher - 0 instance(s) of WebDriver still running
[13:57:00] I/launcher - chrome #01 passed

All end-to-end tests pass.         `

Whatever I try, I cannot get the test to fail!

I have tried ngBuild in between changes etc. The text of the test changes ( so it is picking up the changed source) but the tests themselves don't fail.

Appreciate this isn't necessarily an angular-cli issue per se, but its my first port of call!

Thanks! We'll be in touch soon.

for me the same. i am using the webpack 1.0.0-beta.11-webpack.8 version.
ng test works
ng e2e does not work, i see in a flits the word data; in the browser url bar and then i always get the result test passed.

+1

https://github.com/angular/protractor/issues/3505

https://github.com/angular/angular-cli/issues/1981#issuecomment-246112106
On Mon, Sep 12, 2016 at 5:30 AM, Hans<EMAIL_ADDRESS>wrote:

Closed #1977 https://github.com/angular/angular-cli/issues/1977 via
#2054 https://github.com/angular/angular-cli/pull/2054.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/angular/angular-cli/issues/1977#event-785428779, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADg493DOcXnp5geL5XoLia_bYrUApxQoks5qpMdMgaJpZM4J0uXX
.


add more documents

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@f370df3). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #7   +/-   ##
=======================================
  Coverage        ?   89.60%
=======================================
  Files           ?        3
  Lines           ?      125
  Branches        ?        0
=======================================
  Hits            ?      112
  Misses          ?       10
  Partials        ?        3

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 f370df3...bfa6beb. Read the comment docs.


German Skill commands

Hello !
Is there a german "vocabulary-book"  for the Skill ?
I found some thread here about the Channel-Controller and some works for me.
I wonder if there is a commandlist for the playback controller.
Best regards from Northern Germany
Martin

Can you please write a link to that Website ? I haven´t found ist yet.
I tried several Commands and they seem to be very inconsistant, which is uncomfortable to rememember.
e.g.
...schalte Fernseher EIN/AUS  (switch TV on/off)
...schalte Fernseher Programm 5  (switch TV program 5)
...Fernseher Lautstärke stummschalten (TV mute)
...schalte Fernseher lauter (switch TV louder)
...Ein Kanal vor/zurück auf Fernseher (one Channel up/down on TV)
...wechsel auf Fernseher den Kanal zu ZDF (change on TV the channel to ZDF)
………………..
sometimes TV on beginning, sometimes at the end of the command. It seems to be a bit inconsistant. I am searching for a common Grammar in the possible commands.
I would like to have vocabulary to use the playback-Controller, which I want to use to start and playback timeshift-recording.

https://developer.amazon.com/de/docs/device-apis/alexa-channelcontroller.html
That's the most documentation Alexa has published, its not a lot but that's all there is an they do sometimes make changes without updating. Unfortunately its out of my hands and I don't actually have any control as a skill developer of what the commands actually are


Uncomment 520 retry code

Resolves #17

Regarding https://github.com/scrapy-plugins/scrapy-zyte-api/issues/25, should this be enough (up to 15 minutes of retries), or should we do something else (e.g. allow customizing the retrying parameter of AsyncClient.request_raw, or expose failed requests to middlewares with metadata that reflects the retries done by the client).

As discussed elsewhere, we should make the default retries less aggressive (e.g. 3 retries). In future we could make it more configurable, e.g. like it was in zyte-autoextract library.

$ echo <URL that triggers 520> | zyte-api -
INFO:zyte_api:Loaded 1 urls from <stdin>; shuffled: False
INFO:zyte_api:Running Zyte Data API (connections: 20)
  0%|                                                                                | 0/1 [00:00<?, ?url/s, conn:0.00s, resp:0.00s, throttle:0.0%, err:0+0(0.0%) | success:0/0(0.0%)]ERROR:zyte_api:RequestError: 520, message=, headers=<CIMultiDictProxy('Date': 'Wed, 06 Jul 2022 17:20:08 GMT', 'Content-Type': 'application/problem+json', 'Content-Length': '162', 'Connection': 'keep-alive', 'Retry-After': '60', 'Vary': 'Accept-Encoding', 'Content-Encoding': 'gzip', 'Strict-Transport-Security': 'max-age=0; includeSubDomains; preload')>, body=b'{"type":"/download/temporary-error","title":"Temporary Downloading Error","status":520,"detail":"There is a downloading problem which might be temporary. Retry in N seconds from \'Retry-After\' header."}'
  0%|                                                                                | 0/1 [01:43<?, ?url/s, conn:20.68s, resp:0.00s, throttle:0.0%, err:3+1(100.0%) | success:0/1(0.0%)]
INFO:zyte_api:
Summary
-------
Mean connection time:     20.68
Mean response time:       0.00
Throttle ratio:           0.0%
Attempts:                 4
Errors:                   100.0%, fatal: 1, non fatal: 3
Successful URLs:          0 of 1
Success ratio:            0.0%

INFO:zyte_api:
API error types:
[('/download/temporary-error', 4)]
INFO:zyte_api:
Status codes:
[(520, 4)]
INFO:zyte_api:
Exception types:
[]

It looks good for one request; how does it look like if another request is successful?

$ echo "<URL that triggers 520>
> https://toscrape.com" | zyte-api -
INFO:zyte_api:Loaded 2 urls from <stdin>; shuffled: False
INFO:zyte_api:Running Zyte Data API (connections: 20)
  0%|                                                                                | 0/2 [00:00<?, ?url/s, conn:0.00s, resp:0.00s, throttle:0.0%, err:0+0(0.0%) | success:0/0(0.0%)]{"url": "https://toscrape.com/", "browserHtml": "<!DOCTYPE html>\n        <meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\">\n        <title>Scraping Sandbox</title>\n        <link href=\"./css/bootstrap.min.css\" rel=\"stylesheet\">\n        <link href=\"./css/main.css\" rel=\"stylesheet\">\n    \n    \n
\n
\n

\n
\n                    \n
Web Scraping Sandbox
\n
\n
\n\n
\n

\n
\n
Books
\n
A fictional bookstore that desperately wants to be scraped. It's a safe place for beginners learning web scraping and for developers validating their scraping technologies as well. Available at: books.toscrape.com
\n
\n                        \n
\n
\n
\n

Details
\n
Amount of items 	1000
\n
Pagination 	✔
\n
Items per page 	max 20
\n
Requires JavaScript 	✘
\n

\n
\n
\n
\n\n
\n

\n
\n
Quotes
\n
A website that lists quotes from famous people. It has many endpoints showing the quotes in many different ways, each of them including new scraping challenges for you, as described below.
\n
\n                        \n
\n
\n
\n

Endpoints
\n
Default	Microdata and pagination
\n
Scroll 	infinite scrolling pagination
\n
JavaScript 	JavaScript generated content
\n
Delayed 	Same as JavaScript but with a delay (?delay=10000)
\n
Tableful 	a table based messed-up layout
\n
Login 	login with CSRF token (any user/passwd works)
\n
ViewState 	an AJAX based filter form with ViewStates
\n
Random 	a single random quote
\n

\n
\n
\n
\n
\n    \n\n", "echoData": "https://toscrape.com"}
 50%|█████████████████████████████████████████                                         | 1/2 [00:08<00:08,  8.67s/url, conn:8.66s, resp:8.66s, throttle:0.0%, err:0+0(0.0%) | success:1/1(100.0%)]ERROR:zyte_api:RequestError: 520, message=, headers=<CIMultiDictProxy('Date': 'Thu, 07 Jul 2022 11:38:30 GMT', 'Content-Type': 'application/problem+json', 'Content-Length': '162', 'Connection': 'keep-alive', 'Retry-After': '60', 'Vary': 'Accept-Encoding', 'Content-Encoding': 'gzip', 'Strict-Transport-Security': 'max-age=0; includeSubDomains; preload')>, body=b'{"type":"/download/temporary-error","title":"Temporary Downloading Error","status":520,"detail":"There is a downloading problem which might be temporary. Retry in N seconds from \'Retry-After\' header."}'
 50%|████████████████████████████████████████                                        | 1/2 [01:43<01:43, 103.44s/url, conn:18.99s, resp:8.66s, throttle:0.0%, err:3+1(80.0%) | success:1/2(50.0%)]
INFO:zyte_api:
Summary
-------
Mean connection time:     18.99
Mean response time:       8.66
Throttle ratio:           0.0%
Attempts:                 5
Errors:                   80.0%, fatal: 1, non fatal: 3
Successful URLs:          1 of 2
Success ratio:            50.0%

INFO:zyte_api:
API error types:
[('/download/temporary-error', 4)]
INFO:zyte_api:
Status codes:
[(520, 4), (200, 1)]
INFO:zyte_api:
Exception types:
[]

Thanks @Gallaecio!


Issue when used with DSPAutosorter

When used with DSPAutoSorter, items are automatically pushed into delivery slots, even when DeliveryFirst=false. Behavior only appears to happen when both mods used together.

Config option SortToDelieverySlots has been added in 1.4.2. The default value is now false.


[Feature] Enhance supported platforms

Search before asking

[X] I searched the issues and found no similar issues.

Component
KFP workflows
Feature
We have validated the execution of the data-prep-kit kind deployment on several platforms, see below, and have faced the Ray Job execution issues on the others. We need to extend supported platforms:

Operating System
Container Agent
Support
Priority
Comments

RHEL 7
any
-
-
Kind doesn't support RHEL 7

RHEL 8

RHEL 9.4
Docker
Yes
-

RHEL 9.4
Podman
No
?
Issues with Ray job executions

Ubuntu 24-04
Docker
Yes
-
(Validate nginx deployment)

Ubuntu 24-04
Podman

?

Windows WSL2
Docker
Yes
-

Windows WSL2
Podman

?

MacOS amd64
Docker
Yes
-

MacOS arm64
Podman
No
?
Issues with Ray job executions

In the meantime we don't test investigate other OS and other container agents, such as Rancher, or colima.
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

my plan is to add a similar table to the project documentation.


fix to make hasIdle Boolean

Yes, this is just a nitpick. 😝
But, I want hasXXX to returns Bool. IMO.
What do you think?

Haha, I disagree! I prefer truthy values in general; much more flexible and has the same result. Maybe we should rename the var instead? Imo it doesn't really matter tho, just internals haha

@yoshuawuyts Thanks!
We don't need to rename for the same result.:)
Just no problem!


fix ci

Codecov Report

Merging #95 (2925617) into master (b500645) will increase coverage by 0.13%.
The diff coverage is 18.18%.

@@            Coverage Diff             @@
##           master      #95      +/-   ##
==========================================
+ Coverage   51.75%   51.88%   +0.13%
==========================================
  Files          83       83
  Lines        1227     1220       -7
  Branches       45       48       +3
==========================================
- Hits          635      633       -2
+ Misses        592      587       -5

Impacted Files
Coverage Δ

...n/scala/org/bitlap/zim/server/api/ZimUserApi.scala
100.00% <ø> (ø)

...m/server/configuration/AkkaHttpConfiguration.scala
11.11% <ø> (ø)

...in/scala/org/bitlap/zim/server/util/FileUtil.scala
0.00% <0.00%> (ø)

...n/scala/org/bitlap/zim/tapir/ApiErrorMapping.scala
10.00% <0.00%> (ø)

...main/scala/org/bitlap/zim/tapir/ApiJsonCodec.scala
41.89% <40.00%> (+0.11%)
:arrow_up:

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 e0f8be6...2925617. Read the comment docs.


[v7] Table 100% width

I use useBlockLayout and I don’t understand how to make the table stretch 100% of the width of the parent. In theory, the width of the columns should be adjusted as it was at V6

Out of the box, no, it does not behave like v6, since it is not using a flexbox model. useBlockLayout uses inline-block divs with precise widths. You can stretch the table container itself to take up the full width, but in a block or absolute layout, your columns will not grow automatically. The only way I know of to reliably do that is using the default html-table-element layout.

Out of the box, no, it does not behave like v6, since it is not using a flexbox model. useBlockLayout uses inline-block divs with precise widths. You can stretch the table container itself to take up the full width, but in a block or absolute layout, your columns will not grow automatically. The only way I know of to reliably do that is using the default html-table-element layout.

but then I can not set the width of the columns?

Yes you can. width can be set on columns, and also, if you are using resizable columns, minWidth and maxWidth are also used

Good. I’ll think about how to do it better. It’s not clear from the documentation how inline-block divs affects performance. Please explain)

useBlocklayout is a plugin hook that adds support for headers and cells to be rendered as inline-block divs (or other non-table elements) with explicit width. Similar to the useAbsoluteLayout hook, this becomes useful if and when you need to virtualize rows and cells for performance.

Yes you can. width can be set on columns, and also, if you are using resizable columns, minWidth and maxWidth are also used

Good. I’ll think about how to do it better. It’s not clear from the documentation how inline-block divs affects performance. Please explain)

useBlocklayout is a plugin hook that adds support for headers and cells to be rendered as inline-block divs (or other non-table elements) with explicit width. Similar to the useAbsoluteLayout hook, this becomes useful if and when you need to virtualize rows and cells for performance.

Yes you can. width can be set on columns, and also, if you are using resizable columns, minWidth and maxWidth are also used

How can i set width without useBlockLayout?

Please refer to this example: https://codesandbox.io/s/github/tannerlinsley/react-table/tree/master/examples/block-layout

@tannerlinsley is there a way to get a full width table (100%) and have cells stretch out to fill out the 100% table?

When you say stretch, that could mean many things. Do you want each cell to grow equally? Do you want them to grow with their original size ratio? Do you want the 1st, 4th and last column to grow equally to fill the empty space?
You can see how that can be interpreted in so many ways. A lot of those ways were handled by the flex layout, since flexbox can do most of that natively, but flexbox calculations get really messed up when you move to column groups, column spans, etc. The alignment can get really off.
If you really really want an HTML-element table layout that will go 100%, then you could try this example. It even supports collapsible cells!
https://codesandbox.io/s/github/tannerlinsley/react-table/tree/master/examples/full-width-table

Thanks @tannerlinsley. I was looking for the default table behavior and styles you'd get with a 100% width table: https://codepen.io/coreybruyere/pen/oNNVzPa
That example works great but now my first column cell which has an expander and an empty th header is also expanding. That entire column should have a max width of 32px:

The columns array
	const MOCK_COLUMNS = React.useMemo(
		() => [
			{
				// Expander cell
				Header: () => null, // No header
				Cell: ({ row }) => {
					// Look for comment property before rendering expander
					return row.original.comment ? (
						<ThemeConsumer>
							{(theme) => (
								<span {...row.getExpandedToggleProps()}>
									{row.isExpanded ? (
										<Icon.Decrease color={theme.colors.base[5]} />
									) : (
										<Icon.Expand color={theme.colors.base[5]} />
									)}
								</span>
							)}
						</ThemeConsumer>
					) : null;
				},
				id: 'expander',
				width: 32 // Arbitrary value to make room for icon - Not working
			},
			{
				Header: 'Test',
				accessor: 'test',
				minWidth: 300
			},
			{
				Header: 'Results',
				accessor: 'results',
				minWidth: 300
			},
			{
				Header: 'Range',
				accessor: 'range',
				minWidth: 300
			}
		],
		[]
	);

The table header with custom, styled components mapping through header groups:
						<TableHeader>
							{headerGroups.map((headerGroup) => (
								<TableRow {...headerGroup.getHeaderGroupProps()}>
									{headerGroup.headers.map((column) => (
										<TableCell {...column.getHeaderProps()}>{column.render('Header')}</TableCell>
									))}
								</TableRow>
							))}
						</TableHeader>

As shown in that example, you can use a column.collapse flag to apply a style that will collapse specific columns to their smallest needed width.

so it's impossible to make table with 100% and fixing some cells?
for example I wan't to make table with 100%, 30vw for first cell, 30 vw for second and rest for others?
in example you just removed useBlockLayout, but only with this you can set custom width to columns.

Technically that is feasible, it's all just a matter of setting it up in your renderer and accepting any tradeoffs that may come with it. For instance, instead of setting up the collapse option like I did above, you could just use width and set each column as best you can.
If you are looking for true column flex though (similar to v6), you'll have to venture down a custom path of using useBlockLayout and flex styles. I don't suggest people do that, since there were a few problems with flex layout that could never be solved, namely cross-browser nested column header alignment and scrollbar offsets from scrollable table bodies.

Im also looking for the same behavior as @OlegBrony.

namely cross-browser

@tannerlinsley  just wanted to add that in case react-table is used in an electon app (as is my case), that wouln't be a problem. Will look how that can be accomplished with useBlockLayout.

Just now I decided to upgrade from V6 to V7. I got everything right but the resize functionality. In V6 when resizing It does not affect other columns but in V7 it does.
React V6: https://giphy.com/gifs/Jpp6HWUT1GR2IJMCSv/fullscreen
React V7; https://giphy.com/gifs/dCR44Nywbz7wDNjwVi/fullscreen
My Code: https://codesandbox.io/s/cool-fermi-6jtgo?file=/src/Table.js
What am I missing?

@Jucesr Hi! Did you solve the problem?

Is there anyway to have a table with 100% of the parent width + the resizing feature ?
I posted this question on Stackoverflow here.


@unocss/nuxt package does not work when autoImports are disabled [with repro]

The error:
at eval (./virtual:nuxt:/home/projects/github-4d1z2m/.nuxt/unocss.mjs:3:32)
at async ViteNodeRunner.directRequest (file://./node_modules/vite-node/dist/client.mjs:301:5)

https://stackblitz.com/edit/github-4d1z2m?file=nuxt.config.ts

To fix, import defineNuxtPlugin here: https://github.com/unocss/unocss/blob/main/packages/nuxt/src/index.ts#L45
Workaround: set autoimport: false in plugin settings:
  unocss: {
    autoImport: false,

and import manually import 'uno.css';

You didn't install @unocss/nuxt package. Please guide our docs. https://github.com/unocss/unocss/blob/main/packages/nuxt/README.md#installation

@zyyv Yeah, reproduction is missing the @unocss/nuxt package but the issue mentioned in the title appears after you install it. Reopening it to track progress 🙏

Hello
Same error in a custom nuxt module.
Can't build the playground.
Adding import { defineNuxtPlugin } from '#app' in index.mjs > defineNuxtModule > addPluginTemplate fix the issue.
Itt was working with 0.46.5


API loading become very slow after updating to latest version of both VSF and VSF-API.

I m still on developing mode, testing in local docker server, grabbing data from magneto host on AWS.
Not sure why the API loading time is much longer than before.
I have also enable PayPal extension and not sure is it the reason too.

Thanks for noticing us however it’s very hard to help: please try to be more specific. Please do also check the Elastoc and Magento response times accordingly

Thank you for your hints, let me try to gether more information.
At least I know this is not a common issue.


Serialize strict/sloppy mode of functions

Currently strict mode directives are ignored by Livepack.
e.g. A function defined in a file with a global 'use strict' directive is not serialized to a strict mode function. Currently, all functions in CJS output are sloppy-mode, and all are strict mode in ESM output.
When serializing functions defined in sloppy-mode CommonJS files to ESM output, it's impossible to produce sloppy-mode output. Either must accept this minor difference between input and output, or implement sloppy mode emulation. A few features of sloppy mode are not possible to emulate in strict mode e.g. eval() within a with () {} block.
Most input code will be strict mode so a quick solution for majority of cases would be to make all CommonJS output strict mode.

There is an escape hatch from strict mode - new Function(). Sloppy-mode functions could be included in ESM output by using it.
Input (CommonJS, not strict mode):
module.exports = function() {
  delete Object.prototype; // This would throw in strict mode
  console.log('it did not throw');
};

Output (ESM format, strict mode):
export default new Function("delete Object.prototype; console.log('it did not throw');")

External scope vars can also be injected in (see #136 for a mechanism to do this).


Ubuntu support?

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I remove or skip any mandatory* field

Checklist

[X] I'm asking a question and not reporting a bug or requesting a feature
[X] I've looked through the README
[X] I've verified that I'm running yt-dlp version 2022.11.11 (update instructions) or later (specify commit)
[X] I've searched the bugtracker for similar questions including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Please make sure the question is worded well enough to be understood
Ubuntu 18.04 not supported anymore because lastest Python there is 3.6.x?
Provide verbose output that clearly demonstrates the problem

[ ] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
No response

Python 3.6 support was dropped for further development. Would you consider to install a higher Python version or take a look into pyenv?

Or, use the standalone executable


[rewrite] Case-insensitivize method in m.request

Not against this PR (I'm actually rather neutral), but I'd like to note that the corresponding HTTP methods themselves are technically case sensitive. Just a little info bit on this.


⚠ Samsung has degraded performance

In a52fd07, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2034 ms

Resolved: Samsung performance has improved in 1d34960.


Unemployment Analysis

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
The Unemployment Analysis feature is designed to provide insights and detailed analytics on unemployment data. This feature leverages data from various sources, including government databases, surveys, and economic reports, to analyze trends, patterns, and factors influencing unemployment rates.
Use Case

Policy Making: Governments and policymakers can use this feature to design and implement effective employment policies.
Economic Forecasting: Economists and financial analysts can predict future unemployment trends and their impact on the economy.
Business Strategy: Businesses can understand labor market conditions, aiding in strategic planning and decision-making.
Academic Research: Researchers can use the data for academic studies related to labor economics and social sciences.
Job Market Analysis: Employment agencies and job portals can analyze job market conditions to better match job seekers with employers.

Benefits

Informed Decision-Making: Provides accurate data to support policy and business decisions.
Trend Analysis: Helps identify trends over time, aiding in long-term planning and forecasting.
Targeted Interventions: Allows for the identification of specific demographics or regions with high unemployment rates, enabling targeted interventions.
Resource Allocation: Optimizes the allocation of resources for job creation programs and unemployment benefits.
Economic Stability: Contributes to economic stability by helping to mitigate the adverse effects of high unemployment.
Enhanced Research: Supports academic and market research with comprehensive data and analysis tools.
Competitive Advantage: Businesses gain a competitive edge by understanding labor market dynamics and adapting accordingly.

Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Please assign this issue to me @sanjay-kv

Please assign this issue to me @sanjay-kv


SOCIAL-3234: improving returned load size from /Install/installstat.log....

...resources.txt endpoint
I added two minor fixes as well

formatting installer log date as yyyyMMdd instead of yyyyMd
made installer log entries date/time stamp local (same as regular logs) instead of UTC.

can you please clone the social ticket as a platform ticket so we have a valid public jira to associate this with

Here is the Platform Jira for this issue: https://dnntracker.atlassian.net/browse/DNN-6746

thanks, i'll review and merge tomorrow

merging into development and cherrypicking into release/7.4.1


Add link to this github

I suggest a button (github icon) to go to here.

Why we need this button? What's use case for this button?
Most users even don't know what github is.
When you suggest a feature, focus on use cases. I would like this button for my purposes, but my use cases is not relative to a Linguist users use cases. We can't add buttons for few users. Especially if the button will confuse another users.
If you can explain why another users will need this button, we could implement it.

In your extension design, there is no link to reach you, for the user get more information about the extension, post bugs report and feature requests. Every time I need to get here, it’s tedious. Most extension offers a link to website or github.

It make sense.
A popup must contains only a most important UI controls, so it's not a place for link to a github, but i would place a link to a github to a options page. I will create section "support" for that purpose

@Fred-Vatin is it would useful for your use case? Is it would solve problem you have?
I see some reasons for me, but i'm interesting your use case.
For what you need a link to a github?

I think most people expect an about section where to find some information about the tool : version, contact, etc. Anℹ icon in the main UI would be straightforward for the user. He would know inherently where to go to find information and support links.
Unless you have another way to get feedback from users, this github is appropriate to feature in this section.


Supporting RFC

What problem does this feature solve?
Evan recently implemented several features into vue-next/compiler-sfc, among them is <script setup>, which has already been introduced to vite, but doesn't seem to be supported by vue-cli just yet. Introducing this feature to vue-cli will help with the adoption of such feature to a wider audience.
What does the proposed API look like?
All possible variants (in JS, or TS) have already been described here as part of the RFC.

Supported in the latest version.
If you encounter any bug, please raise an issue in the vue-loader repository.


The output result of _flash_attn_backward in flash_attn_triton.py is random

I use flash attention to train my model multiple times, and get different results when use same seed.
The reason is there will be different results each time when calling _flash_attn_backward.
Here is my code appending in flash_attn_triton.py to confirm it:
if __name__ == "__main__":
    batch_size = 32
    seqlen = 1024
    nheads = 32
    headdim = 128
    torch.manual_seed(233)
    q = torch.rand((batch_size, seqlen, nheads, headdim), dtype=torch.bfloat16, device="cuda")
    k = torch.rand_like(q)
    v = torch.rand_like(q)
    bias = torch.rand((1, nheads, seqlen, seqlen), dtype=torch.bfloat16, device="cuda")
    q, k, v = [x if x.stride(-1) == 1 else x.contiguous() for x in [q, k, v]]
    o, lse, softmax_scale = _flash_attn_forward(
        q, k, v, bias=bias, causal=True, softmax_scale=None)
    do = torch.rand_like(o)
    with torch.inference_mode():
        dq = torch.empty_like(q)
        dk = torch.empty_like(k)
        dv = torch.empty_like(v)
        _flash_attn_backward(do, q, k, v, o, lse, dq, dk, dv,
                                bias=bias, causal=True, softmax_scale=None)
    t = {
            "dq" : dq,
            "dk" : dk,
            "dv" : dv
        }
    print(t)
    if False: #True when run in first time
        torch.save(t, "t0.pt")
    t0 = torch.load("t0.pt")
    for key in ["dq", "dk", "dv"]:
        print(torch.abs(t0[key] - t[key]).max())

The reuslt:
...
tensor(3.8147e-06, device='cuda:0', dtype=torch.bfloat16)
tensor(0., device='cuda:0', dtype=torch.bfloat16)
tensor(0., device='cuda:0', dtype=torch.bfloat16)

The backward is non-deterministic because we use atomic adds. This is expected.

The backward is non-deterministic because we use atomic adds. This is expected.

Thank you for reply. May I ask if there is any solution? The inability to reproduce the experiment has caused some difficulties for our team.

Yes there'll be a "deterministic" option later on (hopefully in 2-3 weeks, but I can't promise). The tradeoff is that it'll be slower (potentially quite a bit slower for long sequences).

Yes there'll be a "deterministic" option later on (hopefully in 2-3 weeks, but I can't promise). The tradeoff is that it'll be slower (potentially quite a bit slower for long sequences).

Great! Thank you so much. I really appreciate it and I'm looking forward to your solution.

The backward is non-deterministic because we use atomic adds. This is expected.

Today I find it is also random in flash attention2, is this expected?

Yes

There's an option for deterministic bwd in v2.4.1.


[Feature Request] Logging own info as the app does for other users

Explain in detail what your suggested feature would be used for.
I suggest an ability for VRCX to log your own info. Everything that other players have now but you don't. Examples: status and bio changes, online/offline timestamp, avatar switches.
Describe how it would look if it requires a UI.
Just use the same parts of the UI, but with your username and/or as "You"
Explain why people would want to use it.
Could be useful for remembering any stuff you did before

Duplicate, due to how VRCX works internally it requires a lot of work https://github.com/vrcx-team/VRCX/issues/318


Add service filters download and compute to the existing filters

Fixes #814 .
Changes proposed in this PR:

add service access type filters download and compute to the existing filters

All works nicely. But here we should look into the duplication Codeclimate complains about, as accessType and serviceType are essentially doing the same. So maybe we can come up with only one handler for serviceType instead of separating this into 2 things with which we then do exactly the same with minimal differences

Sure, I'll manage it right now.

Maybe some space between the two categories ? Might look a bit better.

Not sure how to refactor more since we use 'serviceType'  and 'accessType' filters both separate and together, if for example we want all datasets with compute access type. So I think we need to differentiate them in order to obtain a proper search query. What do you guys think?

I think we can change a little bit how those filters buttons work. Right now for example if we take in consideration the access type either you have no access type selected or have all selected you get the same result. We could change that, either to be able to select only one and if no one selected to get both, or have them both selected by default and if deselect them you won't get any asset.

Functionality wise works great, maybe we should try and tackle the issues mentioned above. Another thing that we need to decide on is if we will have the new added filters on the profile's published assets page where we rely on the existing filters updated components in this PR, otherwise we will have to handle that in another manner.

new added filters on the profile's published assets page...

yes! They were one of the problems I encountered when trying to improve assets loading over in #841 and would be a good candidate to replace them with js filtering. That is already kinda prepared as the ProfileProvider already holds all published assets https://github.com/oceanprotocol/market/pull/841/files#diff-2fd7fca45bccc84bae93cf604acfb3ee47fa57584a37e7c19b3a543869fcdc13R167-R171.
This way the filter mechanism in this PR would be kept for only search, which probably prevents the component from getting more complex with #774


[Enhancement] Make these two configurations dynamically modifyable

Why I'm doing:
What I'm doing:
Make be config max_length_for_to_base64 and max_length_for_bitmap_function modifyable.
What type of PR is this:

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

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

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

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

[ ] This is a backport pr

Bugfix cherry-pick branch check:

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

[x] 3.3
[x] 3.2
[x] 3.1
[x] 3.0
[x] 2.5

    if (bitmap_ptr->cardinality() > config::max_length_for_bitmap_function) {
        std::stringstream ss;
        ss << "bitmap_to_string not supported size > " << config::max_length_for_bitmap_function;
        throw std::runtime_error(ss.str());
    }

possibly the size in error message differs from the actual length in if statement, if there is a runtime change in between.

Good suggestion, Fixed.


Low-level state changes

If you call Remove for an Added entity its state gets set to Detached. See #251 and #265. However, the same is true for setting the entity's state to Deleted--it actually becomes Detached. Should setting the state honor the state passed, while the Remove method does something different? Or is it better to be consistent, in which case maybe the SetState method should be called ChangeState and documented appropriately? Also, see #1246 since this could result in setting the state to Unchanged but getting Modified.

Happy with the behavior we have


It would be realy helpfull, if the README.md gave an overview of the accepted .env variables

In the README.md only the default env values are mentioned. This is not very useful, as there is no mention of what values are accepted.
A list of all possible env values should be given.

Hi @redRolf ! I'm trying to understand what you are trying to get here.
There are three different sections in the README file: one for the Apache vars, another for Nginx vars, and the last for ModSecurity vars. Can you give me an example of what you will expect from those? I mean... that's the whole list of possible env values.

Hi @fzipi I do apologise for the bad quality of my issue. Thank you for your quick response. The section I am referencing is the ModSecurity ENV Variables I found myself repeatedly wondering what values are accepted. There are some that are obvious like directory paths. But there are others where I then had to do research on what values are accepted. Here are some examples:

MODSEC_AUDIT_LOG_FORMAT (Default: JSON), the other accepted value here is Native but there is no way for me to know this.
MODSEC_AUDIT_ENGINE (RelevantOnly), here it would be good to know, what is relevant only means and what other values are accepted here.
MODSEC_RULE_ENGINE (Default: on), here the values DetectionOnly and off are also accepted, where the latter is trivial but DetectionOnly is not.

It would be great to have either just a list of the accepted values. This would make it more comprehensive and not put me in the position where I need to start looking elsewhere for an explanation of what values are accepted.
If a list or documentation does exist, it would also work for me if you just linked that documentation.

Now, that makes more sense :)
Truly sorry, probably we are way too used to the config of modsecurity to describe those, but you make a perfectly valid point. Will extend the readme with values and pointers to the modsecurity wiki.

@redRolf Can you take a look at the linked PR and see if it works for you?

@fzipi Wow that was quick, I barely got coffee in that time 😍  Yes the changes work for me. Thank you for the quick help :)

Thanks!