Sourcemap and Breakpoint Fixes

Fixes source maps so they work properly when run in concat chunks, pages, or dynamic chunks.
Updates files names in dev mode to be constant so breakpoints will persist across page refreshes.
Fixes #2990

The disable cache feature in dev tools is on by default. Also cache
management in dev mode is something devs should be aware of. It was one of
the first things I learned back in the “old days” :)
On Tue, Oct 17, 2017 at 1:43 PM Vlad Frolov<EMAIL_ADDRESS>wrote:

@frol commented on this pull request.
In server/render.js
https://github.com/zeit/next.js/pull/3121#discussion_r145219193:

@@ -93,11 +93,9 @@ async function doRender (req, res, pathname, query, {
}

const docProps = await loadGetInitialProps(Document, { ...ctx, renderPage })

// While developing, we should not cache any assets.
// So, we use a different buildId for each page load.
// With that we can ensure, we have unique URL for assets per every page load.
// So, it'll prevent issues like this: https://git.io/vHLtb
const devBuildId = Date.now()

// Hard coding build id to development to allow for breakpoints to be set across
// page reloads.
const devBuildId = 'development'

Won't this bring the mentioned issue #2014
https://github.com/zeit/next.js/issues/2014 back?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zeit/next.js/pull/3121#pullrequestreview-69987291,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAL_Jpju2Pt__PkVrF1FRwTADOk6VLYLks5stPUSgaJpZM4P8Z1r
.

But headers also provide better fixes that allow both to live together.
On Tue, Oct 17, 2017 at 2:36 PM Kevin Decker<EMAIL_ADDRESS>wrote:

The disable cache feature in dev tools is on by default. Also cache
management in dev mode is something devs should be aware of. It was one of
the first things I learned back in the “old days” :)
On Tue, Oct 17, 2017 at 1:43 PM Vlad Frolov<EMAIL_ADDRESS>wrote:

@frol commented on this pull request.
In server/render.js
https://github.com/zeit/next.js/pull/3121#discussion_r145219193:

@@ -93,11 +93,9 @@ async function doRender (req, res, pathname, query, {
}

const docProps = await loadGetInitialProps(Document, { ...ctx, renderPage })

// While developing, we should not cache any assets.
// So, we use a different buildId for each page load.
// With that we can ensure, we have unique URL for assets per every page load.
// So, it'll prevent issues like this: https://git.io/vHLtb
const devBuildId = Date.now()

// Hard coding build id to development to allow for breakpoints to be set across
// page reloads.
const devBuildId = 'development'

Won't this bring the mentioned issue #2014
https://github.com/zeit/next.js/issues/2014 back?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zeit/next.js/pull/3121#pullrequestreview-69987291,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAL_Jpju2Pt__PkVrF1FRwTADOk6VLYLks5stPUSgaJpZM4P8Z1r
.

@frol pulled in the explicit no-cache headers from #2680 to help avoid any issues if not using dev tools, etc.

Had to revert the PR:
https://github.com/zeit/next.js/issues/3134
https://github.com/zeit/next.js/issues/3135

I can reproduce #3134. Appears to be timing issue between the combine assets plugin and the uglify plugin. Investigating fix there.
I have not been able to reproduce #3135, but have subscribed and will note if the reporter provides more information.

Thanks @kpdecker ❤


Add Country as detailed metric

Seeing the languages of users is nice, but it would be more helpful to know where visitors are coming from. To do this in a privacy focused way you could get the country from the IP address with something like geoip-country and save only that to the DB. With this module everything would happen locally and you wouldn't need a third party service.

I created a PR (#105)  that adds the country as a metric

Thanks a lot 👏 I hope I can take a closer look at it soon.

Has this feature been added? My version does not have.

The feature hasn't made it into Ackee. You can read more about that decision in the PR: https://github.com/electerious/Ackee/pull/105#issuecomment-616098682


Need to dynamic actions in order to support code splitting

#435 showed its possible to write an HoA to encapsulate state+action+view into module and https://github.com/hyperapp/hyperapp/issues/435#issuecomment-340067619 showed its possible to load lazy said module, except for the module actions.
Motivation
Code splitting.
Problem
There is currently no way to add actions dynamically.
Possible Solutions
1. Include addAction action in app

solves the problem in the most direct way

2. Include loadModule action in app

solves the bigger issue at the same time

3. Merge the concepts of state and actions

state is expected to change, so what if we just put state and actions in the same place?
replace state and actions with root, keep view
allow root to hold both data and functions. functions would take in root and slice the tree as it does now
functions return and object which will merge into the subtree of where it lives, it can return both data and more functions (aka actions!)
since actions don't need to be there at init time, then modules don't need to exist either! modules can be put directly on the root or added during init or add lazily later

Option 3 is most interesting to me since it removes even more concepts from Hyperapp.

@Pyrolistical This is currently impossible given we don't have stateful components. It could work in userland if you have different apps talking to each other, which is not unheard of, but not what you want probably.
I would prefer not having code splitting than implementing it in any of the proposed ways, sorry. But there's still hope, we just need to think more about it.
Dynamically loading views, when using e.g., a router, is feasible and I can see how this could be useful, given that views and components can make up a very large chunk of your app bundle too.

I don't understand your stateful components comment. What does stateful components have to do with this?

AFIK, in React you can dynamically load components and its child components with all its moving parts, and setup codesplitting for that. In Hyperapp you can't because there is only one app and a single entry point.
Honorable mention: Have you looked into HOAs?

@Pyrolistical How about this?
app(load => ({
  actions: {
    reactorStart() {
      import("/remote-module").then(load)
    }
  }
}))

???? isn't app(function) the old HoA style that has been removed?

we don't need stateful components for code splitting, we already have modules, state slice, its just dynamic actions that is the blocker

@Pyrolistical Hey, so what about this? It's just pseudo-code.
app(load => ({
  actions: {
    myAction() {
      import("/remote-module").then(load)
    }
  }
}))

yep, that would work

@Pyrolistical If this ever lands here, I think I would prefer something along those lines. It doesn't have to be an exact match, but close.

@Pyrolistical isn’t this the same issue as #431?
Would my suggestion from over there solve this too?

I think #431 and this issue have different motivation.

Yes, actually, #431 is about dynamically wiring actions to a sub-state of the slice, but not actually modifying the action tree. This is about adding a new module to the app dynamically. My bad.

Hmm. I may not be fully grasping the use case here, but if we're talking about code-splitting (so the async loading of modules/parts), then each dynamically loaded module would have to be quite independent (since it can't know for sure if any of the other modules are loaded or not).
My approach in such a scenario would probably be to have each module as it's own  app({..}). One master app to manage the fetch/load/initializing of sub apps.

@zaceno my use case is to be able to defer loading of whole subsections of site, just not split up a single app into multiple loads.

@Pyrolistical, I see well that even more emphasizes that the different subsections/modules are quite independent, no?
Is there a reason you would want to have the subsections together in a single app({...})?

Interesting, that would require out of band communication to pass stuff between apps? That's pretty annoying.
Also, code splitting subsections of whole sites is just the MVP, where I really want to get to is being able to load tiny individual modules

It makes sense to me to be able to add dynamic actions especially for lazily instantiated modules, where you want to have actions scoped to each module. As opposed to a 'many' #435 or 'instance' #434 controller with substates
Plus it seems like overkill to force nested apps to implement widgets..?
If that's the best way to go about it, how would you go about joining the apps together?

@snalld @Pyrolistical @zaceno We should work on a way to code split based on routes, instead of creating an intricate solution to a non-problem.

Plus it seems like overkill to force nested apps to implement widgets..?

@snalld @Pyrolistical -- perhaps you're right! It's just how I would solve it, given that hyperapp doesn't support dynamically adding actions (which seems to me a bit at odds with the declarative philosophy of hyperapp anyway)

However, if that's the best way to go about it, how would you go about joining the apps together?

Well... You could render each sub-app in a components oncreate lifecycle event.
Each app({...}) call returns the action-callers of the app, so you could wire up a parent app to control child apps through that.
You may use an external event bus to allow child->parent communication.
It's quite dated now (I wrote it for an older version of hyperapp) but perhaps https://github.com/zaceno/hyperapp-nestable could provide some ideas as well.
I realize this all feels like a "hack" on top of hyperapp. But maybe that's not so wrong. I don't know tbh.

@zaceno  I suppose what feels wrong to me about that is that the child apps could load their own data which means the parent app doesn't have the only source of truth. On the other hand maybe that's ok (twitter feed widget?)

Each app({...}) call returns the action-callers of the app, so you could wire up a parent app to control child apps through that.

How do you suggest storing the action-callers in a parent app? I want to give this a try but I'm not sure how you'd go about it...

@snalld I suppose what feels wrong to me about that is that the child apps could load their own data which means the parent app doesn't have the only source of truth.

I don't recommend or encourage writing apps this way. You are of course, free to try, but it's out of the scope of what I set out to do with hyperapp and definitely in the upside-down. You've been warned. Welcome to the fringe zone.

@JorgeBucaran haha I'll tread carefully...
So just to clarify, what's your favourite way to tackle the widgets use case?

@snalld We return actions from the app() because otherwise there is no way to communicate with your app from the outside. The discussed scenario is usually a legacy system sending messages (calling actions) to hyperapp.
What's the widget use case again?

Being able to lazily instantiate a module that has its own actions (register actions dynamically) rather than have a module with substates and a general set of actions that
@JorgeBucaran it's very possible I'm not across the inner workings of HA to be getting involved in this particular discussion haha

@snalld Being able to lazily instantiate a module that has its own actions (register actions dynamically) rather than have a module with substates and a general set of actions that

In that case, using @zaceno's recommendation is one way to go about it right now. In the future something like this might be possible though.

Ah ok missed that bit
Tbh I think maybe I'm over complicating things with the whole dynamic modules thing, probably just need to rethink how to achieve what I want more declaratively

@snalld I thought we were just ideating. This is all future business. In reality, you can't possibly need any of this right now. Also, my comment here. 😄

https://github.com/hyperapp/hyperapp/issues/439#issuecomment-341001122 :

We should work on a way to code split based on routes, instead of creating an intricate solution to a non-problem.

We shouldn't do code-split on routes. It's not flexible. What if I want to make an Electron app with Hyperapp, it would limit the view tremendously. Or I have to make routes inside the electron stuff just to keep it working.
I'm really a fan of the Polymer way of routing. They just have a component where it switches components based on properties. And those properties can potentially come from a route, but also from state or an event or something.
What I'd like to see is an atomic component which has access to the full application state, but has it's own actions and views, which can be dynamically loaded, based on the users actions.

@Alber70g Thanks for the write up. Could you show us some code or pseudo code of how you think the API would look like?

@Alber70g @Pyrolistical If #477 is implemented, actions can return new actions. Wouldn't that fix this?

yes it would! let's talk more in #477

@Pyrolistical I have a contrived example with dynamic actions for the models branch with a few updates.
Here is the code:

const model = {
  count: 0,
  new: () => store => ({
    count: store.count - 1,
    mult: () => store => {
      return {
        count: store.count * 10
      }
    }
  }),
  up: () => store => ({ count: store.count + 1 })
}

const view = store => (
  <main>
    <h1>{store.count}</h1>
    <button onclick={store.up}>Increment</button>
    <button onclick={store.mult}>Multiply ({store.mult ? "Ready" : "Not Ready"})</button>
    <button onclick={store.new}>Add Dynamic Action</button>
  </main>
)

app(model, view)

Alas, we didn't get this since #490 was merged over #484.
The new combine concept is great for modularization of a project, but is still statically combined before the app is running.

@Pyrolistical Yes, this is a non-trivial problem to solve elegantly with the current architecture so I don't know if it will be possible. I'd be happy to help you out if you want to work on this, but I don't think I'll have much time to work on this exclusively myself since it does not affect me directly and there's so much other stuff to do.


Mo cma es

The tests fails because Bayesian Optimisation makes some assumption on the shape of the losses array. We should detect if there is multiple losses and not run the Bayesian optimisation sampler.

No it was a newly added MOCMAES test that failed because of the assumption that insert_complementary was call for each result.

With scikit-learn 0.19, the tests seems to fail for Bayes.


Mission replays can't be viewed from the replay menu.

The game crashes if you save a replay of a mission and then view it from the replay menu. I tried it with the mission Stake Out, and when I save the replay, then exit the mission and go to the replay menu to view it, it crashes to desktop, displaying the following message. I'm using the latest release.

And here's the crash dump:
REDRIVER2.zip

Fixed in e3f17a9


Broken links

This fix resolve

broken links in documentation (Indonesian and Korean)
misplaced markdown braces (that was generated web errors)
fix a few links in the blog (English)

It will be great to have "hacktoberfest" labels =)

Hi @butuzov
Thanks for submitting this.
This pull request touches several different parts of the website. Would you be willing to resubmit this as different pull requests?
Ttypically: a change to the blog posts would be separate from non-blog changes, and each pull request should only cover a single localization (eg Bahasa Indonesia).

Hi @sftim
No problem.
Can I combine blog related changes in one PR?

combine blog related changes in one PR?
That should be fine!

It can be closed, in favor of that bunch of PRs. On other points - there are a lot of 404 at the website.. like 267 only for local links. Where can I share this info?
I rather kill myself than create an issue for each URL (which I am investigating manually)? Or should I create PR in auto mode (it shouldn't be hard using scripting).

/do-not-merge

I think this is related to #16642

yes! also related to

#16640
#16641
#16643

And I have no idea what to do with the rest of the broken links I have found.

Since you already selarate it into new PRs may be you can close this PR in favor of that other PRs? Cheers!

oh. sure.

@butuzov there are two ways you can help further (if you're interested):

Log an issue about the remaining list of broken links.
Take a look at automating the reporting / checking; see issue #15893

@sftim I will try to back asap, maybe with some automated aproach. at least it's nice to develop own link checking tool and test it with kubernetes website.


I found this error when i use Mitmproxy on Ubuntu15.04

Mitmproxy works fine on my Ubuntu15.04 last month,but today I found some problem:
When I type sudo pip install mitmproxy,everything is OK:
wechat@ubuntu:~$ sudo pip install mitmproxy
[sudo] password for wechat:
Requirement already satisfied (use --upgrade to upgrade): mitmproxy in /usr/local/lib/python2.7/dist-packages
Requirement already satisfied (use --upgrade to upgrade): backports.ssl-match-hostname<3.6,>=<IP_ADDRESS> in /usr/local/lib/python2.7/dist-packages (from mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): blinker<1.5,>=1.4 in /usr/local/lib/python2.7/dist-packages (from mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): click<7.0,>=6.2 in /usr/local/lib/python2.7/dist-packages (from mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): certifi>=2<IP_ADDRESS> in /usr/local/lib/python2.7/dist-packages (from mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): configargparse<0.11,>=0.10 in /usr/local/lib/python2.7/dist-packages (from mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): construct<2.6,>=2.5.2 in /usr/local/lib/python2.7/dist-packages (from mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): cryptography<1.3,>=1.2.2 in /usr/local/lib/python2.7/dist-packages (from mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): Flask<0.11,>=0.10.1 in ./.local/lib/python2.7/site-packages (from mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): h2<3.0,>=2.1.2 in /usr/local/lib/python2.7/dist-packages (from mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): hpack<3.0,>=2.1.0 in /usr/local/lib/python2.7/dist-packages (from mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): html2text==2016.1.8 in /usr/local/lib/python2.7/dist-packages (from mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): hyperframe<4.0,>=3.2.0 in /usr/local/lib/python2.7/dist-packages (from mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): Pillow<3.2,>=3.1 in /usr/local/lib/python2.7/dist-packages (from mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): passlib<1.7,>=1.6.5 in /usr/local/lib/python2.7/dist-packages (from mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): pyasn1<0.2,>=0.1.9 in /usr/local/lib/python2.7/dist-packages (from mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): pyOpenSSL<0.16,>=0.15.1 in /usr/local/lib/python2.7/dist-packages (from mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): pyparsing<2.2,>=2.1 in /usr/local/lib/python2.7/dist-packages (from mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): pyperclip<1.6,>=1.5.22 in /usr/local/lib/python2.7/dist-packages (from mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): requests<2.10,>=2.9.1 in /usr/local/lib/python2.7/dist-packages (from mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): six<1.11,>=1.10 in /usr/local/lib/python2.7/dist-packages (from mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): tornado<4.4,>=4.3 in /usr/local/lib/python2.7/dist-packages (from mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): urwid<1.4,>=1.3.1 in /usr/local/lib/python2.7/dist-packages (from mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): watchdog<0.9,>=0.8.3 in /usr/local/lib/python2.7/dist-packages (from mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): idna>=2.0 in /usr/local/lib/python2.7/dist-packages (from cryptography<1.3,>=1.2.2->mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): setuptools>=1.0 in /usr/lib/python2.7/dist-packages (from cryptography<1.3,>=1.2.2->mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): enum34 in /usr/local/lib/python2.7/dist-packages (from cryptography<1.3,>=1.2.2->mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): ipaddress in /usr/local/lib/python2.7/dist-packages (from cryptography<1.3,>=1.2.2->mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): cffi>=1.4.1 in /usr/local/lib/python2.7/dist-packages (from cryptography<1.3,>=1.2.2->mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): Werkzeug>=0.7 in /usr/local/lib/python2.7/dist-packages (from Flask<0.11,>=0.10.1->mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): Jinja2>=2.4 in /usr/local/lib/python2.7/dist-packages (from Flask<0.11,>=0.10.1->mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): itsdangerous>=0.21 in /usr/local/lib/python2.7/dist-packages (from Flask<0.11,>=0.10.1->mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): singledispatch in /usr/local/lib/python2.7/dist-packages (from tornado<4.4,>=4.3->mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): backports-abc>=0.4 in /usr/local/lib/python2.7/dist-packages (from tornado<4.4,>=4.3->mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): PyYAML>=3.10 in /usr/local/lib/python2.7/dist-packages (from watchdog<0.9,>=0.8.3->mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): argh>=0.24.1 in /usr/local/lib/python2.7/dist-packages (from watchdog<0.9,>=0.8.3->mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): pathtools>=0.1.1 in /usr/local/lib/python2.7/dist-packages (from watchdog<0.9,>=0.8.3->mitmproxy)
Requirement already satisfied (use --upgrade to upgrade): pycparser in /usr/local/lib/python2.7/dist-packages (from cffi>=1.4.1->cryptography<1.3,>=1.2.2->mitmproxy)
Cleaning up...

But when I use Mitmproxy, something is wrong:
wechat@ubuntu:~$ mitmproxy
Traceback (most recent call last):
  File "/usr/local/bin/mitmproxy", line 9, in <module>
    load_entry_point('mitmproxy==0.17', 'console_scripts', 'mitmproxy')()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 521, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2632, in load_entry_point
    return ep.load()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2312, in load
    return self.resolve()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2318, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/local/lib/python2.7/dist-packages/mitmproxy/main.py", line 6, in <module>
    from netlib.version_check import check_pyopenssl_version, check_mitmproxy_version
ImportError: No module named netlib.version_check

The error is can't find the module named 'netlib.version_check',but in my system,netlib is already installed:
wechat@ubuntu:~$ sudo pip2 install git+https://github.com/mitmproxy/netlib.git@master
Downloading/unpacking git+https://github.com/mitmproxy/netlib.git@master
  Cloning https://github.com/mitmproxy/netlib.git (to master) to /tmp/pip-Dwf0Lo-build
  Running setup.py (path:/tmp/pip-Dwf0Lo-build/setup.py) egg_info for package from git+https://github.com/mitmproxy/netlib.git@master

  Requirement already satisfied (use --upgrade to upgrade): netlib==0.17 from git+https://github.com/mitmproxy/netlib.git@master in /usr/local/lib/python2.7/dist-packages
Requirement already satisfied (use --upgrade to upgrade): mitmproxy>=0.17 in /usr/local/lib/python2.7/dist-packages (from netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): backports.ssl-match-hostname<3.6,>=<IP_ADDRESS> in /usr/local/lib/python2.7/dist-packages (from mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): blinker<1.5,>=1.4 in /usr/local/lib/python2.7/dist-packages (from mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): click<7.0,>=6.2 in /usr/local/lib/python2.7/dist-packages (from mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): certifi>=2<IP_ADDRESS> in /usr/local/lib/python2.7/dist-packages (from mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): configargparse<0.11,>=0.10 in /usr/local/lib/python2.7/dist-packages (from mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): construct<2.6,>=2.5.2 in /usr/local/lib/python2.7/dist-packages (from mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): cryptography<1.3,>=1.2.2 in /usr/local/lib/python2.7/dist-packages (from mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): Flask<0.11,>=0.10.1 in ./.local/lib/python2.7/site-packages (from mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): h2<3.0,>=2.1.2 in /usr/local/lib/python2.7/dist-packages (from mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): hpack<3.0,>=2.1.0 in /usr/local/lib/python2.7/dist-packages (from mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): html2text==2016.1.8 in /usr/local/lib/python2.7/dist-packages (from mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): hyperframe<4.0,>=3.2.0 in /usr/local/lib/python2.7/dist-packages (from mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): Pillow<3.2,>=3.1 in /usr/local/lib/python2.7/dist-packages (from mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): passlib<1.7,>=1.6.5 in /usr/local/lib/python2.7/dist-packages (from mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): pyasn1<0.2,>=0.1.9 in /usr/local/lib/python2.7/dist-packages (from mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): pyOpenSSL<0.16,>=0.15.1 in /usr/local/lib/python2.7/dist-packages (from mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): pyparsing<2.2,>=2.1 in /usr/local/lib/python2.7/dist-packages (from mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): pyperclip<1.6,>=1.5.22 in /usr/local/lib/python2.7/dist-packages (from mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): requests<2.10,>=2.9.1 in /usr/local/lib/python2.7/dist-packages (from mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): six<1.11,>=1.10 in /usr/local/lib/python2.7/dist-packages (from mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): tornado<4.4,>=4.3 in /usr/local/lib/python2.7/dist-packages (from mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): urwid<1.4,>=1.3.1 in /usr/local/lib/python2.7/dist-packages (from mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): watchdog<0.9,>=0.8.3 in /usr/local/lib/python2.7/dist-packages (from mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): idna>=2.0 in /usr/local/lib/python2.7/dist-packages (from cryptography<1.3,>=1.2.2->mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): setuptools>=1.0 in /usr/lib/python2.7/dist-packages (from cryptography<1.3,>=1.2.2->mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): enum34 in /usr/local/lib/python2.7/dist-packages (from cryptography<1.3,>=1.2.2->mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): ipaddress in /usr/local/lib/python2.7/dist-packages (from cryptography<1.3,>=1.2.2->mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): cffi>=1.4.1 in /usr/local/lib/python2.7/dist-packages (from cryptography<1.3,>=1.2.2->mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): Werkzeug>=0.7 in /usr/local/lib/python2.7/dist-packages (from Flask<0.11,>=0.10.1->mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): Jinja2>=2.4 in /usr/local/lib/python2.7/dist-packages (from Flask<0.11,>=0.10.1->mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): itsdangerous>=0.21 in /usr/local/lib/python2.7/dist-packages (from Flask<0.11,>=0.10.1->mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): singledispatch in /usr/local/lib/python2.7/dist-packages (from tornado<4.4,>=4.3->mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): backports-abc>=0.4 in /usr/local/lib/python2.7/dist-packages (from tornado<4.4,>=4.3->mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): PyYAML>=3.10 in /usr/local/lib/python2.7/dist-packages (from watchdog<0.9,>=0.8.3->mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): argh>=0.24.1 in /usr/local/lib/python2.7/dist-packages (from watchdog<0.9,>=0.8.3->mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): pathtools>=0.1.1 in /usr/local/lib/python2.7/dist-packages (from watchdog<0.9,>=0.8.3->mitmproxy>=0.17->netlib==0.17)
Requirement already satisfied (use --upgrade to upgrade): pycparser in /usr/local/lib/python2.7/dist-packages (from cffi>=1.4.1->cryptography<1.3,>=1.2.2->mitmproxy>=0.17->netlib==0.17)
Cleaning up...

What can i do to fix this issue? THANKS very much!!

It seems you are using mitmproxy 0.17:
load_entry_point('mitmproxy==0.17'
Its is not a good idea to mix pypy releases with github master branches.
Please try to remove all mitmproxy/netlib/pathod packages from your python installation, and try again with a clean pip install.
Also, please note, if you really want to use github latest, there was a big change: mitmproxy & netlib & pathod repository were merged - so this might change a few things for you.

Thanks very much. I followed ur advice to reinstalled Mitmproxy,everything is OK now!!


can't open extension from a link (ff v105 issue)

this is not a smart rss bug, but perhaps there's a solution on the extension developer side
in FF 105 something was changed regarding security that affects extensions apparently - i thought the culprit was pref("extensions.content_web_accessible.enabled", false); but it is not
if i load moz-extension://<blahblah>/rss.html and bookmark it, i can load the ext. from the bookmark - great - but if add that link to my new tab page (which is like a text editor more or less), then i cannot load the ext.
Security Error: Content at moz-extension://<blahblah>/newTab/newTab.html may not load or link to moz-extension://<blahblah>/rss.html.
ff 105
smart rss 2.23.2
linux

I'll try defining the page as a web accessible resource, though I'm not sure if just opening it will work properly, I remember the process started by clicking the toolbar button was more complex in the past and simply navigating to the reader page would misbehave. Quick tests seem like it's fine now, but honestly I don't remember fixing it so I recommend caution when using it this way

thanks zakius - if you happen to need it to test, the new tab page ext. i use is Mark-It


stateCd does not work with nwis_client

I had not realized certain options were non-functional with the current version of nwis_client. These options appear to work with the version on the restclient_transition branch. So, I would say that makes getting this branch merged into main a high priority.

Yeah good catch, I was not aware of that either. That sounds like something a pytest --run-slow should have caught. I need to create a new gh-action that runs our slow tests every Sunday if something new has been added since the last time the action ran.

Something similar to this.


Issue with Detecting Player Color and Recognizing Meeting Triggered by Dead Body Discovery

Hello,
I noticed a couple of issues that might need attention:
Color Detection Problem: The system doesn't seem to accurately detect my player color during gameplay. This often leads to incorrect identification and affects the gameplay experience.
Meeting Detection Issue: The plugin (or python script) fails to recognize when a meeting is initiated due to a dead body being reported. This is crucial for gameplay analysis and needs to be addressed to ensure the AI's functionality aligns with game events.
Could you please look into these issues?
Thank you for your efforts in developing this project.

Currently working on other projects besides this one, but will take a look when I have the time

Currently working on other projects besides this one, but will take a look when I have the time

I really need this for an ongoing project. Could you please let me know how I can fix the issue myself? Alternatively, I would be happy to provide a donation to help resolve it.


added windows 11 and its registry keys

after reading this article, i found windows 11 is missing so i added windows 11 and its related registry keys.
I need assistance from @JohanFreelancer9.

@denisebmsft  this pr #10115 is not merged still.


[Request Feedback]: TR-2, Insufficient access control with vector store

Contact Details
<EMAIL_ADDRESS>What is the idea
This is a request for direct feedback and answers to the following questions regarding a threat described in the governance framework.
TR-2, Insufficient access control with vector store
Section: governance-framework/_threats/tr-2.md
File (private repo link): https://github.com/finos/ai-readiness-private/blob/10e31ea7ccf3893983404de3484f7c57f9934d57/governance-framework/_threats/tr-2.md
Diff (private repo link): https://github.com/finos/ai-readiness-private/pull/5/files#diff-db30cd48d424d2b7f0230e21f604f54911fcc66a58c65c610517d8b32fac9a8c
Title: Insufficient access control with vector store
Type: Confidentiality
External references:

owasp-llm-top-10

LLM06: Sensitive Information Disclosure

Description:
Given the immaturity of the products, the vector store may not have capabilities expected of enterprise software (access control, encryption at rest, audit logging etc). Misconfiguration may allow unauthorized access to data. Internal user accesses data and leaks/tampers it.
Questions:

Original writing of this threat: just related to maturity of new tooling. Is that a sufficient threat?
Is local vector store poisoning/tampering and/or theft an integrity and confidentiality issue? Is this covered by other frameworks?
What are the low-level mechanics of poisoning or data extraction from a vector store?

Why this is important
Discussion surrounding this threat has been going on live, on today's meeting (2024-09-03).
We have opened this issue to better capture's everyone's feedback, and not being constraint by the time alloted to the meeting.
Code of Conduct

[X] I agree to follow the FINOS Code of Conduct

Yes, the immaturity of vector store technologies is a sufficient threat to warrant inclusion in the framework. Unlike traditional databases, vector stores are relatively new and are often not equipped with the enterprise-grade security features typically expected, such as robust access control, encryption at rest, and audit logging. Misconfiguration or lack of these controls can lead to unauthorized access, tampering, and data leakage, especially in environments that handle sensitive or proprietary information. The fact that many vector stores are still in developmental stages increases the risk of misconfigurations or incomplete security implementations, making them an easy target for both external and internal threats.

The threat associated with vector stores is twofold: integrity and confidentiality. While TR-2 primarily addresses confidentiality concerns, data poisoning and tampering are serious integrity issues that must also be considered. If an attacker or unauthorized internal user gains access to the vector store, they could tamper with or poison the embeddings, which would lead to compromised responses from the RAG model, potentially undermining business processes or steering the model toward erroneous or harmful outputs.

From a technical perspective, the mechanics of data extraction and poisoning in a vector store are as follows:

Data Extraction: Vector stores store embeddings, which are high-dimensional representations of data. Without access controls, an attacker can simply query or retrieve these embeddings. By analyzing these vectors, attackers can reverse-engineer or infer the original sensitive data that was used to generate the embeddings. This is especially concerning for embeddings that may represent proprietary algorithms, financial data, or sensitive corporate documents.

Poisoning: In a poisoning attack, an attacker with write access to the vector store could inject false embeddings or modify existing ones. The LLM would then retrieve these tampered embeddings during inference, leading to corrupted or malicious outputs. For example, embedding toxic or misleading data into the vector store could result in biased or harmful recommendations when the LLM performs RAG operations.

IMO LLM + Vector Store = Two Layers of Security. By focusing on both the LLM and vector store in the threat model, we ensure that both inference (LLM) and retrieval (vector store) are secured. Leaving out the vector store would create a blind spot, as attackers could bypass LLM-specific security mechanisms by attacking the data layer.


Parent link from search results always displays listing page 1

A user after clicking on the "Parent" link of a search result item will always be shown page 1 of the parent listing. It could be reasonably expected that the page containing the search result item will be shown, possibly even anchored at the item within the listing.
Any varying thoughts on this?

I can see what you mean, but I don't believe this would be expected. The search listing makes no suggestion that by clicking the "Parent" link, you'll be shown the search result in situ, the parent link is merely provided as a convenience and for context.
That isn't to say what you're suggesting is a bad idea, however everywhere else where a page's parent is linked in this way, the link takes you to page 1 of the parent. That presents an issue of consistency to address if we were to change the behaviour in the case of search results.

@davecranwell thank you for following up on this. It could have just been my frame of mind at the time. I think I expected my context to remain consistent with me as far as possible with each action in the system and was surprised when the context was reset. In the Kano model that would have been delightful :-)
I can see how this could be a decent chunk of work to change in a consistent manner. Once the UI is run off the API and untangled from the backend these changes might be less work. This issue/enhancement may not be worth pursuing depending on your roadmap and what others think.

I think this issue has merit, but relatively speaking this would be very low in a rather long list of priorities. In the interest of reducing the overhead of managing this many open tickets in a small team, we'd rather close it. We'd welcome you to re-opened again later as the situation changes.


[AutoRelease] t2-newrelicobservability-2023-03-24-89843(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/3822
Live test success

issue link:https://github.com/Azure/sdk-release-request/issues/3822

/azp run prepare-pipelines

/azp run prepare-pipelines

/azp run prepare-pipelines

/azp run prepare-pipelines


Alternative to CurrentValueSubject in ViewStore

This is a proof of concept as a way to provide consistent ordering for StorePublisher subscribers (discussed in #698). @mbrandonw mentioned:

It would be great if it could be fixed at the library level

so I thought I'd give it a try. Pretty sure it will need to be made thread safe and have some extensive tests/benchmarks added.
I can see the benefits of sticking with CurrentValueSubject and I haven't thoroughly tested this... just checking to see if it's something worth exploring further. I used CombineExt/CurrentValueRelay as a starting point.

@iampatbrown Thanks for the PR! @mbrandonw and I just chatted about it and think it's a simple enough addition that we think it's worth merging, especially if it makes things a bit more deterministic than the tools Apple ships. The existing benchmarks (simple as they are) don't appear to be negatively affected.
We also think that thread safety is probably not necessary due to the fact that it is only used in the store, which is already designed to not be thread safe.
If you think this is ready, please feel free to remove the draft status and we'll look to merge!

We also think that thread safety is probably not necessary due to the fact that it is only used in the store, which is already designed to not be thread safe.

I thought this might have been the case as well. My main concern was if people were using viewStore.publisher.subscribe(on:). Had a feeling this might be impacted. But yeah, the docs are pretty clear about not being thread safe though. I guess we can revert back fairly easily if there are any problems.
Any preference on the file structure and naming?

Ha didn't mean to leave you hanging here!

Any preference on the file structure and naming?

Nope! What you have looks great. If you think this is ready, please move it into review and we'll get it merged :smile:

@stephencelis Hahaha. No worries. Did you give it a test drive? Pretty sure it was all good when we originally looked at it.

@iampatbrown Yup! All looked good to us and seems to benchmark about the same 😄


add ability to change interpolateZoom function

There is currently no way to change the current interpolateZoom function. I would like to be able to have a simple direct pan / zoom tween transition.

Sounds reasonable. I’m added zoom.interpolate. If you set it to d3.interpolate instead of the default d3.interpolateZoom you can disable “smooth” zooming.


document is not defined Error

greeting
i want to use this package in nuxt and i got this error message

document is not defined

 var styleElement = document.querySelector('style[' + ssrIdKey + '~="' + obj.id + '"]')
do you have any solution ?

if you're using this with nuxt.js, consider defidining this as a plugin and omitting it from server side rendering.
// ./plugins/v-marquee-text.js
import Vue from 'vue'
import MarqueeText from 'vue-marquee-text-component'

Vue.component(MarqueeText)

in your nuxt.js configuration
// ./nuxt.config.js

{
  //...
  plugins: [
    { ssr: false, src: './plugins/v-marquee-text.js' }
  ],
  //...
}

Sorry @hamedsrk I don't use nuxt.
@kylewelsby thank you for your support


Can I load a image into the alert box?

$.confirm({
content: 'url:text.txt',
title: 'Title'
});
in this code how can i load a image in the content? thx

You can simple insert an image tag inside content
$.confirm({
content: '<img src="youimage.jpg">',
title: 'Title'
});


Dont return rt result if Rt composite doesnt exist

This fixes this sentry error.
I believe it was a result of the latest Rt smoothing - the smoothing expects Rt composite to be there but that only exists when there is some case/death data.
This fix isn't the best fix, but was what I felt most comfortable with.  I'm pretty sure this happens in low case count counties, so shouldn't be too impactful on a global level
I tested out fips 31081 in nebraska, and case/death data was filtered out, but the smoothed hospitalization data wasn't.
One fix I would be in favor of doing is changing how we include hosps as an "available timeseries" here.  we have a condition if len(hosps > 3) but it might be better to define a minimum hospitalization threshold.
Please Check

[ ] Are the JSON schemas updated?
[ ] Are the api docs updated?
[ ] Are tests passing?

I can't think of an example where we hospitalization data but no case or death data. This makes me nervous that this error is actually catching something else. Are you saying that we drop case/death data in such a way that it seems empty, but we don't dump the associated hospitalization data?

I can't think of an example where we hospitalization data but no case or death data. This makes me nervous that this error is actually catching something else. Are you saying that we drop case/death data in such a way that it seems empty, but we don't dump the associated hospitalization data?

yeah so here's one spot that could happen:
        if np.sum(cases) > self.min_cases:
            available_timeseries.append(TimeseriesType.NEW_CASES)
        if np.sum(deaths) > self.min_deaths:
            available_timeseries.append(TimeseriesType.NEW_DEATHS)
        if (
            self.hospitalization_data_type
            is load_data.HospitalizationDataType.CURRENT_HOSPITALIZATIONS
            and len(hosps > 3)
        ):
            # We have converted this timeseries to new hospitalizations.
            available_timeseries.append(TimeseriesType.NEW_HOSPITALIZATIONS)

there is no minimum number of hospitalizations required for the hospitalization timeseries to be included.
Also, even though, for the case of fips=31081, there are new_cases, new_deaths, and new_hosps, the cases and deaths get smoothed out in the gaussian smoothing and the timeseries come back empty.
For some reason the hospitalizations don't get removed, I think that's because the value is 6 all the way across (though i thought those should be new hosps, so not sure why that values is 6 all the way across)).

I think we may be mixing CURRENT_HOSPITALIZED and CUMULATIVE_HOSPITALIZED. We convert between the two in PySEIR for scoring and plotting, but it's sometimes not obvious unless you're paying attention to ModelFitter().hospitalization_data_type


Release 6.0.2

Questions
Answers

Description?
Release 6.0.2

Type?
improvement

BC breaks?
no

Deprecations?
no

Fixed ticket?
N/A

How to test?
N/A

Thanks @Progi1984


New version: MikeFarah.yq version 4.35.1

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

I have no idea why the installation validation failed:

The linked pipelines do not appear to contain any error either.

Automatic Validation ended with:

Installation failed with exit code -1978335187
2023-08-20 14:42:53.269 [FAIL] Installer failed security check. Url: https://github.com/mikefarah/yq/releases/download/v4.35.1/yq_windows_386.exe Result: 0x80004005

This scan failure might be a false positive. We can rescan tomorrow.


Zero copy alternative: data pre-fetch.

Add store data pre-fetch and its config.
The change is for server getRequest performance experiment.

Read data from file and buffer it to memory in requestHandler thread.
Do socketChannel write with buffer from memory in Processor thread.

Codecov Report

Merging #892 into master will decrease coverage by 0.04%.
The diff coverage is 88.57%.

@@             Coverage Diff              @@
##             master     #892      +/-   ##
============================================
- Coverage        67%   66.96%   -0.05%
+ Complexity     4249     4248       -1
============================================
  Files           356      356
  Lines         27806    27836      +30
  Branches       3530     3534       +4
============================================
+ Hits          18632    18639       +7
- Misses         8209     8225      +16
- Partials        965      972       +7

Impacted Files
Coverage Δ
Complexity Δ

.../main/java/com.github.ambry.store/HardDeleter.java
80% <100%> (-2.59%)
41 <0> (-1)

...main/java/com.github.ambry/config/StoreConfig.java
100% <100%> (ø)
1 <0> (ø)
:arrow_down:

...om.github.ambry.network/PlainTextTransmission.java
83.33% <100%> (+0.35%)
9 <0> (ø)
:arrow_down:

...java/com.github.ambry.network/SSLTransmission.java
62.79% <100%> (+0.12%)
49 <0> (-1)
:arrow_down:

...rc/main/java/com.github.ambry.store/BlobStore.java
85.86% <100%> (ø)
63 <0> (ø)
:arrow_down:

.../java/com.github.ambry.network/NetworkMetrics.java
81.37% <100%> (+0.37%)
3 <0> (ø)
:arrow_down:

...va/com.github.ambry.store/StoreMessageReadSet.java
86.81% <85.18%> (-1.07%)
12 <0> (+4)

...in/java/com.github.ambry.clustermap/Partition.java
82.43% <0%> (-4.06%)
23% <0%> (-1%)

...github.ambry.rest/AsyncRequestResponseHandler.java
88.59% <0%> (-2.29%)
23% <0%> (ø)

... and 5 more

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 a3a93ef...ba06cf4. Read the comment docs.

server integration test for perFetch is added.
Good to review.

Addressed comment from @vgkholla and @pnarayanan . Ready for review.

addressed comments and isolate doPrefetch and transferTo per offline discussion.

Okay to merge this?

Yup


CV Docs Refactor

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes:

The CV Docs were a mess of duplication and redundancy making maintenance unsustainable. With the inclusion of a new health source with Google Big Query (https://harness.atlassian.net/browse/CDS-95956), the immediate need for a refactor is apparent.

Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

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

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

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


Refactor GEOS_SINCE_3X0 to GEOS_SINCE_3_X_0

Probably GEOS_SINCE_3_8_0 is a slightly better convention for these macros IMO, makes it a bit less ambiguous. Especially in the future, for say, in case of a 3.10.0 version.
https://github.com/pygeos/pygeos/blob/a999b767aecf409dfc8421314cbc6ee459dd9430/src/geos.h#L20
Should be a straight forward change, I can do a refactor and raise a PR for this if that works.
Let me know if you guys have any other ideas.

Good suggestion. Please go ahead!


chore: upgrade CSI driver image versions

What type of PR is this?
/kind feature
What this PR does / why we need it:
chore: upgrade CSI driver image versions
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall First build on andyzhangx/upgrade-csi-driver-1.28.1 at 61.537%

Totals

Change from base Build<PHONE_NUMBER>:
61.5%

Covered Lines:
2563

Relevant Lines:
4165

💛  - Coveralls


Default version of core object is not handled correctly

When client send supported object to the server, it can omit the version of this object.
In Leshan we consider that a missing version always means 1.0.
But this is is not what is described in LWM2M specification concerning core object.
See :

<EMAIL_ADDRESS>Object Definition and Object Version Usage
<EMAIL_ADDRESS>Object Definition and Object Version Usage.

We currently target 1.1.x. (for Leshan v2.x)
I'm not so sure to understand correctly the v1.1.x but I feel both try to describe the same idea... version 1.2.x is much clearer :

If a Core Object version does not correspond to version contained in the LwM2M Enabler release supported by the LwM2M Client, the Object Version MUST be provided by the LwM2M Client to the LwM2M Server.

Here is OMA question relative to this issue : https://github.com/OpenMobileAlliance/OMA_LwM2M_for_Developers/issues/561

Based on information about the Object 4  (Connectivity Monitoring)
In OMA Registry there is all these following versions of this Object 4:

if the device says it support globally lwm2m version 1.1, we can see among the 4 above versions, that the Minimum Object Version compatible with LwM2M Version 1.1 is Object Version 1.2
Therefore this is not necessary to explicitly mention ver="1.2" in registration

I also added comment in this discussion.
Together with @Warmek we preparred PoC  demonstrated how this issue can be addressed in Leshan. In first commit we are using most recent object version, in second one we getting minimum value (for a given version of the lwm2m) from objects registry.
It would be great for us if "new default object versioning" could be available in the next release of Leshan.

I looked at the PoC and I do not like so much the idea about giving the "responsibility" to choose the default version in LwM2mModelProvider. I feel maybe we should rather have a new dedicated class. (:warning: I didn't take to much time on this so I can change my mind)
But before to search another way, I have one question : Do we want this behavior customizable or is it OK to have hardcoded behavior which strictly follow LWM2M specification ?

It would be great for us if "new default object versioning" could be available in the next release of Leshan.

Yep, let's try to do it.

About :

But before to search another way, I have one question : Do we want this behavior customizable or is it OK to have hardcoded behavior which strictly follow LWM2M specification ?

As we have doubt about how specification should be understood maybe safer to have a customizable way. :thinking:
I will try to think more about this :thinking:

As we have doubt about how specification should be understood maybe safer to have a customizable way. 🤔
I will try to think more about this 🤔

We don't have response from OMA yet. We do not know when we will receive an answer and what will be the this answer. Therefore I think that customization is the best idea.

I created a PR about that see #1452, you can review / test if you want.
Any feedback is welcomed.

If you need to have different default version, it is also possible to override DefaultRegistrationDataExtractor.getDefaultVersion(LwM2mVersion lwM2mVersion, int objectId)

Does it mean you think I should consider to integrate #1452 in master ?

I think, it's a very good idea.

Just for documentation purpose, I explain more precisely our choice at : https://github.com/OpenMobileAlliance/OMA_LwM2M_for_Developers/issues/561#issuecomment-1791076649


resolving issue velocity_chokidar.js:34 Uncaught ReferenceError: Npm …

Uncaught ReferenceError: Npm is not defined velocity_chokidar.js:34

Thanks for reporting this issue. I have fixed it and release new versions. The latest is now 1.0.3_1.

Thank you @Sanjo


Case study for list of navigation links.

Thought it would be nice to have a case study showing how to deal with a list of navigation links. This is the simplest kind (i.e. each row has a route enum and we only pass binding to child view), but it's at least something. Maybe in the future we demonstrate a more complicated one like what is in the inventory case study.

Looks good!


Boolean values mis-display

when i try to access any resource in the admin panel, boolean values displayed as No for both true and false values. and when i upgraded to the latest version 2.1.2 it doesn't show any value but only the field name. and when i try to edit , it show unchecked check-boxes for true and false values!
but it works fine when i try to filter by these values.
for example , in the below images , email verified and market joined are boolean fields with true and false values and there isn't something to indicate that !
please help ! and let me know if there is something wrong within my configurations.

which version of admin-bro-mongoose/sequelize do you use? can you share some configuration/schema code?

@wojtek-krysiak
I'm using<EMAIL_ADDRESS>const adminBro = new AdminBro({
databases: [mongoose],
resources: [
    {
      resource: User,
      options: {
        properties: {
          name: {
            isVisible: { list: true, filter: true, show: true, edit: false }
          }, email: {
            isVisible: { list: true, filter: true, show: true, edit: false }
          },
          password: {
            isVisible: { list: false, filter: false, show: false, edit: false }
          },
          phoneNumber: {
            isVisible: { list: true, filter: true, show: false, edit: false }
          },
          nationality: {
            isVisible: { list: true, filter: true, show: true, edit: false }
          }
        },
        parent: { name: 'User-Related' }
      }
    },
    {
      resource: Workspace
    },
    {
      resource: Job
    },
    {
      resource: Category
    },
    {
      resource: Invitation
    }],
  rootPath: '/admin',
  branding: {
    companyName: 'bla bla',
    softwareBrothers: false,
    logo: '/assets/images/logo.png'
  }
});
const Admin = {
  email: process.env.ADMIN_EMAIL || 'bla bla bla ',
  password: process.env.ADMIN_PASSWORD || 'bla bla bla'
};

const router = AdminBroExpress.buildAuthenticatedRouter(adminBro, {
  cookieName: process.env.ADMIN_COOKIE_NAME || 'admin-bro',
  cookiePassword: process.env.ADMIN_COOKIE_PASS || 'supersecret',
  authenticate: (email, password) => {
    if (email === Admin.email && password === Admin.password) {
      return Admin;
    }
    return null;
  }
});

@wojtek-krysiak hi, is there any update ?


Utilize font-weight for Inter fonts

Hey all, this is the fix for #293 - I implemented the strategy I mentioned there.
The mapping I created for inter style weight class to CSS font-weight is as follows:
Inter Style -- CSS font-weight
light -- 300
regular -- normal (400)
medium -- bold (700)
bold -- 800
I tested a few usages and it works.  If it's what you're expecting, we can merge (no functional changes yet), I can help convert the existing font-family for the Inter fonts to use the Inter family and then properly utilize the new font-weight, so we can deprecate the current usage.
Oh, and here's my account number :)
3cdb51ef0b7da3db65f47c170ec1815f3409c9781d4d8ca6c976273a732c9218
Thanks!

this is great! can you update this PR to fulfill the following acceptance criterias:

Remove the old Inter stuff in the /styles/_font.scss file.
within /styles/_font.scss, the css Custom Properties (CSS varialbes) starting in line 70: all references of --font-family-inter-... should be removed. Inter will be our default font, so we should have no variables related to this.
Every instance of --font-family-inter-bold, --font-family-inter-light, --font-family-inter-medium, etc etc should be replaced with the font-weight counterpart.

Thanks!  Will do, I'll have it done in the next day or two.

Ok, updated!  I tested each update and there is no visual change, except for a very slight one for Task Title from the update to src/containers/Tasks/TasksTask/TasksTask.scss as previously the css was overriding a font-weight of 600 on top of the Inter Medium, which was landing the weight somewhere between Inter Medium and Inter Bold.  I could not reproduce the exact weight, but the difference is very slight.
Let me know what you think.

@colfax23 phenomenal work! I made a couple minor changes:

create a --font-family-default: Inter, sans-serif
for the body, have the style font-family: var(--font-family-default)
because of above, we no longer ever need to reference Inter in any of our other selectors, so I removed all other instances of Inter
make sure font-size comes before font-weight (alphabetize css)

If you plan on doing the same task for the AccountManager, please keep these in mind! But other than that, this is trully exactly what we wanted. Thanks!

Thanks for the feedback and making those changes!  Updated the AccountManager PR with those changes as well.


rename addressbook to cardbank

Pull Request Test Coverage Report for Build 409

116 of 127 (91.34%) changed or added relevant lines in 15 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.603%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/main/java/seedu/address/storage/XmlSerializableCardBank.java
9
10
90.0%

src/main/java/seedu/address/model/CardBank.java
5
6
83.33%

src/main/java/seedu/address/model/ModelManager.java
40
41
97.56%

src/main/java/seedu/address/model/UserPrefs.java
9
11
81.82%

src/main/java/seedu/address/MainApp.java
7
13
53.85%

Totals

Change from base Build 406:
0.0%

Covered Lines:
2226

Relevant Lines:
2541

💛  - Coveralls


feat(ktor): update to stable v3

Q
A

Bug fix?
no

New feature?
yes

BC breaks?
no

Related Issue
Fix #384

Describe your change
Update Ktor to stable v3.

Hi @aallam , can you please release a version with the ktor 3.0.0 support?

@aallam, could you please publish this one?


Best-effort handle ReflectionTypeLoadExceptions in controller type assembly enumeration

https://github.com/microsoft/MixedRealityToolkit-Unity/issues/4319
The controller type enumeration happens to look through every single assembly that is visible to the editor - it's possible that this certain classes of a module may not be loadable, so in that case we will end up using those best effort.
Note that I wasn't ultimately able to repro the reported issue, but doing some online searches I can see it is a not-uncommon issue, especially when you're enumerating every single visible asssembly like we are. Maybe it would be more appropriate to not handle the exception if we could scope our assemblies to just "MRTK" and "MRTK extending" ones, but there's no clean way of doing that.

/azp run mrtk_pr


Separate Library Folders for P1 and P2 Objects

I think it will be helpful to separate the P1 and P2 library folders. When selecting either, the file filter would automatically be set as needed for the folder.

Agreed on separation.  For filter: I think the file filter should be auto-set to the combined P1 & P2 filter when selecting one of these folders, in case someone had misplaced the opposite Propeller type file in there - it'd help them find it / notice it more readily and take steps to solve the mistake.
NOTE: More consideration is in order, but this may require separate library path preferences be made; although with the extension settings as they are, it may not be an issue.  Need to consider the adv/disadv of each before fully implementing.


Route request url handler doesn't exist in rt library.

When i hit GET ROUTE button, a request is sent to /from/:id/to/:id but there is no handler for these request in rt-library. rt-library handles only /astar/from/:id/to/:id and /dijkstra/from/:id/to/:id..
getRoute method:
getRoute = (waypoints) => {
    const startOsmId = waypoints[0];
    const destinationOsmId = waypoints[waypoints.length - 1];
    // this url req is not handled by rt-library
    const url = `${GreenNavServerAddress}from/${startOsmId}/to/${destinationOsmId}`;
    ...

Hm it should have been changed by commit 09dbb0as

Hmm, I was a bit hesitant to make that change myself so I opened this issue.


Suites are failing frequently due to timeouts

E.g. https://dev.azure.com/ms-azuretools/AzCode/_build/results?buildId=21559&view=logs&j=a5e52b91-c83f-5429-4a68-c246fc63a4f7&t=95359773-9cfc-583f-7b87-0a0d44ca7da9&l=40467

The previous fix seems to have worked.


Error reading data from kaggle

Hello, I did everything as shown in the video, but I get an error when I want to access the "transcript.csv" file
https://gyazo.com/c59a07d69a758e2d9abe2820113eae0d
https://www.kaggle.com/renjagrotemeyer/prototech-chat-transcipt

You will have to unzip it first. then type "transcript.csv", it should load then.


community: Weekly Sync

Hangouts?
Add info to CONTRIBUTING.md
Google docs for notes?

https://calendar.google.com/calendar/embed?src=0b6g0ki0qsq1fd1sr703ceeioc%40group.calendar.google.com&ctz=America%2FLos_Angeles

Need to remove the hangouts link from the /community.html doc


PSScriptAnalyzer doesn't seem to be using the SuppressMessageAttribute ctor fields as intended.

So here is an example of how PSScriptAnalyzer is using this attribute to target a parameter:
[System.Diagnostics.CodeAnalysis.SuppressMessageAttribute("PSProvideDefaultParameterValue", "b")]
[System.Diagnostics.CodeAnalysis.SuppressMessageAttribute("PSProvideDefaultParameterValue", "a")]
Param([string]$a, [int]$b)

But the intent of the first two parameters of the SuppressMessageAttribute constructor are to uniquely identify the suppressed rule, and to apply to a parameter would use the MessageId property e.g.:
[SuppressMessage("Microsoft.Performance", "CA1801:ReviewUnusedParameters", MessageId = "isChecked")]
[SuppressMessage("Microsoft.Performance", "CA1804:RemoveUnusedLocals", MessageId = "fileIdentifier")]
static void FileNode(string name, bool isChecked)

So I would expect that every PowerShell suppression of a built-in rule would start like this:
[Diagnostics.CodeAnalysis.SuppressMessageAttribute("Microsoft.PowerShell", "PSAvoidUsingCmdletAliases")]

This identifies the rule as a built-in rule.  I could imagine custom rules would use their module/assembly name in the first field (category).
Suppression of a parameter should look like:
[Diagnostics.CodeAnalysis.SuppressMessageAttribute("Microsoft.PowerShell", "PSProvideDefaultParameterValue", MessageId="b")]
[Diagnostics.CodeAnalysis.SuppressMessageAttribute("Microsoft.PowerShell", "PSProvideDefaultParameterValue", MessageId="a")]
Param([string]$a, [int]$b)

Note that MessageId is the field that is supposed to be used if Scope/Target aren't sufficiently precise.

Another option for the built-in rule category would be:
[Diagnostics.CodeAnalysis.SuppressMessageAttribute("PSScriptAnalyzer.PS", "PSProvideDefaultParameterValue", MessageId="a")]
[Diagnostics.CodeAnalysis.SuppressMessageAttribute("PSScriptAnalyzer.PSDSC", "PSDSCDscTestsPresent")]

Keith. Thanks for your input.
This is a feature request and we will add to the backlog items


Bug: Right-clicking a picture doesn't invoke the right-click context menu

As requested I'm opening a bug report as Fly doesn't open a context-menu when right-clicking a picture for me. No matter what I do or on which file I try it on nothing happens. Right-clicking next to the picture makes Fly go windowed as intended.
I'm using Fly 2.2.0 and Windows 11 23H2 22631.3593 and this feature never worked for me.

Did you use mouse right click or any other means?

@riyasy I'm using the default Right-Click function of my mouse, no macros or anything else involved.

I saw the new version but sadly a full, clean reinstall of 2.2.1 didn't help at all with the issue. I can still right-click next to the image to make fly exit fullscreen however right clicking on a picture still doesn't trigger a menu or any kind of reaction. It's as if fly simply isn't registering the right-click on the picture. The log-file shows nothing but this, I opened a single picture in a folder as a test:
2024-08-01T13:51:42.183|Trace|FlyPhotos.Utils.Util.FindAllFilesFromExplorerWindowNative|1 files listed from Explorer

I added error checking in that part solely based on this bug. I have tested this Fly on new installations of Win11 and Win10. And in Win11, both with old and new style context menu enabled. (What ever style is selected in Windows 11, Fly will display the win 10 style full context menu as seen in other third party integrations).
Are you able to see the explorer context menu from other third party applications say like Everything app or some other app which you use?(https://www.voidtools.com/). In everything app, if we right click any file item after search, the default explorer context menu is shown. I have employed the same approach.

@riyasy Thanks for continuing to look into it! I think you might be onto something here. I do use the classic right-click menu in Windows 11 with an Acrylic background via StartAllBack, could that be the culprit? I never had issues with any other program though and the right-click menu works no problem in Everything:

Ok. I don't understand the exact reason why you are not getting it. I have tested in several machines and could not get the issue. Anyway I have fully rewrote the ContextMenu part in CPP native code instead of C#. Can you please check the 2.2.2 installer from the following link?
https://drive.google.com/file/d/1k7CpurwvjISZjrNh0WhWdzDiUu-B2zEa/view?usp=sharing

@Skyyblaze , Were you able to have a look?

@riyasy Sorry I completely missed your earlier message! I tried the 2.2.2 build now and sadly nothing changed. I am sorry if I drive you crazy with this, I don't understand myself what's going on but I appreciate your work.

@Skyyblaze , Did you get something like "Showing context menu failed" in the log file?
I installed StartAllBack and checked, but still context menu showed up. The only thing remaining is a german windows installation. :-)

@riyasy No, the only thing my log file gets populated with seems normal:
2024-08-01T13:51:42.183|Trace|FlyPhotos.Utils.Util.FindAllFilesFromExplorerWindowNative|1 files listed from Explorer 2024-08-01T23:56:32.451|Trace|FlyPhotos.Utils.Util.FindAllFilesFromExplorerWindowNative|24 files listed from Explorer 2024-08-01T23:57:28.132|Trace|FlyPhotos.Utils.Util.FindAllFilesFromExplorerWindowNative|24 files listed from Explorer 2024-08-03T06:21:36.234|Trace|FlyPhotos.Utils.Util.FindAllFilesFromExplorerWindowNative|80 files listed from Explorer 2024-08-04T14:41:48.670|Trace|FlyPhotos.Utils.Util.FindAllFilesFromExplorerWindowNative|111 files listed from Explorer 2024-08-04T19:05:20.716|Trace|FlyPhotos.Utils.Util.FindAllFilesFromExplorerWindowNative|111 files listed from Explorer
It is indeed weird, I would be stumped if the language was the culprit but I've seen weirder things so there's that haha. One thing I did notice, my right-click and my left-click behave exactly the same in fly, is that intended that you can move the picture while holding right-click?

Well I'm not sure what to say. Upon updating Fly to 2.3.0 it wouldn't work at all anymore so I did a clean re-install (as I did before) and now the right-click menu works haha.

That's good to hear.


bridges | update singleton after level was solved

Motivation
closes #250
After the level is finished (which happens when entering the goal area), we want to update the global inventory and bridge connection list.
What was changed/added
When clicking the "Continue" button in the goal menu, the SingletonPlayer inventory is updated and the necessary bridge-edges are added.
Because while returning to the overworld we will not change the level, nothing else has to be changed.
Testing
https://github.com/mango-gremlin/arch-enemies/assets/57258671/d793841a-b36c-4e44-8de9-7f631c33e4b4
Through print statements before and after you can see that the bridge edge was added correctly.

Additional Information
For this implementation to work the current level must exist in SingletonPlayer.bridge_level_scenes. If there is a better solution to find out which BridgeEdge we are using in the current level, let me know.

I've changed to edge finding approach. There's now a new variable in SingletonPlayer, current_edge which is getting set in the player script while entering a bridge level, and retrieved by the goal menu script while setting the solved bridge edge.
I'm not sure if using the singleton for that is the best way, but I'm not really familiar with the overworld code to find a better solution.


bump typeurl version to 2.2.0

fix: https://github.com/containerd/containerd/issues/10715

/assign @samuelkarp


data type of ttl in restore api should be of long type instead of int type

Expected behavior
dump and restore commands expect ttl to be in milliseconds. So, we use pttl command api along with dump command api, and pttl api uses Long data type to hold ttl value. But, when we want to restore the serialized data using restore command api, it expects ttl value to be of int type. This is a problem for very large ttl values.
Actual behavior
type of ttl argument in restore command api should be of long type instead of int type.
Write here what happens instead ...
Steps to reproduce:
Please create a reproducible case of your problem. Make sure
that case repeats consistently and it's not random

convert 365 days to milliseconds, and save it as expire time of some key in redis
use dump and pttl jedis api to serialize the key's value and to get keys ttl value respectively
restore above serialized value using restore api

Redis / Jedis Configuration
single node setup
Jedis version:
2.7.3
Redis version:
3.2.8
Java version:
1.8.0_121

It's long in the master branch https://github.com/xetorthio/jedis/blob/5c2b5858fcac335b67fc0eb00b503a1c71644b19/src/main/java/redis/clients/jedis/commands/JedisCommands.java#L37


GH-37017: [C++] Guard unexpected uses of BMI2 instructions.

Rationale for this change
Some functions introduced with Acero only check for AVX2 availability, but they actually invoke BMI2 instructions.
This can have two negative consequences:

compiling BMI2 intrinsics may fail because BMI2 was not explicitly enabled on the compiler (gh-37017)
some rare CPUs (Via CPUs perhaps) may support AVX2 but not BMI2; other CPUs by AMD have a very inefficient implementation of some BMI2 instructions

What changes are included in this PR?

Ensure that the suitable compiler flag is passed when compiling code with BMI2 intrinsics
Make sure the CPU supports BMI2 adequately before invoking functions featuring BMI2 instructions

Are these changes tested?
Yes, assuming CI covers enough diversity of target platforms.
Are there any user-facing changes?
No, but performance might change (positively or negatively) depending on the CPU and platform.

Closes: #37017

@github-actions crossbow submit r-binary-packages

@github-actions crossbow submit -g cpp

I assume that the remaining errors on r-binary-packages above are not related, but I'd appreciate if someone more competent could double-check? @assignUser or @thisisnic  perhaps?

Oh thanks @pitrou I will check!

Yeah the remaining errors look unrelated (brotli linking error and actions/checkout failing on centos7...) +1

I'm somewhat surprised we don't just fold AVX2 + efficient BMI2 into a single SIMD level

Historically we didn't use BMI2 at all. It then appeared only for a very special operation in Parquet, while AVX2 can be implicitly enabled in lots of other places.
This was manageable, but of course the stealth use of BMI2 in Acero makes the situation more annoying.

If I understand correctly we compile the _avx2.cc files with both AVX2 and BMI2 enabled. Doesn't this meant that any function in any _avx2.cc file may contain a bmi2 operation?

Nit: only two _avx2.cc files are concerned, those that use explicit BMI2 intrinsics.

In other words, even if we examine a file and determine it has no explicit pext, pdep, etc. then wouldn't it still be possible for the compiler to insert those instructions itself as an implicit operation?

Indeed. But this PR introduces matching runtime guards when calling those functions, so this shouldn't be a problem.
Am I missing another concern here?

(distantly related: https://github.com/apache/arrow/issues/26514 )

Am I missing another concern here?

Consider the file level_comparison_avx2.cc. It doesn't contain any explicit bmi2 instructions.  Currently, we compile it with -mavx2 -march=haswell and so it also won't contain any implicit bmi2 instructions (inserted by the compiler).
However, if I understand this PR, it is changing this to compile with -mbmi2 -mavx2 -march=haswell.  So, even though there are not any explicit bmi2 instructions, isn't the compiler free to insert bmi2 instructions in an optimization pass?
That being said, I just tested this file, and several others with avx2 in the name, and adding the -mbmi2 flag did not change the compiled object file at all.  So maybe gcc doesn't do any bmi2-specific optimization or maybe these files just can't take advantage of it.

That's not what this PR does. The BMI2 flag should only be passed for three files: parquet/level_conversion_bmi2.cc, arrow/compute/key_map_avx2.cc and arrow/compute/util_avx2.cc. Are you seeing something else?

No, it's ok to merge since everyone seems to be ok with the approach.

I posted #37623 as a followup to reenable more code paths.


How to sniff Pandora's API

I'm interested in trying to reverse engineer Pandora's play playlist API, but I don't know where to start.  I've snipped the connection between my Android APP and Pandor's cloud while playing a playlist but all of the API comms are over a TLSV1.2 connection.
I gather that if I had the clear text I'd still need to use this tool to decrypt it further, but the links are dead and I don't know Dart.
I'm an embedded program and do 95% of my work in C.
Any hints on how to get the plaintext?

You will need a MITM tool and a way to get the Pandora app to trust a self-signed certificate (either by modding the app or Android itself).
My go-to is HTTP Toolkit (the free version is fine) and a rooted Android device (IIRC this can be an emulator). HTTP Toolkit sets everything up over ADB with one click.
For more advanced stuff, like scripting and my own Pandora MITM tool, I use mitmproxy - though this requires manually installing the CA on Android. I find this Magisk Module useful for that.


Use Java style array decelerations

Codecov Report

Merging #362 (ae70e0b) into master (81a498b) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##             master     #362   +/-   ##
=========================================
  Coverage     81.10%   81.10%
  Complexity     4592     4592
=========================================
  Files           288      288
  Lines         13407    13407
  Branches       1975     1975
=========================================
  Hits          10874    10874
  Misses         1935     1935
  Partials        598      598

Impacted Files
Coverage Δ

...pache/commons/collections4/set/ListOrderedSet.java
92.30% <ø> (ø)

...ns/collections4/iterators/ObjectArrayIterator.java
92.85% <100.00%> (ø)

...he/commons/collections4/map/AbstractHashedMap.java
89.13% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Problem adding net in direct plot

Hi Murat,
As shown in attached GIF, I am not able to select net under "direct plot" option or seletc output net in noise analysis. I tried following steps mentioned in tutorial on website but it didn't helped. Can you please clarify how to directly select net on schematic signal plot.

l
Regards
Vipul

Hello,
I think the problem is that you need to double click on "select a Net/Instance" entry, then select the net, click back on entry line and press "ESC". It is a bit convoluted as Glade does not emit too many signals.

Thanks Murat, issue is resolved now.
On Sun, Apr 10, 2022 at 4:04 PM Murat Eskiyerli @.***>
wrote:

Hello,
I think the problem is that you need to double click on "select a
Net/Instance" entry, then select the net, click back on entry line and
press "ESC". It is a bit convoluted as Glade does not emit too many signals.
—
Reply to this email directly, view it on GitHub
https://github.com/eskiyerli/revEDAsetup/issues/5#issuecomment-1094359308,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUDKPUVYDLH3J6JF5LVNI7TVEMX55ANCNFSM5TANOOGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


azcopy hangs on ubuntu:20.10 (and other) containers on Azure Batch

Which version of the AzCopy was used?
10.8.0
Which platform are you using? (ex: Windows, Mac, Linux)
I'm running Ubuntu images, linux-amd64 on Azure batch environment.
What command did you run?
azcopy cp hello.txt 'https://nfbucket.blob.core.windows.net/my-data/hello.txt?SAS_TOKEN

What problem was encountered?
The upload process hangs, here's the log
Log file is located at: /mnt/resource/batch/tasks/workitems/nf-job-1610972315/job-1/task-1610972316/wd/.azcopy_log/571790c5-3d0a-8f4a-5bad-b863ad57d1c7.log

100.0 %, 0 Done, 0 Failed, 1 Pending, 0 Skipped, 1 Total,
100.0 %, 0 Done, 0 Failed, 1 Pending, 0 Skipped, 1 Total,
100.0 %, 0 Done, 0 Failed, 1 Pending, 0 Skipped, 1 Total,
100.0 %, 0 Done, 0 Failed, 1 Pending, 0 Skipped, 1 Total,
100.0 %, 0 Done, 0 Failed, 1 Pending, 0 Skipped, 1 Total,
100.0 %, 0 Done, 0 Failed, 1 Pending, 0 Skipped, 1 Total,
100.0 %, 0 Done, 0 Failed, 1 Pending, 0 Skipped, 1 Total,
100.0 %, 0 Done, 0 Failed, 1 Pending, 0 Skipped, 1 Total,
100.0 %, 0 Done, 0 Failed, 1 Pending, 0 Skipped, 1 Total,
100.0 %, 0 Done, 0 Failed, 1 Pending, 0 Skipped, 1 Total,
100.0 %, 0 Done, 0 Failed, 1 Pending, 0 Skipped, 1 Total,
100.0 %, 0 Done, 0 Failed, 1 Pending, 0 Skipped, 1 Total,
100.0 %, 0 Done, 0 Failed, 1 Pending, 0 Skipped, 1 Total,

How can we reproduce the problem in the simplest way?
Launching azcopy from within the docker container image for the specified Ubuntu linux container.
This seems to be related to a previous issue https://github.com/Azure/azure-storage-azcopy/issues/517
Have you found a mitigation/solution?
I changed the docker image from ubuntu to a different one continuumio/miniconda3:4.8.3 and it worked. Note that the latter image is based on debian.

Hi @abhi18av, do you know if there are any proxy/firewall in your environment?
Could you please share with us the actual log file? (the one on your disk, /mnt/resource/batch/tasks/workitems/nf-job-1610972315/job-1/task-1610972316/wd/.azcopy_log/571790c5-3d0a-8f4a-5bad-b863ad57d1c7.log)

Hi @abhi18av, do you know if there are any proxy/firewall in your environment?
Could you please share with us the actual log file? (the one on your disk, /mnt/resource/batch/tasks/workitems/nf-job-1610972315/job-1/task-1610972316/wd/.azcopy_log/571790c5-3d0a-8f4a-5bad-b863ad57d1c7.log)


Align new 9.1.1 XM images with existing ones

Thank you for adding 9.1.1 support! From the recent release notes:

[Added] Sitecore 9.1.1 XM and XP on ltsc2019/1809, please notice that the xm1 tags is now just xm

Is there any reason for this? Does it make sense to align the naming conventions and rename all the existing xm1 images into xm (or vice versa)?
Currently I'm using docker hub with 20 repositories ($22/month) to build 9.x images. 9.1.1 introduces 3 new xm repos that do not feet my plan and force me to either switch to the next one ($50) or to configure local registry (which I'd like to avoid).
Please let me know if I should come up with a PR fixing this.

I'm sorry that I didn't foresee the consequences of this rename for those of you using the "pay per repository" model!
I think that it would be best to go back to using xm1 instead of changing all the other to xm. The reason why I chose xm1 to begin with was to reflect which package it came from and that is also why xp is only xp since it's a mix of both xp0 and xp1 :)
What do you say?

The reason why I chose xm1 to begin with was to reflect which package it came from
+1. I'd change it to xm1


figure out git and nano in anaconda prompt

windows users (probably) need to use the Anaconda prompt to run sphinx commands (sphinx-build, sphinx-quickstart). Git seems to be present in the standard anaconda installation, but not nano.
TODO:

figure out which git is available in the anaconda prompt
figure out why conda install -c anaconda nano didn't work on a windows machine (see https://anaconda.org/anaconda/nano)

a good working solution seems to be that windows users have two windows side-by-side, one with anaconda prompt and another with git-bash


document remedy for Error: pq: windower-limited: memory budget exceeded

Title
Fine-tune max-sql-memory best practice.
Description
Encountered getting Error: pq: windower-limited: memory budget exceeded: 112146104 bytes requested, 10240 currently allocated, 67108864 bytes in budget while running insert into fac_chrg select row_number() OVER () as fac_id,* from (select current_date(), random()::string, chrg_id from chrg_cd limit 7985445);
Outline
max-sql-memory describes how much RAM all SQL processors can take up on the whole cluster whereas sql.distsql.temp_storage.workmem is how much memory a single processor of a single query can use, so the former is “global” whereas the latter is “local”
There are couple other settings that describe how much memory joins and sorts can use before they are forced to spill to disk, but all other memory-intensive operations look at sql.distsql.temp_storage.workmem
cc https://cockroachlabs.slack.com/archives/C8HD41C82/p1575302414002600
potentially other issues to consolidate this:

https://github.com/cockroachdb/docs/issues/5923

Expected Audience
Developers and DBAs

I need your expertise in investigating an explain query. It is necessary to understand whether this problem takes place?
The request is associated with error 532000 windower-limited: memory budget exceeded.
The graph was built from the message above.

And how can the memory size for the window request be increased?

We have a private cluster setting (i.e. not explicitly documented) sql.distsql.temp_storage.workmem that determines how much memory a single processor in the query can use before it must spill to disk or bail on the execution. By default it is 64MiB.

@yuzefovich thanks!
Increasing to 100Mb solved the problem
SET CLUSTER SETTING sql.distsql.temp_storage.workmem = '100MB';

Is it possible to set this parameter by default somewhere? Or can it be configured only through a query?

Great to hear that it helped!
No, this cluster setting can only be changed via a query, but note that it is a "cluster setting" meaning that once set, it'll be that new value for all connections of the cluster.

@intech this can be verified by running show cluster setting sql.distsql.temp_storage.workmem;.  The example below showing the difference between MB use to set and MiB used in show.
> SET CLUSTER SETTING sql.distsql.temp_storage.workmem = '100MB';
show cluster setting sql.distsql.temp_storage.workmem;
  sql.distsql.temp_storage.workmem
------------------------------------
  95 MiB

> SET CLUSTER SETTING sql.distsql.temp_storage.workmem = '100MiB';
SET CLUSTER SETTING

Time: 10.601ms

root@:26257/defaultdb> show cluster setting sql.distsql.temp_storage.workmem;
  sql.distsql.temp_storage.workmem
------------------------------------
  100 MiB

@robert-s-lee oh, good point!

@robert-s-lee tell me how the memory allocation in the window function will work:

the required amount will be allocated depending on the ranges located on the node.
the virtual table will be created on one of the nodes and the required memory limit will be needed only on this node.
memory will be allocated on each node according to the virtual table

@intech here is some info. Keep in mind that we distribute the computations of the window function based on PARTITION BY clause (all rows belonging to the same partition must end up on the same node), so if the query doesn't specify PARTITION BY, then all the computations is done on a single node (the gateway).
There are three big users of memory space when computing the window functions:

we buffer up all the input data belonging to partitions that are assigned to the node, with no PARTITION BY clause that will be all of the input data
we separate out those - possibly multiple - partitions on the node and compute window functions one at a time
for every partition on the node we compute each window function and store the result of computation in memory.

Note that we don't emit any output until we have fully processed all window functions of all partitions on the node.
Going back to the discussion about the memory, we use disk-backed data containers for steps 1 and 2 (meaning that we can use temporary disk storage to store that data), but step 3 always keeps the result of computation of window functions in memory. It's likely that you're hitting a limit in that third step. Additionally, while looking through the code right now, I'm currently not sure whether we correctly fall back to disk in steps 1 and 2 in all of the cases (there might be a bug that would force us to mistakenly think we're still using the memory although we have spilled to disk and prevent new memory allocations for step 3 to occur even though they are within workmem limit), I'll need to double check that.

Very detailed and helpful answer. Many thanks.
If there is new information, leave in this issue, please.
I have some questions about the operation of the window function, I noticed that indexes are not used and all data inside the window function itself is selected, although there is a where in the query and the result really comes filtered.
At the same time, I see that instead of using the where clause of 900k records, total records (2.7kk) are selected, and after that it filters.
I tried to specify the index manually, then the request time increases several times, it selects 2 times. From the main index and specified by me and then combines from it.
I don't understand why this is happening, and even more questions arise about the correctness of such behavior.

Windower processor itself doesn't read the data from disk at all - all scan operations are done by the TableReader processor, and it is up the optimizer to decide which index to use in order to scan all the required data.
In the first case, the optimized chose to do a full table scan (on the primary index) with a filter on top, so that's why we see that 2.7m rows were read by the table reader but only 900k by the windower - other 1.8m were filtered out.
In the second case you forced the use of a secondary index, so now the optimizer use it for scanning, and the table reader scanned the desired 900k rows. However, that index doesn't contain all the columns that are needed to populate the end result (for window functions - arguments and ORDER BY clause - and for the final projection), so now we need to do a lookup join - from shares_reward_index we can only obtain reward and  uuid columns, but we also need created and difficulty, so we are performing a lookup using uuid column into the primary index to get those. And regarding the running time, it appears that the optimizer correctly estimated that the second plan is less efficient and only the index hint forced it to use that.
Hope this makes sense.

@yuzefovich I can't remember the last time I received such prompt and high-quality support! You are best!
Based on your comment, I can make an index with the necessary storing(uuid, difficulty, created) fields and thereby reduce the number of readable records? Since this base is just a small test, in the original billions of records.

Yes, I believe if you make such an index, then that index should be used by the table reader and there will be no filtering needed. Glad I could help :)

@yuzefovich We have reduced the time several times!

@drewdeally try SET CLUSTER SETTING sql.distsql.temp_storage.workmem = '100MB';


Removing All Language Headlines

@Butt4cak3 realized we no longer need the language headlines so this PR removes them. This can be seen in PR #245

I can't review the entire PR right now, but why is it that your PRs always have these random "Merge pull request" commits in them?

I think he has a fork of the project and commits to it but he has to pull the changes made in the original project so for this he created a pull request and forgot to remove it from the PR he makes on the original.

@lulucca12 is correct. Sorry about that I will make sure I don't do that in the future


Add stack_config_folder_name variable

what

Add stack_config_folder_name variable

why

The existing variable stack_config_path is used to read the YAML stack config using the terraform-yaml-stack-config module, and it needs to be a relative path to the stacks folder at the time of execution so the module could find the YAML config files. It's usually in the format ../../../stacks
On the other hand, we need to specify the name of the stack config folder to prefix the imports with it to be used in the Rego policies (it should not be a relative path to stack configs)

/test all


Is there a tag I can insert to exclude document from word count?

Problem
What problem would your idea solve? How do you currently manage this problem?
Currently all words in my weekly journal are included in the daily count. This includes numbers for time, rants and mundane details which I don't want to count towards my actual sense of achievement that day.
I could just have my routine in a separate document, but I often have uncontrolled brain farts which end up in there until I properly move them across to the right places.
To manage this presently I count my words added to my weekly journal and then subtract them from my total, then write that down in the weekly journal. Minus two more words, for the '#### words' I just wrote.
Idea
Describe the feature you want to suggest.
A (ExcludeFromBetterWordCount) tag that can be inserted perhaps as a comment at the top of a markdown document.
Thank you for your lovely work either way.

As of v2.19.0, published just now, you can add the exclude-from-word-count tag to frontmatter to exclude a note from most counts. For details, see the "Excluding notes" section of the README: https://github.com/isaaclyman/novel-word-count-obsidian/tree/master#excluding-notes


Testing GitHub Pull Request Builder Jenkins plugin

test this please

Adding a comment that shouldn't trigger build

test this please

test this please

Adding a comment that shouldn't trigger build


CSS collection

收集一些有趣實用好玩的 css 相關 plugin, preprocessor, tools...
知識文章:
Modular CSS

Myth
http://www.myth.io/
Myth is a preprocessor that lets you write pure CSS without having to worry about slow browser support, or even slow spec approval.
It's like a CSS polyfill.

Sass
http://sass-lang.com/
Sass is the most mature, stable, and powerful professional grade CSS extension language in the world.

CSS Stats
http://www.cssstats.com/
http://github.com/mrmrs/cssstats

stylelint
http://stylelint.io/
https://github.com/stylelint/stylelint
A mighty, modern CSS linter

css-loader
http://www.raphaelfabeni.com.br/css-loader/

Simple loaders for your web applications using only one div and pure CSS ♥.

cssreference
http://cssreference.io/

A free visual guide to CSS


Add legend for data

The exact meaning for a lot of the data columns are unknown.  Some research and adding that info onto the website somehow would be useful.

See the About page that we added.


Function.length

Is it at all possible to backport the length argument for FunctionTemplate?
It is supposed to set the length property of resulting functions to the number of expected arguments.
It was introduced in one of the newer v8 versions, but I think the property is part of the ES5 standard.
What changed in ES6 seems to be that it is now supposed to be configurable, presumably through Object.setOwnProperty.
In some v8-dev discussion I saw, they mentioned that this lead to some complications for them, (maybe the term was shadowing). This could be why the property is implemented as an accessor pair.
Would it not then be possible to hack up a solution by creating a FunctionTemplate without specified length and then manipulating its associated ObjectTemplate, adding a function returning the desired length, obtained through a template parameter, as the getter and a no-op function as the setter, before finally returning this Frankenstein's Monster to the user?
pseudocode
template <int I> NAN_GETTER(NanLengthGetter_) { return v8::Integer::New(I); }
NAN_SETTER(NanLengthSetter_) {}

NanNewFunctiontemplate(InvocationCallback callback=0, Handle< Value > data=Handle< Value >(), Handle< Signature > signature=Handle< Signature >(), int length) {
v8::Local<v8::FunctionTemplate> tpl = v8::FunctionTemplate::New(callback, data, signature);

tpl->InstanceTemplate()->SetAccessor (v8::String::New("length"), NanLengthGetter_<length>, NanLengthSetter_, Handle< Value >(), DEFAULT, static_cast<v8::PropertyAttribute>(v8::ReadOnly | v8::DontEnum));

return tpl;
}

Am I missing something important here?
Is it at all feasible?
Is there a simpler way?
@bnoordhuis: Perhaps you can shed some light on this?

Is it at all feasible?

I don't think so.  The .length property is effectively hard-coded into the function object instance with V8 3.14.

Is there a simpler way?

Not expose a way to set .length? :-)

I guess that is it indeed it then. Nothing seems to work for this particular property.