Drop shared PLTs support and change PLT name to .plt

I am worried about supporting the shared PLT location option because it will be very easy to use a PLT which is not suitable or has slightly different files than a project's dependencies. If there are two branches of an application with different versions of dependencies the same PLT probably should not be used.
I think it would be better to require a user to be specific about how they are sharing PLTs using the explicit directory location. Otherwise someone unfamiliar with dialyzer might think shared is an optimisation and end up using dialyzer incorrectly or in a sub-optimal fashion. That is, we should definitely make the optimisation available for those who need it (with the directory name option) but we should not make it too easy to do the wrong thing.
I also took this opportunity to change to the default PLT name to match that used (currently) by rebar3. It is very awkward to include the application name in the PLT's name because there can be multiple applications in a rebar3 release project. Without the shared option the PLT does not need to include the application name.

Where were you when I asked whether we should remove shared :)? Jokes aside, as I said on the list, I'm okay with removing shared, but I'm yet unconvinced about the filename change. If a user decides to have a ~/.cache/plts/ and put all PLTs there, it makes sense to include the app-name. If it's stored project-local, what's the problem with the old filename?
We can also remove all plt location options and add it later, if there's a feature request. Alternatively we could turn it into a full path option, but that would complicate if and how we embeded the OTP release string in the filename.
If we support *only* project-local PLTs and no option to copy it around (embedded beam paths), I'm okay with dropping the app-name.

/cc @ferd @asabil

Where were you when I asked whether we should remove shared :)?

Hehe, I didn't notice this until porting rebar3 to be compatible, sorry.

If it's stored project-local, what's the problem with the old filename?

In rebar3 there is direct support for an apps/ structure to include multiple top level applications for a release. This means the application name can not be used because their could be multiple applications.
Could we add an option plt_name or plt_prefix, which defaults to rebar, so that PLTs are name <plt_name>_<otp_version>_plt or similar? Rebar3 already has several users of a custom directory for the PLT.

What's included from the local projects in the rebar3 PLT? Do you have multiple PLTs for the top-level project? Where does rebar3 store the PLT by default?

The rebar2 PLT model is that you have a *single* project with rebar deps and what's configured in the .app file. These are included in the PLT. Your apps/ may also be used like deps. You need to properly maintain your .app file.

What's included from the local projects in the rebar3 PLT?

Once https://github.com/rebar/rebar3/pull/502 is merged it will include the same files as a rebar2 PLT with the caveat that erts, kernel``stdlib and crypto are always included (by default)

Do you have multiple PLTs for the top-level project? Where does rebar3 store the PLT by default?

The rebar3 PLT is stored in ./_build/<profiles>/ so the default location is ./_build/<profiles>/.

The rebar2 PLT model is that you have a single project with rebar deps and what's configured in the .app file. These are included in the PLT. Your apps/ may also be used like deps. You need to properly maintain your .app file.

rebar3 handles this situation perfectly. Lets stop worrying about what rebar3 does, it actually has tests to prove all these situations work correctly.

Once rebar/rebar3#502 is merged it will include the same files as a rebar2 PLT with the caveat that erts, kernelstdlib and crypto are always included (by default)

Adding kernel, stdlib, and crypto by default may work most of the time, but it's not a good idea, as you can build erlang apps with only erts. Somebody will request a feature to exclude apps from the hard-coded set.

The rebar3 PLT is stored in ./_build// so the default location is ./_build//.

Is it *one* PLT for each profile, or one for each app in each profile?

rebar3 handles this situation perfectly. Lets stop worrying about what rebar3 does, it actually has tests to prove all these situations work correctly.

I've tried to explain what rebar2's build-plt does, given how rebar2 projects work, trying to figure out whether the models and supported projects are different enough that unifying the naming schemes is pointless. From what I understand, with rebar3 custom PLT locations, you have to use extra sub-dirs to differentiate between app1's 18.0.plt and app2's 18.0.plt.

Adding kernel, stdlib, and crypto by default may work most of the time, but it's not a good idea, as you can build erlang apps with only erts. Somebody will request a feature to exclude apps from the hard-coded set.

Quite the opposite, it means rebar3 can do a lot less work (saving a couple of minutes on build time) and has always been fully configurable.

Is it one PLT for each profile, or one for each app in each profile?

It's one per profile per project. If a project contains multiple applications it is still one per profile.

I've tried to explain what rebar2's build-plt does, given how rebar2 projects work, trying to figure out whether the models and supported projects are different enough that unifying the naming schemes is pointless.

Rebar3 only builds the PLT in a different way, if it does not create the same PLT and analyse the same files it is a bug.

From what I understand, with rebar3 custom PLT locations, you have to use extra sub-dirs to differentiate between app1's 18.0.plt and app2's 18.0.plt.

With a simple rebar3 project (structured the same as rebar projects):
src/module.erl
_build/default/PLT

With a release structured project:
apps/app/src/module.erl
_build/default/PLT

The application name can't be used in the release structured project because there could be multiple applications.
The reason for a unifying naming scheme is so that {plt_location, Dir}, where Dir is a directory, points to the same file.

Once rebar/rebar3#502 is merged it will include the same files as a rebar2 PLT with the caveat that erts, kernelstdlib and crypto are always included (by default)

It is possible to fix this caveat if required for compatibility.

and has always been fully configurable

You didn't say so, and I could have assumed it, but it's fine if the default set can be overridden.

The application name can't be used in the release structured project because there could be multiple applications.

That's my point. rebar3 works without a master (aka top) project, and treats all apps equally. This is not the case in rebar2, and hence the possibility of including the app name for simple custom location dirs.

The reason for a unifying naming scheme is so that {plt_location, Dir}, where Dir is a directory, points to the same file.

Same reason the filename is generated in rebar2 and why I called it "location" (not "dir").
I've read your comments twice, but I cannot see an explanation for how plt1 and plt2 are stored in a shared location, without extra sub-dirs.
If not app name (which is the top project name in rebar2), you surely have a project name, don't you?

To not block 2.6.0, perhaps we should reduce the patch to a simple shared removal and leave the naming scheme for later.

To not block 2.6.0, perhaps we should reduce the patch to a simple shared removal and discuss naming schemes independently.

Rebar 2.x can totally be made to ignore a top-project by specifying additional directories or running commands with -r; it's a common usage pattern even for releases, though it's unfriendly and usually an uphill battle doing so.

I've read your comments twice, but I cannot see an explanation for how plt1 and plt2 are stored in a shared location, without extra sub-dirs.

Ah, I was confused, I thought we were talking about when used in an /apps project! It has not come up as an issue and just use sub-dirs myself.
@ferd can you think of naming scheme that works for both that allows a global directory to contain PLTs from multiple projects?

{ok, Pwd} = file:get_cwd(), %% or use project root dir
integer_to_list(erlang:phash2(Pwd)) ++ "-" ++ OTPVsn ++ ".plt"

Then it becomes invalid if you move directories around I guess. Rebar3 would need to add the profile (or a different directory) to that seed. Not sure I like it.

So requiring sub-dirs for global PLTs is not an option for rebar2? If so I will remove the naming scheme change and accept the incompatibly.

I have force pushed to only remove shared PLTs. Given that removing the application name from the PLT in rebar could detract from the user experience (have to use sub-dirs to share a PLT) I think its best to leave the name as is.
Rebar3 can switch the PLT name to <prefix>_<otp_version>_plt, where the prefix defaults to a constant value such as rebar3 or otp and add an option plt_prefix, which can be set to the application name if someone wants to share PLTs between rebar and rebar3. Thoughts?

Thanks, can you append your name in THANKS and update rebar.config.sample, all as part the original commit?

Amended.

Thanks. Do we actually still need {plt_location, local}, or should we transform it into an optional {plt_dir, "dir"}? I'm okay with 643f045, just putting the question up for final discussion before we merge. @ferd?

local is useful in rebar3 because it allows a profile to "undo" the plt_location set by another (or the default) profile. A commit adding configuration compatibility is available here: https://github.com/fishcakez/rebar3/commit/74f62a62fe5eca1bcd36df6541330cd6ff52065f#diff-10e271abea3a3fa058f7fb38aa685fdeR115. The BaseDir on that line includes the profile combination and assuming the default profile is ./_build/default/ but could be ./_build/test+dev/default.

Oh dear, I've just realised I used dialyzer_opts instead of dialyzer.

Okay, let's keep local then. In that case, this should be ready to merge.

Can we please merge this?


Add seeds for FeedbackMessage to fill up the feedback dashboard

Resolves #1832
Description
This PR should help out the Staging/Dev environments to show up some test information about Feedback Messages.

Type of change

New feature (non-breaking change which adds functionality)

How Has This Been Tested?
I tested this out setting up the app DB (rails db:setup) and expecting the feedback messages being filled up for a  freshly DB setup.

LGTM though I think the issue requested that the README.md be updated to reflect login creds? (check bullet item 3 on the issue)
I'll mark it approved tho. Thanks!

Hey, @armahillo I think we are all set. It was not necessary to touch in any Admin user. So the Readme remains the same. Does it make sense for you?


Add LICENSE file

It would be a good idea to add a LICENSE file with the appropriate license text.  Package.json indicates MIT.

Ok thanks for reminding


Fix some typos

keyd is an awesome project! Thanks for creating it.
I just noticed some typos and fixed them (and then I let vim's spell checker check both the README and the manual).

Oops. How embarrassing. I suppose that is what I get for not turning on my spellchecker :P.


Add parameter to fail on specific impact levels

For the following issue #9

@eoinobrien , this was released in v2.0.0!

@eoinobrien , this was released in v2.0.0!


Stop auto focus on DropdownMenu.Item

Bug report
Current Behavior
I want to put an input element as one of my dropdown menu items.
My problem is that whenever I start to type something and move my cursor over other items, my input loses focus.
<DropdownMenu.Root>
    <DropdownMenu.Trigger />

    <DropdownMenu.Portal>
      <DropdownMenu.Content>
        <DropdownMenu.Item />
               <input ... />
          <DropdownMenu.Item />
        <DropdownMenu.Separator />
        <DropdownMenu.Item />
               text item
          <DropdownMenu.Item />
      </DropdownMenu.Content>
  </DropdownMenu.Root>

Expected behavior
I want to be able to keep the focus on my input element (and keep typing) even if I move the cursor over other items.
Your environment

Software
Name(s)
Version

Radix Package(s)
@radix-ui/dropdown-menu
2.0.4

React
n/a
18.2.0

Node
n/a
18.16.0

npm/yarn

Operating System
macOS  Ventura
13.3.1

Hi @itaikeren , any update?

Hi, I have same issues, is there any update?

Running into this issue. I'm using the Dropdown in a text format bar component (similar to Notion), and I want to preserve the focus on the selected text. It would be great to have some way of opting out of the autoFocus behavior.

Any workarounds? This is quite a pain.

I have the same issue

Hey, sorry for the late response.
The only workaround I found for now is to add those lines to the <Dropdown.Item> component:
<Dropdown.Item>
	...
	onPointerLeave={(event) => event.preventDefault()}
	onPointerMove={(event) => event.preventDefault()}
	...
</Dropdown.Item>

It will disable the auto-focus for each dropdown item when you hover over it.

I got it working by wrapping my Input with a div, and adding a onKeyDown={e=>e.stopPropagation()}
like this

 e.stopPropagation()}>
  <Input
    placeholder={t.filter[lang]}
    value={search}
    onChange={(e) => {
      e.stopPropagation();
      e.preventDefault();
      setSearch(e.target.value);
      // bug in radix ui
      // setTimeout(() => e.target.focus(), 100);
    }}
  />

None of the above solutions worked for me. I tried overriding basically every mouse event I could find and nothing would stop the input box from losing focus when my mouse left.

Running into this issue. I'm using the Dropdown in a text format bar component (similar to Notion), and I want to preserve the focus on the selected text. It would be great to have some way of opting out of the autoFocus behavior.

onCloseAutoFocus works for me: https://www.radix-ui.com/primitives/docs/components/dropdown-menu#content
<DropdownMenuContent
        onCloseAutoFocus={(e)=>{e.preventDefault(); e.stopPropagation();}}
...

I got it working by wrapping my Input with a div, and adding a onKeyDown={e=>e.stopPropagation()}
like this

 e.stopPropagation()}>
  <Input
    placeholder={t.filter[lang]}
    value={search}
    onChange={(e) => {
      e.stopPropagation();
      e.preventDefault();
      setSearch(e.target.value);
      // bug in radix ui
      // setTimeout(() => e.target.focus(), 100);
    }}
  />

this solution also works for shadcn-vue that uses  "radix-vue" as components


Print ER Diagram to PDF has Font Issue

Trying to print ER Diagram.  It prints it, but the text is largely illegible when using Microsoft Print to PDF.  See attached image.

Hello @KipmarkMR,
Looks that your issue is caused by having a display scaling above 100%.
As a workaround you can set it to 100%.

Thanks for the reply.
Where is "display scaling" set?  I never changed anything... by default it is set above 100%
Are you talking about this:

If so, it is set to 100%.  Did you mean something else?

I'm talking about system's settings.


Remove dead code in nvme driver which may cause system hang

NvmeHcPciBase is the data used to select PCI BDF and register offset in CF8 port in PCI scan. Use it to access MMIO region is a bug. In some cases, the buggy address falls into iGPU stolen memory and such read access will cause bus hang later.
Tracked-On: OAM-115757

Android CI has started Engineering Build for this issue ,Please check the linked Tracked-On issue/Android CI Web  for more details.

SUCCESS: Android CI has completed Engineering Build for this issue.Please check the linked Tracked-On issue/Android CI Web  for more details.

Android CI has started MERGE Build for this pr ,Please check the linked Tracked-On issue/Android CI Web  for more details.

Android CI has completed MERGE Build for this pr, build is SUCCESS. Please check the linked Tracked-On issue/Android CI Web  for more details. For Binaries: /cactus-absp-or-local/celadon_smr0_master-merge/887


Noob - is it possible to use this with python2.7?

I have done some reading and attempts with future but not able to get it working.
I have it installed and working with python3 code so that part is fine.
Is it doable? Any sample code?

I think I used a few Python 3-only language or library features, so it probably won't work without lots of fixing.


PoC: multi-version architecture

High-level proof of concept for adding V2 support to the existing juice-interface repository. See the RFC on Notion: https://www.notion.so/juicebox/Frontend-V2-support-49fb4a50c658483fa146c793503bcb51#0c1ed6e84e644ec385fbccd57e364f45
What this PR does

adds the @jbx-protocol/contracts-v2 dependency
adds a Vx suffix to the filename of any version-specific hook, context or constant (like contract names). Also puts these in a v1/ directory.
moves most of the modals directory to to Dashboard/modals (most modals are dashboard-specific)
renames Dashboard to DashboardV1
duplicates DashboardV1 into DashboardV2
adds logic to the Router to render DashboardV2 when we encounter a V2 project: source
wraps the DashboardV2 component in both UserProviderV1 and UserProviderV2. This is so we can iteratively (and in parallel) rewrite DashboardV2 to use the V2 contracts.
rewrote parts of the Create Project page to deploy a minimal V2 project: source
started rewriting the DashboardV2 to load a V2 project. I think the project handle works: source

We've decided to start pursuing this approach. I'll close this PR and start making iterative PRs towards this.


Adding Stitches.js detection

in this pr i added Stitches.js detection
it is a new css-in-js lib that is framework agnostic and support SSR and other cool features
stitches repo
it is used in
https://ped.ro/
https://vercel.com/dashboard
https://uiw.tf/

Thanks!

You are welcome ! thank you for the awesome tool i use everyday 😌


ParMETIS does not compile on femto/intel with failure to include  "GKlib.h"

@pvelissariou1
cd thirdparty_open/parmetis
make config
make

results in
make[3]: Entering directory `/sciclone/home20/clemmen/devel/noaa/CoastalApp/thirdparty_open/parmetis/build/Linux-x86_64'
[  1%] Building C object libparmetis/CMakeFiles/parmetis.dir/akwayfm.c.o
cd /sciclone/home20/clemmen/devel/noaa/CoastalApp/thirdparty_open/parmetis/build/Linux-x86_64/libparmetis && /usr/local/skylake/linux-centos7-x86_64/intel-18.0.5/openmpi-3.1.4-nrpbrsazh5ctfqireohisqylydu43wne/bin/mpicc  -I/sciclone/home20/clemmen/devel/noaa/CoastalApp/thirdparty_open/parmetis/include -I"/sciclone/home20/clemmen/devel/noaa/CoastalApp/thirdparty_open/parmetis/~/local/include" -I/sciclone/home20/clemmen/local/include -I/sciclone/home20/clemmen/devel/noaa/CoastalApp/thirdparty_open/parmetis/libparmetis/.  -DLINUX -D_FILE_OFFSET_BITS=64 -xHost -DNDEBUG -DNDEBUG2 -DHAVE_EXECINFO_H -DHAVE_GETLINE -O3   -o CMakeFiles/parmetis.dir/akwayfm.c.o   -c /sciclone/home20/clemmen/devel/noaa/CoastalApp/thirdparty_open/parmetis/libparmetis/akwayfm.c
In file included from /sciclone/home20/clemmen/devel/noaa/CoastalApp/thirdparty_open/parmetis/libparmetis/akwayfm.c(14):
/sciclone/home20/clemmen/devel/noaa/CoastalApp/thirdparty_open/parmetis/libparmetis/./parmetislib.h(20): catastrophic error: cannot open source file "GKlib.h"
  #include <GKlib.h>
                    ^

compilation aborted for /sciclone/home20/clemmen/devel/noaa/CoastalApp/thirdparty_open/parmetis/libparmetis/akwayfm.c (code 4)

Try to use the develop_build branch (soon to be merged with develop). Build scripts have been updated (scripts/*) to accommodate ParMETIS builds for both Intel and GNU.

Please use develop_build branch (soon to be merged with develop).
See issue https://github.com/noaa-ocs-modeling/CoastalApp/issues/138
for more details on ParMETIS compilation issues.
Use scripts/download_parmetis.sh to download ParMETIS.

While trying this, I noticed that on macOS it fails with
/Users/Lemmen/devel/noaa/CoastalApp-dev/thirdparty_open/parmetis/GKlib/graph.c: In function 'gk_graph_Read':
/Users/Lemmen/devel/noaa/CoastalApp-dev/thirdparty_open/parmetis/GKlib/graph.c:297:26: error: format '%lld' expects argument of type 'long long int *', but argument 3 has type 'ssize_t *' {aka 'long int *'} [-Werror=format=]
  297 |         if (fscanf(fpin, "%"SCNd64" %"SCNd64, &i, &i) != 2)
      |                          ^~~                  ~~
      |                                               |
      |                                               ssize_t * {aka long int *}
In file included from /Users/Lemmen/devel/noaa/CoastalApp-dev/thirdparty_open/parmetis/GKlib/./gk_arch.h:43,
                 from /Users/Lemmen/devel/noaa/CoastalApp-dev/thirdparty_open/parmetis/GKlib/./GKlib.h:23,
                 from /Users/Lemmen/devel/noaa/CoastalApp-dev/thirdparty_open/parmetis/GKlib/graph.c:10:
/Applications/Xcode-beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/inttypes.h:157:53: note: format string is defined here
  157 | #  define SCNd64        __SCN_64_LENGTH_MODIFIER__ "d"

I tested with the develop_build branch and it worked on femto.
Also tested on linux  with the develop_build branch and it worked.
Thanks for your clarification, please merge speedily into develop so we can pull the changes downstream


Add simple profiling for test automation

What this PR does / why we need it:
Simple execution time output is now rendered when KUBEVIRT_PROFILE_MAKE=1
is used. This is set in automation/test.sh by default.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

I assume the purpose of this PR is to ease debugging. Am I correct @dhiller?

I assume the purpose of this PR is to ease debugging. Am I correct @dhiller?

Yes, ATM we have problems with slow CI builds and want to know where the most time is consumed.

Thanks, @dhiller. Please include This level of motivation in the primary message of PRs, so that laypersons like me would have a chance to differential a helper PR like this from a PR that that solves something.

Closing this in favor of kubevirt/kubevirt#3609


installer for Arm64

Hello, I'm trying to use your script to migrate my postgres12 database to postgres15 in Ghostfolio, but I'm using a system with an arm64 processor. Could you create a special version, or explain how I could create one? I'm not a programmer, so I don't have advanced skills.
thanks

Hi @Pindol83,
Thank you for getting in touch. The current script does not handle the migration of data from an existing running instance. However, I will explore the possibility of providing an arm64-based image for you to use on your server.
If you're interested in upgrading Postgres from version 12 to 15, you can refer to the following post in the Ghostfolio repository: How to upgrade from PostgreSQL 12 to 15? #2509.
I recommend attempting this migration only if you possess a basic understanding of Docker and databases.
I will notify you once I've an update on the arm64-based image.

Thanks, I'll take a look tomorrow. Anyway, I think it would be interesting, not only for me, to have an ARM version of your script for migrating from Postgres 12 to Postgres 15.

Hey @Pindol83 ,
I've just introduced an arm64-based image:
docker pull leonstoldt/ghostfolio-installer:latest_arm64

Unfortunately, I couldn't test it on an arm64 system. Please give it a try and share your feedback on whether it works. If successful, I'll consider this issue resolved.

"interesting [...] to have an ARM version of your script for migrating from Postgres 12 to Postgres 15 (without data)."

You should be able to launch a new ghostfolio with Postgres 15 (empty) using the arm image and migrate the data via the discussion thread mentioned earlier (utilizing pgdump).


cannot import name 'get_config' from 'tensorflow.python.eager.context'

I am doing an object detection project on google colab. I have installed dependencies as indicated in the following article - https://medium.com/deepquestai/train-object-detection-ai-with-6-lines-of-code-6d087063f6ff
But when i run the code for training, it shows the following error -
ImportError: cannot import name 'get_config' from 'tensorflow.python.eager.context' (/usr/local/lib/python3.7/dist-packages/tensorflow/python/eager/context.py)
I have tried different versions of tensorflow after that but it doesnt work. How exactly can i remove this error?
Also If i am trying to detect multiple objects through a custom dataset, how should the directory structure of the dataset be?
Is it something like this -
Dataset -> train -> Object1 -> images, annotations
Object2 -> images, annotations
Dataset -> validation -> Object1
Object2

try to install tensorflow==2.5.0rco and keras==2.5.0rc0 if you using python3.8


A potential risk of kubecost makes a worker node get the token of any Service Account

Summary
The Kubecost in GKE gave excessive authority when defining Service Account named "kubecost-1-cost-analyzer-serviceaccount-name-dff5" "kubecost-1-cost-analyzer-prometheus-serviceaccounts-server-name-e82d" and "kubecost-1-deployer-kvsqj". Besides, these Service Accounts are mounted into pod, witch makes it possible for attackers to raise rights to administrators.
Detailed Analysis

We deployed Kubecost  in the marketplace of Google's GKE cluster by default.

The clusterrole named "default:kubecost-1:cost-analyzer.serviceAccount.name-r0" defines the "*" verb of "pods, deployments, replicationcontrollers and nodes". And this clusterrole is bound to the Service Account named "kubecost-1-cost-analyzer-serviceaccount-name-dff5". The Service Account is mounted into the pod named "kubecost-1-cost-analyzer-789fc48778-xgpkg".

The clusterrole named "default:kubecost-1:cost-analyzer.prometheus.serviceAccounts.server.name-r0" defines the "*" verb of "pods, jobs, deployments, statefulsets, replicationcontrollers and nodes". And this clusterrole is bound to the Service Account named "kubecost-1-cost-analyzer-prometheus-serviceaccounts-server-name-e82d". The Service Account is mounted into the pod named "kubecost-1-prometheus-server-6f9d5c9989-l972j".

The clusterrole named "default:kubecost-1:deployerServiceAccount-r0" defines the "*" verb of "clusterroles and clusterrolebindings". And this clusterrole is bound to the Service Account named "kubecost-1-deployer-sa". The Service Account is mounted into the pod named "kubecost-1-deployer-kvsqj".

Attacking Strategy
If a malicious user controls a specific worker node which has the pod mentioned above, or steals one of the SA token mentioned above.He/She can raise permissions to administrator level and control the whole cluster.
For example,

With the "*" verb of "clusterroles and clusterrolebindings", attacker can elevate privileges by creating a clusterrolebinding resource and binding cluster-admin to their own Service Account.

With the "*" verb of "pods, jobs, deployments, statefulsets, replicationcontrollers", attacker can elevate privileges by creating a pod to mount and steal any Service Account he/she want.

With the "*" verb of nodes, attacker can hijack other components and steal token by adding a "NoExecute" taint to other nodes.

Mitigation Discussion

Developer could use the rolebinding instead of the clusterrolebinding to restrict permissions to namespace.

Developers could define precise permissions for workload resources, including pods, deployments, jobs, statefulsets, replicationcontrollers , rather than using wildcard (*).

The "kubecost-1-deployer" appears to be used for initialization, and developers can delete resources such as the corresponding pod or Service Account after they are no longer needed.

A few questions

Is it a real issue in Kubecost?
If it's a real issue, can Kubecost mitigate the risks following my suggestions discussed in the "mitigation discussion"?
If it's a real issue, does Kubecost plan to fix this issue?

Reporter list

Xingyu<EMAIL_ADDRESS>me)
Nanzi Yang(952508578nanziyang<EMAIL_ADDRESS>Xunqi<EMAIL_ADDRESS>Xin<EMAIL_ADDRESS>Wenbo<EMAIL_ADDRESS>Jinku<EMAIL_ADDRESS>
Looking forward to your reply. Regards Xingyu Liu

Hi @sparkEchooo, this is the wrong repository for your report. Please open an issue on https://github.com/kubecost/cost-analyzer-helm-chart, that is the repository which controls this resources you are concerned about.

Hi, thanks for your reminder.
I will resubmit this issue on the repository you mentioned. :)


feat: support mermaid graphs

Hello i have installed mark 8.4 but the mermaid graph is not working in confluence it displayed this error in confluence page unknown macro: cloudscript-confluence-mermaid
Plz help.


[Bug] typo maxIdelTime

Search before asking

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

Version
master
What's Wrong?
there's a typo maxIdelTime in java files and be.conf :
https://github.com/apache/doris/blob/master/fe/be-java-extensions/jdbc-scanner/src/main/java/org/apache/doris/jdbc/JdbcExecutor.java#L91
private int maxIdelTime;
https://github.com/apache/doris/blob/master/conf/be.conf#L22
-DJDBC_MAX_IDEL_TIME=300000
What You Expected?
it should be maxIdleTime.
How to Reproduce?
No response
Anything Else?
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

-DJDBC_MAX_IDEL_TIME=300000 is passed as an argument to the JVM started by the BE process, and then JdbcExecuter will take the value of JDBC_MAX_IDEL_TIME and assign it to maxIdelTime. Then put it into the Druid connection pool for use.
You should pay attention to:
https://github.com/apache/doris/blob/master/fe/be-java-extensions/jdbc-scanner/src/main/java/org/apache/doris/jdbc/JdbcExecutor.java#L106
maxIdelTime = Integer.valueOf(System.getProperty("JDBC_MAX_IDEL_TIME", "300000"));

Thank you for reviewing code!


Don't overreact to calibration jumps

With oref0-g4-loop we now have calibrations available in glucose.json, so it'd be good to have oref0 disable SMB right after calibrations to avoid bolusing on a calibration uptick.

I was considering the same problem over the last couple of days. Lookout and xdrip-js-logger can provide the last calibration value and time. What are the contents of a oref0-g4-loop calibration record?
However this is implemented, it would be nice to be able to post a calibration record to the oref0 xdrip server to accomplish similar results if xdrip is being used.

I'm currently testing a change in the go-dexcom branch that pulls cal and mbg records from NS (https://github.com/openaps/oref0/commit/60213bc40fcb3887a6c771158f9d69607bbacffb) and stops processing older SGVs if it comes across a cal record (https://github.com/openaps/oref0/commit/07f1e555b11cabbc9d84d87cf8f34a1ae5b43454).
That will prevent calibration jumps from being included in the avgDeltas, and will prevent oref0 from responding aggressively when calibrating while rising, because it will need to get ~15m of data before it can calculate a longAvgDelta > 0.  But when BG is falling, the minDelta will be able to kick in on the second data point after the calibration.  We also now prevent looping entirely when both shortAvgDelta and longAvgDelta are exactly 0, so it will only cancel high temps and shorten long zero temps when there is only a single CGM reading after the last cal record.

Another approach, (which might or might not be a good idea - i'm not sure - but i'm just mentioning it for discussion) is to recalculate the past n svgs using the new calibration record. xdrip+ already has an option to do that, though it doesn't seem to update the previous entries in ns.
The approach suggested here also  seems a bit aggressive when previous calibration was actually correct, and it seems like it might unnecessarly limit the loop for 15m in that case.

This will prevent SMBs or high-temps for up to 5m after a cal record, until the next SGV.  It will then limit (for 20-30m) the use of rising BG to justify SMBs and high-temping.  Given that the PWD can decide when to calibrate and should already be trying to avoid calibrating when BG is rising fast, that seems like an acceptable limitation to me.
I do agree we should consider how best to use the filtered and unfiltered values available from Dexcom sensors.  To date the main use case for them has been during sensor restart, but I can see retrospective recalibration being a useful enhancement in the future.  I think this PR is a good safety improvement in the meantime, though.

Ah, the title was saying 15m. I should review this more closely.
I personally, often calibrate before by evening meal. Will this stop/delay the smbs on the meal, if i calibrate, and then enter some carbs shortly after?

As long as there is 30m between your calibration and the actual BG rise from the meal, it wouldn't affect you.  The expected rise from the carbs you entered will still be applied to the post-calibration SGVs, and it will SMB for those as normal: it will just ignore any positive deltas (since minDelta will be zero) until longAvgDelta starts getting calculated ~30m after the calibration.

@scottleibrand this is in 0.7.0 now, correct? If so, please comment with link or otherwise update.

No, this is still in the go-dexcom branch: https://github.com/openaps/oref0/blob/go-dexcom/lib/determine-basal/determine-basal.js#L77-L83 and https://github.com/openaps/oref0/blob/go-dexcom/lib/glucose-get-last.js#L19-L22

Implemented in #677 and modified in #717


Add support for Hyper Terminal

Hyper Terminal is already supported, feel free to use it.

clime me to reach out!


New Events Page - tests and move folders

This is the final PR for the events feature. This PR adds some tests, and moves the new events files into the regular events folder, deletes the old duplicates (like EventsPage) and renames a few components still being used in communities (EventsList => CommunityEventsList), etc.
NOTE: This will merge into the feature branch, not develop.
Web frontend checklist

[ x ] Formatted my code with yarn format
[ x ] There are no warnings from yarn lint --fix
[ x ] There are no console warnings when running the app (well, no new ones...)
[ ] Added any new components to storybook
[ x ] Added tests where relevant
[ x ] All tests pass
[ x ] Clicked around my changes running locally and it works
[ x ] Checked Desktop, Mobile and Tablet screen sizes

FYI a lot of this was reviewed already. It just looks new as I moved the files into the existing events folder. It's really the tests that are new (and the file moving).

LGTM (sehr gut, wie immer :D)

for me it's an approve, but I rather wait until aapeli/darren feedback

Merging as we discussed in DM it was okay since just tests and goes to feature branch.


New Zealand

Same
I am obviously not in New Zealand, but Google thinks I am, so it won't let me install the app.

Hello @Nemo157 and @immibis ,
the following article describes the current state of the international app store availability: https://www.coronawarn.app/en/faq/#international.
Thank you for sharing your idea of adding New Zealand to this list.
@immibis a workaround would be to change your Google Play country: https://support.google.com/googleplay/answer/7431675?hl=en
Best regards,
LMM
Corona-Warn-App Open Source Team

I think the reasons people are unwilling to change their Google Play country include: they cannot change it again for another year (so they will have the opposite problem in their home country); and it could make other apps unavailable, and there is no way to predict whether that will happen.


Error in npm workspaces monorepo

Hi I'm trying out Solid Start (and solid) to get a feeling of the framework.
When building or starting the dev server from an npm workspaces monorepo i get this error:
cician@ciciomp:/tmp/solid-start-ws/packages/site$ npm run build

> build
> solid-start build

 solid-start build
 version  0.2.5
failed to load config from /tmp/solid-start-ws/packages/site/vite.config.ts
node:fs:1438
  handleErrorFromBinding(ctx);
  ^

Error: ENOENT: no such file or directory, scandir 'node_modules'
    at Object.readdirSync (node:fs:1438:3)
    at detectAdapter (file:///tmp/solid-start-ws/node_modules/solid-start/vite/plugin.js:555:6)
    at solidStart (file:///tmp/solid-start-ws/node_modules/solid-start/vite/plugin.js:590:72)
    at file:///tmp/solid-start-ws/packages/site/vite.config.ts.timestamp-1668372870119.mjs:5:13 {
  errno: -2,
  syscall: 'scandir',
  code: 'ENOENT',
  path: 'node_modules'
}
npm ERR! Lifecycle script `build` failed with error:
npm ERR! Error: command failed
npm ERR!   in workspace: site
npm ERR!   at location: /tmp/solid-start-ws/packages/site

Reproduction:
mkdir solid-start-ws
cd solid-start-ws
echo "{\"workspaces\": [\"./packages/*\"]}" > ./package.json
mkdir packages
mkdir packages/site
cd packages/site
npm init solid
# chose bare, ssr=false and ts=true
npm install
npm run build

Builds and runs fine in a simple project without npm workspaces so for now I'll just continue with a simpler setup or a workaround.
Thanks and keep up with the good work.

I got around it by manually creating an empty node_modules folder...

Also running into this issue in an nx monorepo when trying to run the build command. Have used patch package with the changes from #435 for now, seems to fix the issue.


Awaiting analysis to complete.

I upgrade my plugin today.
Twenty minutes later, there is no score yet.
url: https://pub.dartlang.org/packages/flutter_ijkplayer#-analysis-tab-

It looks like document analysis takes too much time.

Thanks for the report, @isoos, did we fix this by removing the old datastore entity?

The analysis was done at 2019-04-10T09:52:18.183947Z. Do you recall at what time did you delete the record?

10.11 UTC, so this appears unrelated.

I may be unrelated to the fix, but I think it was related to the delay. If we hadn't had that entry, the analysis should have happened much sooner.

@CaiJingLong: Thanks for reporting it. Usually analysis can take anywhere from a few minutes to an hour, and in this case it took unusually longer. I'll add a few changes in the triggers to make it happen faster for new uploads.

Thx for work.


Game Debugger closes immediately

Scenario 1

create a new project
import through the asset library
start the debugger
window opens, and closes immediately

Scenario 2

clone repository
import as project from disk
start the debugger
window opens, and closes immediately

Both scenarios produce no errors nor any feedback in the console.

engine version?

4.22

@KoBeWi you can close this now. I've found the problem was specific to my development laptop. It was an incompatibility with a global vulkan reshade configuration.


Add support for external infra clusters in KubeVirt platform

This PR aims to provide an option to create guest cluster infra workloads (VMIs) on another cluster than the management cluster in which hypershift operator is running. It is done by passing a kubeconfig file path as an argument (--external-cluster-kubeconfig-file) to the hypershift create cluster kubevirtCLI command, which in turn will:

create a secret containing the kubeconfig
link it as a secret reference in the KubeVirt stanza in HostedCluster CR
add it to the KubeVirtCluster CR for consumption via CAPK

Signed-off-by: Oren Cohen<EMAIL_ADDRESS>
What this PR does / why we need it:
Provide option to deploy kubevirt-based guest clusters on external infra clusters than the management cluster.
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #
Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

/hold
route53 rate limiting is jamming everything up and need to get https://github.com/openshift/hypershift/pull/2018 to fix it
Can remove hold after it merges.

Hi @davidvossel ,
I addressed most of your comments, I simplified the API - removed the name field from the external kubeconfig struct and it is now just the kubeconfig contents.
However, when trying to test it e2e, CAPK was complaining it cannot unmarshal the kubeconfig.
This is the error given:
E0112 17:02:56.955644       1 controller.go:317] controller/kubevirtmachine "msg"="Reconciler error" "error"="failed to generate infra cluster client: failed to create REST config: couldn't get version/kind; json parse error: json: cannot unmarshal string into Go value of type struct { APIVersion string \"json:\\\"apiVersion,omitempty\\\"\"; Kind string \"json:\\\"kind,omitempty\\\"\" }" "name"="guest1-48mcs" "namespace"="clusters-guest1" "reconciler group"="infrastructure.cluster.x-k8s.io" "reconciler kind"="KubevirtMachine"

Looks like the error is coming from here:
https://github.com/kubernetes-sigs/cluster-api-provider-kubevirt/blob/main/pkg/infracluster/infracluster.go#L75-L78
But I was unable yet to decipher what is exactly wrong with the kubeconfig inside the secret. the contents in the secret are a valid kubeconfig file given by openshift-installer (base64-encoded).

However, when trying to test it e2e, CAPK was complaining it cannot unmarshal the kubeconfig.

@orenc1 It's hard for me to say why that's happening right now. What I do know is that this capk logic is being exercised by our upstream e2e test suite here. Maybe that will offer some clues into why it works for the upstream kubeconfig but not the one you're testing with.
So in that upstream test example, the kubeconfig that's being parsed is the one that's generated by kubevirt-ci. Even though we know this scenario will fail, you could take a kubeconfig generated for a kubevirtci cluster at try it with your hypershift cluster to see if the same marshaling error occurs... obviously that kubeconfig is useless, but it might give you a data point if we know it at least gets parsed correctly.

One thing we probably need to start thinking about is what namespace the VMs will be running in on external infra.
Right now the VMs automatically get placed in the HCP's namespace, but on external infra that namespace won't exist. We'll either need to create a namespace, or require that a namespace is provided along with the kubeconfig to indicate where the VMs shoudl run on the external infra... We might need to consider a network policy for isolation as well for the VM pods on the external infra.

The VMs on the external cluster will run at the same namespace as it was if they were created on the management cluster. I added a namespace definition for the Kubevirtmachine.spec.template.objectmeta.namespace at:
https://github.com/openshift/hypershift/pull/2017/files#diff-2d8fde4a95d3b1dc2de630b5b40ce849f937a940143e4b117ab32f22cec760a9R242
If the namespace does not exist, the VMs won't be created.
They will be created once the namespace is created, because the controller is looping on that.

/test kubevirt-e2e-kubevirt-aws-ovn

/test kubevirt-e2e-kubevirt-aws-ovn

/test kubevirt-e2e-kubevirt-aws-ovn

/test kubevirt-e2e-kubevirt-aws-ovn

/test kubevirt-e2e-kubevirt-aws-ovn

/test kubevirt-e2e-kubevirt-aws-ovn

/retest

/retest

/test kubevirt-e2e-kubevirt-aws-ovn

Hi @davidvossel ,
Your comments have been addressed.
/test kubevirt-e2e-kubevirt-aws-ovn

#2230 is required for the CI, but should be removed when using release payload outside of openshift-ci
/test kubevirt-e2e-kubevirt-aws-ovn

/test kubevirt-e2e-kubevirt-aws-ovn

/test kubevirt-e2e-kubevirt-aws-ovn
nodes on the latest kubevirt test run never came online. It looks like the network never became available for some reason.
    message: 'container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady
      message:Network plugin returns error: No CNI configuration file in /etc/kubernetes/cni/net.d/.
      Has your network provider started?'

/test kubevirt-e2e-kubevirt-aws-ovn

cluster bootstrapping issues
/test kubevirt-e2e-kubevirt-aws-ovn

/test kubevirt-e2e-kubevirt-aws-ovn

/test kubevirt-e2e-kubevirt-aws-ovn

/test kubevirt-e2e-kubevirt-aws-ovn

/test kubevirt-e2e-kubevirt-aws-ovn

the 2nd guest node didn't came ready due to an error in ovnkube-node:
failed to start default network controller: error looking up gw interface: "br-ex", error: Link not found

will try to get journal logs next run
/test kubevirt-e2e-kubevirt-aws-ovn

ci/prow/kubevirt-e2e-kubevirt-aws-ovn passed.
/hold cancel


When testing on new image the code stops at Gtk-WARNING **: cannot open display

So I'm running the code remotely on a server with GPU, and the first thing I'm trying to do is download the pretrained models and look at how they perform at samples images. I've run the following line
 python2 fc4.py test pretrained/colorchecker_fold1and2.ckpt -1 sample_inputs/37.jpg
(I have a 37.jpg image saved in sample_inputs folder)
I've run the code but it says Gtk-WARNING **: cannot open display:. Is this because I'm running on server only via command line? (no GUI/Desktop options).  I don't really care about display as long as it saves the output somewhere. A little noob question but any help would be appreciated!
When I run
CUDA_VISIBLE_DEVICES=0 python2 fc4.py test pretrained/colorchecker_fold1and2.ckpt -1 sample_inputs/37.jpg
this is the output
FutureWarning: Conversion of the second argument of issubdtype from `float` to `np.floating` is deprecated. In future, it will be treated as `np.float64 == np.dtype(float).type`.
 from ._conv import register_converters as _register_converters
2018-10-17 13:32:48.510892: I tensorflow/core/platform/cpu_feature_guard.cc:140] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2 FMA
2018-10-17 13:32:48.620582: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1356] Found device 0 with properties:
name: Tesla K40c major: 3 minor: 5 memoryClockRate(GHz): 0.745
pciBusID: 0000:05:00.0
totalMemory: 11.17GiB freeMemory: 9.74GiB
2018-10-17 13:32:48.620621: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1435] Adding visible gpu devices: 0
2018-10-17 13:32:48.883559: I tensorflow/core/common_runtime/gpu/gpu_device.cc:923] Device interconnect StreamExecutor with strength 1 edge matrix:
2018-10-17 13:32:48.883614: I tensorflow/core/common_runtime/gpu/gpu_device.cc:929]      0
2018-10-17 13:32:48.883621: I tensorflow/core/common_runtime/gpu/gpu_device.cc:942] 0:   N
2018-10-17 13:32:48.883903: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1053] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 9433 MB memory) -> physical GPU (device: 0, name: Tesla K40c, pci bus id: 0000:05:00.0, compute capability: 3.5)
FOLD 0
['g0', 'g1']
['g2']
fire3/squeeze1x1_weights (16, 128, 1, 1)
fire4/expand1x1_weights (128, 32, 1, 1)
conv1_bias (64,)
fire7/squeeze1x1_weights (48, 384, 1, 1)
fire7/expand1x1_weights (192, 48, 1, 1)
fire5/expand3x3_weights (128, 32, 3, 3)
fire5/squeeze1x1_bias (32,)
fire9/squeeze1x1_weights (64, 512, 1, 1)
fire4/expand3x3_weights (128, 32, 3, 3)
fire4/expand3x3_bias (128,)
fire8/squeeze1x1_bias (64,)
fire3/expand3x3_weights (64, 16, 3, 3)
fire8/expand3x3_weights (256, 64, 3, 3)
fire2/expand3x3_weights (64, 16, 3, 3)
fire3/squeeze1x1_bias (16,)
fire6/expand3x3_weights (192, 48, 3, 3)
fire7/expand3x3_weights (192, 48, 3, 3)
fire5/expand1x1_weights (128, 32, 1, 1)
fire2/squeeze1x1_weights (16, 64, 1, 1)
fire5/expand3x3_bias (128,)
conv10_weights (1000, 512, 1, 1)
fire8/squeeze1x1_weights (64, 384, 1, 1)
fire4/squeeze1x1_bias (32,)
fire9/squeeze1x1_bias (64,)
fire6/squeeze1x1_bias (48,)
fire3/expand1x1_weights (64, 16, 1, 1)
fire2/expand1x1_weights (64, 16, 1, 1)
fire8/expand1x1_weights (256, 64, 1, 1)
fire4/squeeze1x1_weights (32, 128, 1, 1)
fire6/squeeze1x1_weights (48, 256, 1, 1)
fire6/expand3x3_bias (192,)
fire2/squeeze1x1_bias (16,)
fire4/expand1x1_bias (128,)
fire5/squeeze1x1_weights (32, 256, 1, 1)
fire9/expand3x3_weights (256, 64, 3, 3)
fire3/expand3x3_bias (64,)
fire8/expand3x3_bias (256,)
fire2/expand1x1_bias (64,)
fire7/expand1x1_bias (192,)
fire9/expand1x1_bias (256,)
fire8/expand1x1_bias (256,)
conv1_weights (64, 3, 3, 3)
fire6/expand1x1_bias (192,)
fire7/squeeze1x1_bias (48,)
fire9/expand3x3_bias (256,)
fire5/expand1x1_bias (128,)
fire9/expand1x1_weights (256, 64, 1, 1)
fire6/expand1x1_weights (192, 48, 1, 1)
fire3/expand1x1_bias (64,)
conv10_bias (1000,)
fire2/expand3x3_bias (64,)
fire7/expand3x3_bias (192,)
/home/USER/fc4-master/squeeze_net.py:112: FutureWarning: elementwise comparison failed; returning scalar instead, but in the future will perform elementwise comparison
 if init == 'variance':
/home/USER/fc4-master/squeeze_net.py:118: FutureWarning: elementwise comparison failed; returning scalar instead, but in the future will perform elementwise comparison
 elif init == 'xavier':
conv1_w (3, 3, 3, 64)
fire2_s1_weight (1, 1, 64, 16)
fire2_e1 (1, 1, 16, 64)
fire2_e3 (3, 3, 16, 64)
fire3_s1_weight (1, 1, 128, 16)
fire3_e1 (1, 1, 16, 64)
fire3_e3 (3, 3, 16, 64)
fire4_s1_weight (1, 1, 128, 32)
fire4_e1 (1, 1, 32, 128)
fire4_e3 (3, 3, 32, 128)
fire5_s1_weight (1, 1, 256, 32)
fire5_e1 (1, 1, 32, 128)
fire5_e3 (3, 3, 32, 128)
fire6_s1_weight (1, 1, 256, 48)
fire6_e1 (1, 1, 48, 192)
fire6_e3 (3, 3, 48, 192)
fire7_s1_weight (1, 1, 384, 48)
fire7_e1 (1, 1, 48, 192)
fire7_e3 (3, 3, 48, 192)
fire8_s1_weight (1, 1, 384, 64)
fire8_e1 (1, 1, 64, 256)
fire8_e3 (3, 3, 64, 256)
fire9_s1_weight (1, 1, 512, 64)
fire9_e1 (1, 1, 64, 256)
fire9_e3 (3, 3, 64, 256)
(?, 32, 32, 512)
conv10 (1, 1, 512, 1000)
(?, 32, 32, 1000)
(?, 32, 32, 1000)
(?, 19, 19, 1000)
Feed to FC shape (?, 15, 15, 512)
FC1 shape (?, 15, 15, 64)
FC2 shape (?, 15, 15, 3)
FC2 shape (?, 15, 15, 3)
WARNING:tensorflow:From /home/USER/fc4-master/summary_utils.py:121: calling reduce_mean (from tensorflow.python.ops.math_ops) with keep_dims is deprecated and will be removed in a future version.
Instructions for updating:
keep_dims is deprecated, use keepdims instead
WARNING:tensorflow:From /home/USER/fc4-master/summary_utils.py:138: calling reduce_sum (from tensorflow.python.ops.math_ops) with keep_dims is deprecated and will be removed in a future version.
Instructions for updating:
keep_dims is deprecated, use keepdims instead
visualization shape (?, 1040, 1560, 3)
WARNING:tensorflow:From /home/USER/fc4-master/fcn.py:219: get_regularization_losses (from tensorflow.contrib.losses.python.losses.loss_ops) is deprecated and will be removed after 2016-12-30.
Instructions for updating:
Use tf.losses.get_regularization_losses instead.
list1 FCN/AlexNet/Wconv1_w:0
list1 FCN/AlexNet/bias_relu1_b:0
list1 FCN/AlexNet/Wfire2_s1_weight:0
list1 FCN/AlexNet/Wfire2_e1:0
list1 FCN/AlexNet/Wfire2_e3:0
list1 FCN/AlexNet/bias_fire2_fire_bias_s1:0
list1 FCN/AlexNet/bias_fire2_fire_bias_e1:0
list1 FCN/AlexNet/bias_fire2_fire_bias_e3:0
list1 FCN/AlexNet/Wfire3_s1_weight:0
list1 FCN/AlexNet/Wfire3_e1:0
list1 FCN/AlexNet/Wfire3_e3:0
list1 FCN/AlexNet/bias_fire3_fire_bias_s1:0
list1 FCN/AlexNet/bias_fire3_fire_bias_e1:0
list1 FCN/AlexNet/bias_fire3_fire_bias_e3:0
list1 FCN/AlexNet/Wfire4_s1_weight:0
list1 FCN/AlexNet/Wfire4_e1:0
list1 FCN/AlexNet/Wfire4_e3:0
list1 FCN/AlexNet/bias_fire4_fire_bias_s1:0
list1 FCN/AlexNet/bias_fire4_fire_bias_e1:0
list1 FCN/AlexNet/bias_fire4_fire_bias_e3:0
list1 FCN/AlexNet/Wfire5_s1_weight:0
list1 FCN/AlexNet/Wfire5_e1:0
list1 FCN/AlexNet/Wfire5_e3:0
list1 FCN/AlexNet/bias_fire5_fire_bias_s1:0
list1 FCN/AlexNet/bias_fire5_fire_bias_e1:0
list1 FCN/AlexNet/bias_fire5_fire_bias_e3:0
list1 FCN/AlexNet/Wfire6_s1_weight:0
list1 FCN/AlexNet/Wfire6_e1:0
list1 FCN/AlexNet/Wfire6_e3:0
list1 FCN/AlexNet/bias_fire6_fire_bias_s1:0
list1 FCN/AlexNet/bias_fire6_fire_bias_e1:0
list1 FCN/AlexNet/bias_fire6_fire_bias_e3:0
list1 FCN/AlexNet/Wfire7_s1_weight:0
list1 FCN/AlexNet/Wfire7_e1:0
list1 FCN/AlexNet/Wfire7_e3:0
list1 FCN/AlexNet/bias_fire7_fire_bias_s1:0
list1 FCN/AlexNet/bias_fire7_fire_bias_e1:0
list1 FCN/AlexNet/bias_fire7_fire_bias_e3:0
list1 FCN/AlexNet/Wfire8_s1_weight:0
list1 FCN/AlexNet/Wfire8_e1:0
list1 FCN/AlexNet/Wfire8_e3:0
list1 FCN/AlexNet/bias_fire8_fire_bias_s1:0
list1 FCN/AlexNet/bias_fire8_fire_bias_e1:0
list1 FCN/AlexNet/bias_fire8_fire_bias_e3:0
list1 FCN/AlexNet/Wfire9_s1_weight:0
list1 FCN/AlexNet/Wfire9_e1:0
list1 FCN/AlexNet/Wfire9_e3:0
list1 FCN/AlexNet/bias_fire9_fire_bias_s1:0
list1 FCN/AlexNet/bias_fire9_fire_bias_e1:0
list1 FCN/AlexNet/bias_fire9_fire_bias_e3:0
list1 FCN/AlexNet/Wconv10:0
list1 FCN/AlexNet/bias_relu10_b:0
list2 FCN/fc1/weights:0
list2 FCN/fc1/biases:0
list2 FCN/fc2/weights:0
list2 FCN/fc2/biases:0
Model pretrained/colorchecker_fold1and2.ckpt restored.
fire3/squeeze1x1_weights (16, 128, 1, 1)
fire4/expand1x1_weights (128, 32, 1, 1)
conv1_bias (64,)
fire7/squeeze1x1_weights (48, 384, 1, 1)
fire7/expand1x1_weights (192, 48, 1, 1)
fire5/expand3x3_weights (128, 32, 3, 3)
fire5/squeeze1x1_bias (32,)
fire9/squeeze1x1_weights (64, 512, 1, 1)
fire4/expand3x3_weights (128, 32, 3, 3)
fire4/expand3x3_bias (128,)
fire8/squeeze1x1_bias (64,)
fire3/expand3x3_weights (64, 16, 3, 3)
fire8/expand3x3_weights (256, 64, 3, 3)
fire2/expand3x3_weights (64, 16, 3, 3)
fire3/squeeze1x1_bias (16,)
fire6/expand3x3_weights (192, 48, 3, 3)
fire7/expand3x3_weights (192, 48, 3, 3)
fire5/expand1x1_weights (128, 32, 1, 1)
fire2/squeeze1x1_weights (16, 64, 1, 1)
fire5/expand3x3_bias (128,)
conv10_weights (1000, 512, 1, 1)
fire8/squeeze1x1_weights (64, 384, 1, 1)
fire4/squeeze1x1_bias (32,)
fire9/squeeze1x1_bias (64,)
fire6/squeeze1x1_bias (48,)
fire3/expand1x1_weights (64, 16, 1, 1)
fire2/expand1x1_weights (64, 16, 1, 1)
fire8/expand1x1_weights (256, 64, 1, 1)
fire4/squeeze1x1_weights (32, 128, 1, 1)
fire6/squeeze1x1_weights (48, 256, 1, 1)
fire6/expand3x3_bias (192,)
fire2/squeeze1x1_bias (16,)
fire4/expand1x1_bias (128,)
fire5/squeeze1x1_weights (32, 256, 1, 1)
fire9/expand3x3_weights (256, 64, 3, 3)
fire3/expand3x3_bias (64,)
fire8/expand3x3_bias (256,)
fire2/expand1x1_bias (64,)
fire7/expand1x1_bias (192,)
fire9/expand1x1_bias (256,)
fire8/expand1x1_bias (256,)
conv1_weights (64, 3, 3, 3)
fire6/expand1x1_bias (192,)
fire7/squeeze1x1_bias (48,)
fire9/expand3x3_bias (256,)
fire5/expand1x1_bias (128,)
fire9/expand1x1_weights (256, 64, 1, 1)
fire6/expand1x1_weights (192, 48, 1, 1)
fire3/expand1x1_bias (64,)
conv10_bias (1000,)
fire2/expand3x3_bias (64,)
fire7/expand3x3_bias (192,)
conv1_w (3, 3, 3, 64)
fire2_s1_weight (1, 1, 64, 16)
fire2_e1 (1, 1, 16, 64)
fire2_e3 (3, 3, 16, 64)
fire3_s1_weight (1, 1, 128, 16)
fire3_e1 (1, 1, 16, 64)
fire3_e3 (3, 3, 16, 64)
fire4_s1_weight (1, 1, 128, 32)
fire4_e1 (1, 1, 32, 128)
fire4_e3 (3, 3, 32, 128)
fire5_s1_weight (1, 1, 256, 32)
fire5_e1 (1, 1, 32, 128)
fire5_e3 (3, 3, 32, 128)
fire6_s1_weight (1, 1, 256, 48)
fire6_e1 (1, 1, 48, 192)
fire6_e3 (3, 3, 48, 192)
fire7_s1_weight (1, 1, 384, 48)
fire7_e1 (1, 1, 48, 192)
fire7_e3 (3, 3, 48, 192)
fire8_s1_weight (1, 1, 384, 64)
fire8_e1 (1, 1, 64, 256)
fire8_e3 (3, 3, 64, 256)
fire9_s1_weight (1, 1, 512, 64)
fire9_e1 (1, 1, 64, 256)
fire9_e3 (3, 3, 64, 256)
(?, 189, 252, 512)
conv10 (1, 1, 512, 1000)
(?, 189, 252, 1000)
(?, 189, 252, 1000)
(?, 176, 239, 1000)
Feed to FC shape (?, 94, 125, 512)
FC1 shape (?, 94, 125, 64)
FC2 shape (?, 94, 125, 3)
FC2 shape (?, 94, 125, 3)
visualization shape (?, 616, 1224, 3)
62.94697 1260.4567 333.5397

(Ret:20889): Gtk-WARNING **: cannot open display:
`

Note: The same error occurs even when I do
CUDA_VISIBLE_DEVICES=0 python2 fc4.py test pretrained/colorchecker_fold1and2.ckpt -1 sample_inputs/37.jpg sample_inputs/new.jpg
Thanks!

so I kinda got this working now by commenting out the cv2 im.show lines, but I don't understand where the processed images are. Could you please guide me??


VerifyError: Error #1053 in Flash Debug Player because Royale compiler allows incompatible function signatures

flashplayer_32_sa_debug.exe throws this error:
VerifyError: Error #1053: Illegal override of A in a.A.
With this:
public interface B
{
	function foo(c:Object):void;
}

public class A implements B
{
	public function foo(c:String):void {}
}

Royale mxmlc happily compiles this.  Flex mxmlc will give this compile error:
Error: Interface method foo in namespace a:B is implemented with an incompatible signature in class a:A.
Why is this important?
If you have:
import org.apache.royale.events.Event;

class ... implements IEventDispatcher
{
...
	public function dispatchEvent( event : Event ) : Boolean { ... }
}

Royale mxmlc compiles it just fine.  And it runs fine in JS.  But in Flash Debugger, it throws VerifyError: Error #1053.
The correct definition is:
COMPILE::SWF
{
    import flash.events.Event;
}

class ... implements IEventDispatcher
{
...
	COMPILE::SWF
	public function dispatchEvent( event : flash.events.Event ) : Boolean { ... }

	COMPILE::JS
	public function dispatchEvent( event : Object ) : Boolean { ... }
}

And this kind of problem is hard to track down.

I can reproduce the VerifyError. That's not good.
Using the -allow-subclass-overrides=false compiler option when compiling your app may help here.
Unfortunately, making -allow-subclass-overrides=true the default seems to have been intentional, and the Royale framework now takes advantage of it widely. It may be very difficult or impossible to fully unravel at this point.


Element from panel gets covered by main view

Hi, I'm trying to accomplish a view which only contains a listview and my sliding up menu. The sliding up menu has a seek bar on top (as a fragment) which actually overlays the menu. The idea is that the seek bar will be exactly in the middle between the menu and the listview but the problem I'm finding is that the listview (or whichever element is on top for that matters) covers the overlaying half of the seek bar. Is there anyway to avoid that? I've been fiddling with the menu properties and different layouts configurations all day and have been unable to fullfill this.

Have a look at the clipChildren attribuet of the layout. See if that works for you. http://developer.android.com/reference/android/view/ViewGroup.html#attr_android:clipChildren


Fix DAP issues for Button

Level
Description

V
All content must reside within a WAI-ARIA landmark or labelled region role.

false positive, since the preview page doesn't have a main tag. Unfortunately there's no reasonable way for us to add one at the moment. Apps should of course render into a main or other valid region.


[2.7] Improve security-scan's e2e validation with yamllint and kube-bench dry-run

backport rancher/cis-operator#227

Validated on rancher v2.7-head. Provisioned RKE1, RKE2 and K3s clusters using below k8s versions:

v1.23
v1.24
v1.25
v1.26

Ran the scans using respective profiles on all the clusters, all scan passed except below failures which are expected and will be release noted:
RKE1 hardened:
Mixed
4.1.7	Ensure that the certificate authorities file permissions are set to 600 or more restrictive (Automated)

RKE2 node driver:
Fail
1.1.1	Ensure that the API server pod specification file permissions are set to 600 or more restrictive (Automated)
Fail
1.1.3	Ensure that the controller manager pod specification file permissions are set to 600 or more restrictive (Automated)
Fail
1.1.5	Ensure that the scheduler pod specification file permissions are set to 600 or more restrictive (Automated)
Fail
1.1.7	Ensure that the etcd pod specification file permissions are set to 600 or more restrictive (Automated)


CIP assets: images missing if in folder itself or for CPSs

The current title states my best guess at the reason for the reason staging currently does not build: due to the recent merge of CPS-0010 (https://github.com/cardano-foundation/CIPs/pull/619) and judging by the CIP build script output because of the image pathnames in that GitHub source (https://github.com/cardano-foundation/CIPs/blob/master/CPS-0010/README.md):
Error: Image docs/governance/cardano-problem-statements/no-data-wallet.drawio.png used in docs/governance/cardano-problem-statements/CPS-0010.md not found.
    at async Promise.all (index 0)
[ERROR] Client bundle compiled with errors therefore further build is impossible.

The CPS-0010 source uses the same relative-pathname syntax as successfully used for the images in CIP-0050... so my guess (not looking at the scripts yet; needed to prioritise reporting this problem while still on a bad Internet connection) is that either:

the prepended /images folder for CIP-0050 allows the script to recognise that there are assets to collect... but doesn't work for images in the CIP folder itself; or:
whatever rule is used to collect those images is only being run for CIP- documents but not for CPS- documents.

This is a hasty report, with some guesswork, since I'm still travelling almost daily & just wanted to blow the whistle on this, since it's affecting the CI build checking for all PRs open on the Dev Portal.  cc @katomm @fill-the-fill @ryun1

Sorry, didn't see this before, I will take it on me


Extract ResolutionStrategy Factory

Create a standalone ResolutionStrategyFactory. This logic should be separate from a ConfigurationContainer.
The primary motivation for this was to avoid calling 'startParameterResolutionOverride.applyToCachePolicy(cachePolicy)' during resolution, as this mutates the resolution strategy. Ideally, we should not be mutating the resolution strategy after resolution has been initiated.
Making this change centralizes the logic required to build a resolution strategy. But more importantly, by avoiding mutating the resolution strategy after resolution has been initiated, we can leverage this change to be more strict about when we lock configurations for mutation.
The actual changes to mutation will happen in a future PR. This was simply an easily-extractable change which will simplify reasoning about the future configuration mutation changes.

@bot-gradle test this

I've triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test and merge

I've triggered a build for you. Click here to see all failures if there's any.


tmle3optmttx exercise problem -- simplified rule

Hi,
I am attempting to work through the exercise at the end of this chapter. While I can get a TMLE value of the optimal ITR, and also for the realistic optimal ITR, when I attempt to get the simplified rule xgboost appears to be throwing errors.
#a simpler rule
tmle_spec2 <- tmle3_mopttx_blip_revere(
V = c("momedu", "floor", "asset_refrig"), type = "blip2",
learners = learner_list,
maximize = TRUE, complex = FALSE, realistic = FALSE
)
fit <- tmle3(tmle_spec2, data = washb_data, node_list, learner_list)
Error in xgboost::xgb.DMatrix(Xmat) :
xgb.DMatrix does not support construction from double
Error in if (nrow(Xmat) > 0) { : argument is of length zero
Failed on predict
Error in self$compute_step() :
Error in if (nrow(Xmat) > 0) { : argument is of length zero
I can provide all of my code if that is helpful.

Hi,
this seems to be a xgboost error; if your library has other learners, you should still get a fit object.

Yes that's true (didn't realize a fit object was still returned). Thanks, can be closed.

No problem, thanks for pointing out!


x/tools/gopls:

gopls version
golang.org/x/tools/gopls v0.9.3
<EMAIL_ADDRESS>h1:wfh4cfJAKwOG49sCE4ldafYeD5rlejE/gJQ7JAR5yX0=
go env

What did you do?
I tries to invoke a go language specific function is vscode such as "Go To Definition" for a function.77
Ever since version 0.9.2 was released (and 0.9.3 as well).  I am not able to use any go language specific functions in vscode.  If I try to "Go To Definition" in a go file, I see the following error in the Developer tools Window:
What did you expect to see?
I expected VSCODE to position itself on source code for the function.
What did you see instead?
VSCODE displays an endless progress bar and display the following error message in developer tools window:
workbench.desktop.main.js:2279 Error: Header must provide a Content-Length property.
at StreamMessageReader.onData
Editor and settings
I have seen this behaviour it the two latest version 0.9.2 and 0.9.3 when I go back to version 0.9.1 everything returns to normal function.
Logs

Thank you for the issue.
This is golang/vscode-go#2406: a new vet analyzer contains a print statement that breaks jsonrpc2 communication in gopls.
It will be fixed on Monday. We only discovered this midday on Friday, and do not release over the weekend.
Sorry for the breakage.

"Sorry for the breakage"
Thanks for everything that does work - It's great.

:heart: thanks.
BTW, if you hit this bug, your project contains a time format string containing "2006-02-01" instead of "2006-01-02", which is probably incorrect (c.f. #48801)


libuv thread communication

I have a c++ lib, client application use this lib to query data from server. This lib create a seperate thread to communicate with server, query result will be passed as parameters in callback function.
Now i want to wrap this c++ lib to nodejs native module, since callback functions are called in this lib's own thread, in order to pass query result to js environment, i believe i have to use libuv's uv_async_send(uv_async_t* async) method to pass data between two thread.(correct me if I'm wrong)
According to libuv's doc:
Warning: libuv will coalesce calls to uv_async_send(), that is, not every call to it will yield an execution of the callback. For example: if uv_async_send() is called 5 times in a row before the callback is called, the callback will only be called once. If uv_async_send() is called again after the callback was called, it will be called again.
Does this warning means uv_async_send may cause data lost? I want to know whether the libuv offer a better solution for this problem or should I use some other thead librarys.

Does this warning means uv_async_send may cause data lost? I want to know whether the libuv offer a better solution for this problem or should I use some other thead librarys.

No. It means that for every uv_async_send invokation the is no guarantee that a callback call will follow, thus you cannot rely on storing stuff on a data pointer and process it in the callback.
You'll need to store the data in a thread-safe queue structure, the use `uv_async_send to wakeup the event loop and process the data in the queue on the async callback.
PS: I'm coling this since it's not a bug, please use our mailing list for questions / discussions, thanks!


Does it support RTX 40 series? If no is there any hope for update?

I'm looking to buy a GPU. and I like to experiment with LLMs. Should I go for RTX 40 series?

I‘m using RTX 4090


phoebemirman/ch12115/should-say-zero-or-for-blank-fields

Clubhouse Story
Submitter checklist

[ ] Test covering functionality added/fixed in
Check the linked story includes the following:

[ ] Steps to reproduce
[ ] Screenshot (If applicable)

Reviewer Checklist

[ ] Test/lint pass

large gap left from removing columns, It's going to get really sparse when outcome is removed. approving and merging.


Compatibility with PHP 7.x

It took more than an year since #39 by @Danack but I finally had the time to sit down and work on polishing his initial contribution and put an end to the wait: phpiredis can be built and used on PHP 7.0, you can find the code on the php7 branch. The test suite is green on all the supported PHP versions and even the test suite of Predis (which has some connection backends that use the reader resource exposed by phpiredis) looks good. I'd like to test this branch a bit more before merging it into master and I'd also like to have some feedback from others so please try the new code and comment on this issue if you find any bug or memory leak using the extension on both PHP 5.x and 7.0.
PS: please note that for now phpiredis depends on hiredis up to v0.13 and it doesn't build with hiredis v1.0.0 which is still unreleased and a work-in-progress.
Thanks for the wait!

By the way, the library can be built even on PHP 7.1.0alpha1 and tests are green.

I'll plug this into our Docker setup and see how it handles itself. Nice work!!

Thanks @ellisio, looking forward to your feedback! Which version of PHP are you using?

We are using 7.0.7. I used it all day yesterday and it seems to work just fine. I plan to run some load testing here in a few days; just have some other stuff I have to get wrapped up before I do that.

@nrk sorry - I don't have time to look at this, but one thing you need to check is something I wasn't aware of when I did the PR.
Basically when you have any Z_TYPE_P, and the zval comes from a user, there ought to be a ZVAL_DEREF before the Z_TYPE_P to make it work properly, rather than falling over.
I think for you that might be just these two places:
https://github.com/nrk/phpiredis/blob/php7/phpiredis.c#L716
https://github.com/nrk/phpiredis/blob/php7/phpiredis.c#L744
need this:
#ifdef ZEND_ENGINE_3
  	ZVAL_DEREF(param);
#endif

As I said, I only found this out recently - the Imagick test that makes sure this works is there.

thank you so much nrk.    nice work . i want donate to u for you work . 👍

@Danack fixed, thanks! Maybe it's just that I'm still a noob when it comes to PHP extensions, but the ZE API seems mostly an undocumented mass of macros, sometimes with only slight differences, that makes it hard for novices to start especially without digging into the ZE source.

the ZE API seems mostly an undocumented mass of macros, sometimes with only slight differences, that makes it hard for novices to start especially without digging into the ZE source.

It is not just you.
As I said, I missed that in my initial port of Imagick......and only found out about it when people complained about stuff breaking.....

After testing this branch for a good week I'm quite confident it's stable enough to get merged into master but since I'm busy for the next few days I'm going to wait a bit more just in case anyone has more feedback. After the merge I guess we can finally have v1.0.0 tagged.

any update nrk?

@erikwestlund the last update is my comment above yours from 6 hours ago as the time of writing.

@nrk, I'm sorry, for some reason I read "7 hours ago" as "7 days ago" .... whoops :)
looking forward to it.  Thank you!

@erikwestlund haha it's fine don't worry :)

Been a little over a week, any chance of this being merged into master? I've been running it for almost a month now in development and production with zero hiccups.

@ellisio I'm planning to merge everything into master this weekend. thanks!

Merge to master would be great

Whoa, whoa, whoa. You can't just rush into these things.

Finally merged the php7 branch into the master! Next week I'll be off on vacation, will tag v1.0.0 at the end of the month :-)

got
error LNK2001: unresolved external symbol _executor_globals
build with --disable-zts flag.


Fix FloatingPoint nextUp/Down on armv7.

Rigorously implement flush-to-zero behavior.
This fixes several recent unit test failures on armv7 hardware.

@swift-ci Please smoke test and merge

@swift-ci Please smoke test and merge


[EXPLOIT FIX!!!] Manufacture creamed cheese.

added a service event for toggling the console did not manufacture creamed cheese or fix exploit sorry
clickbait sorry

I feel very clickbaited.


Import Data from Googlecode

Start the Import Google Code Data into this new GitHub Repository.

project without file history imported


Assign group roles

Suggestion:
Alice Frontend Design
Suhir Frontend Handlebars master
Daron Backend
Kristina SCRUMlord/backend

Suggestion:
Alice Frontend Design
Suhir Frontend Handlebars master
Daron Backend
Kristina SCRUMlord/backend

Daron - back-end and GitHub/Heroku
Alice - front end
Suhir - front end
Kristina - back end

Daron - back-end and GitHub/Heroku
Alice - front end
Suhir - front end
Kristina - back end


checks with const actual no longer compile

unittest
{
    const actual = 42;
    actual.should.equal(42);
}

results in:
core/fluentasserts/core/base.d(449,5): Error: cannot modify const expression r.__expand_field_0
core/fluentasserts/core/base.d(513,39): Error: template instance fluentasserts.core.base.evaluate!(const(int)) error instantiating
instantiated from here: should!(const(int))

(for better reference, I created an issue from my earlier comment)

thanks! i'll look into it.


Using react-router's  component causes double history entries

history.push(location) is called two multiple times with the same values:

first time when the <Link> is clicked

second time when route store listener is called:
  var unsubscribeStore = store.subscribe(function () {
       var routing = getRouterState();
       // Only trigger history update if this is a new change or the
       // location has changed.
       if (lastRoute.changeId !== routing.changeId || !locationsAreEqual(lastRoute, routing)) {

           lastRoute = routing;
           var method = routing.replace ? 'replaceState' : 'pushState';
           history[method](routing.state, routing.path);
       }
   }

This always calls history.pushState for second time because history/router and browser window already have the new location but lastRoute still contain old path. This effectively causes two equal history entries so the browser back button works on the second click only.
The current history location and window.location should be checked before history.push to prevent duplicate history entries.

I have this same issue.

@kromit Have you tried it with the new version https://github.com/rackt/redux-simple-router/blob/master/src/index.js#L99
It shouldn't have the same problem since it uses the key created by RR.

2.0.1 fixed it


Print via API

There has been a request that we should allow users to make prints automatically without human intervention for use with external automation.
One of my ideas was to make it possible for users to create API tokens which allows them to send a POST request to an API endpoint with their document.
We could start developing an API for mars but I think using a full-stack framework with allowing API requests would be a bit cumbersome (developing endpoints for both API requests and both for human users would be a bit tedious).

If they don't want to use our user interface you should allow them to somehow connect to the printer directly. It has all the api and configuration options one might need, there's no point in developing and maintaining this in Mars just to act as a middle man.
Or I don't understand the needs.

If you want, It's fine to handle the tokens with Mars but I would not implement the communication through this system.

If they don't want to use our user interface you should allow them to somehow connect to the printer directly. It has all the api and configuration options one might need, there's no point in developing and maintaining this in Mars just to act as a middle man.

One can only access the printer physically or the network traffic needs to go through our protected management network. (Or anybody would be able to communicate directly with the printer, which could be dangerous if someone on the internet plants malicious firmware on it.) Due to recent regulatory changes, we are unable to give access to the protected management network to non system administrators.
Mars has a way of keeping track of printing credits and giving out direct access to the printer would circumvent it.

If you want, It's fine to handle the tokens with Mars but I would not implement the communication through this system.

Would you recommend us creating a different project which can be used with APIs?

After careful consideration, we have decided not to build a proper API but rather work on such issues on a per-user basis.


HiveDialect doesn't support create table with PARTITIONED BY and CLUSTERED BY clause

When I used the Hive dialect to parse the following Hive SQL, I encountered the following error.
    CREATE TABLE user_info_bucketed(user_id BIGINT, firstname STRING, lastname STRING)
    COMMENT 'A bucketed copy of user_info'
    PARTITIONED BY(ds STRING)
    CLUSTERED BY(user_id) INTO 256 BUCKETS;

with error
Err(ParserError("Expected: end of statement, found: PARTITIONED at Line: 4, Column: 5"))

Here is the code I tested.
use sqlparser::dialect::HiveDialect;
use sqlparser::parser::Parser;

fn main() {
    let query = r#"
    CREATE TABLE user_info_bucketed(user_id BIGINT, firstname STRING, lastname STRING)
    COMMENT 'A bucketed copy of user_info'
    PARTITIONED BY(ds STRING)
    CLUSTERED BY(user_id) INTO 256 BUCKETS;"#;
    let dialect = HiveDialect {};
    let ast = Parser::parse_sql(&dialect, query);
    println!("ast={:?}", ast);
}

@wugeer Yes, it hasn't supported parsing COMMENT after the table column definition yet, nor has the CLUSTERED BY clause. I can support both of them if you want this feature.

@wugeer  Yes, it hasn't supported parsing COMMENT after the table column definition yet, nor has the CLUSTERED BY clause. I can support both of them if you want this feature.

@wugeer Yes, it hasn't supported parsing COMMENT after the table column definition yet, nor has the CLUSTERED BY clause. I can support both of them if you want this feature.

@git-hulk That sounds awesome! Thank you for help! :)

@wugeer Your SQL should be valid after removing the table comment line. For parsing the hive comment, I need to add an extra field hive_comment since it follows after the column definitions and other dialects are not, and it cannot know the dialect information while generating SQL by AST. What do you think about this? @alamb @iffyio

@git-hulk Thank you for your continued attention and contribution to this issue.

@git-hulk we can probably have as part of the CommentDef enum? e.g. if we add a new variant like CommentDef::AfterColumnDefsWithoutEq(String) would provide the required info in the display impl of CreateTable to know where to place the comment.

@git-hulk we can probably have as part of the CommentDef enum? e.g. if we add a new variant like CommentDef::AfterColumnDefsWithoutEq(String) would provide the required info in the display impl of CreateTable to know where to place the comment.

Good advice. I have to say whenever I need better advice, it's always right to call @iffyio. ❤


Updated changes to abstract shared types into a separate header

Copied from a response to a closed PR #26

Thanks for the feedback on the PR @jona-wilmsmann . Sorry, I had forgotten about the the abi generation on the tables once I removed them from the main contract. However I have now added the annotations to ensure they work as expected for the atomicassets contract and will not generate abi entries for the other contracts using the public header.
The intention was not only to create an interface for others but also to ensure there was only one definition of the structs to maintain and therefore prevent them drifting out of sync. With the current changes, for example, there is now templates_s in one header and presets_s in the other which would be an easy mistake to make - also with some different field names such as template_id vs preset_id.
In regards to deleting the custom dispatcher this wasn't quite accidental. Although during my final merge conflict resolution before opening the PR I accidentally removed the [[eosio::on_notify("*::transfer")]] annotation which would ensured the transfer notifications would work as you expected .Sorry about that 🤦 .
With the combination of ACTION annotations and the eosio::on_notify annotation, through my experience, you should not need the custom dispatcher anymore. Also, I think if you do have the custom dispatcher in the code it will use the custom one over the auto generated one but not a combination of both.
I'll open a new PR with the updated changes and see what you think.

You're making a good point regarding the problems of having a redundant interface header, and a pretty good example too ^^ (There actually were a bunch of other things wrong with that header that I fixed now at least for the time being. I copied that over from another (slightly outdated) project where I didn't yet change from preset to template and from scheme to schema.
I wasn't aware of the syntax you're using to make sure that the tables are being generated in the ABI of atomicassets but not for other contracts, that's very cool.
The problem I still see with splitting the file in two is that, I can't think of a good way to have definitions like
collections_t collections = collections_t(ATOMICASSETS_ACCOUNT, ATOMICASSETS_ACCOUNT.value);
offers_t offers = offers_t(ATOMICASSETS_ACCOUNT, ATOMICASSETS_ACCOUNT.value);
balances_t balances = balances_t(ATOMICASSETS_ACCOUNT, ATOMICASSETS_ACCOUNT.value);
config_t config = config_t(ATOMICASSETS_ACCOUNT, ATOMICASSETS_ACCOUNT.value);
tokenconfigs_t tokenconfigs = tokenconfigs_t(ATOMICASSETS_ACCOUNT, ATOMICASSETS_ACCOUNT.value);

or the helper functions like
assets_t get_assets(name acc) {
    return assets_t(ATOMICASSETS_ACCOUNT, acc.value);
}

directly inside the public header.
You could of course just define ATOMICASSETS_ACCOUNT in the public header and then use that in place of get_self, but this means that when using the atomicassets contract, the compiled wasm only works for that one account name that is defined. Do you have any thoughts on that?
Also, why did you not include the config / tokenconfigs singleton in the public header. Is that because singletons are problematic to have in the public header?
Deleting the custom dispatcher in favor of [[eosio::on_notify("*::transfer")]] is a good idea and makes a lot of sense, if you put in a single pull request for that I will merge it.

When I commented about the templates_s vs presets_s I actually thought it was my mix-up but it shows how easy it can happen.
With regards to collections, offers etc. definitions I would think they belong in the non-public header  since those particular instances would be used only by atomicassets contract and are defined as instance variables on the running contract instance itself. Having the "atomicassets" Table annotations in the public header only help with the abi generation. Therefore the compile wasm and abi will be portable to different accounts without needing to re-compile. IMHO the value of the public headers is the structs definition and the typedefs for the associated multi-index types. The consumer would always need to create their own instances by providing the contract name and scope but this will be (or should be) familiar to anyone accessing other contract's data tables.
Actually, checking the code again I have usually created such instances of tables as part of the contract constructor, which you do not have in your code. With that you could also instantiate your singletons and save the singletons in the destructor of the contract. I can make those changes in another PR if you'd like. This would also mean you do not need the init action at all.
In regards to not adding the singletons to the public header this was because I thought they were mainly used internally within the atomicassets contract and therefore need not be shared so publicly.
Also the get_assets convenience function is really only saving the consumer one line of code so probably isn't worth the trouble to make it public when you need to consider the setting the right contract_name value for it to work everywhere.


Only allocate the result space in wrapped_pad_func

Previously wrapped_pad_func was copying the input array into result and then overwriting it. However the copy shouldn't be needed as it isn't used. Thus this uses np.empty to create the NumPy array with correct shape and type instead leaving filling it to the for-loop below.

[x] Tests added / passed
[x] Passes flake8 dask

Merging as this is a trivial change that passes tests. If there are concerns, happy to discuss.


esri leaflet samples need leaflet version bumped

the 'latest' cdn flag in our CDN script tag is now causing an incompatible version of esri-leaflet to be loaded in our samples.  time to upgrade to leaflet-1.0.0beta.1
<!-- Load Leaflet from CDN-->
<link rel="stylesheet" href="http://cdn.leafletjs.com/leaflet-1.0.0-b1/leaflet.css" />
<script src="http://cdn.leafletjs.com/leaflet-1.0.0-b1/leaflet.js"></script>

downgrading esri-leaflet to 1.0.0 works too b265ef542c6f1734a84badb6a0b04d86d038987d
(and is more appropriate until update the doc on the esri leaflet website)


nix-doc: 0.5.8 -> 0.5.9

Description of changes
Fixes compatibility with Nix 2.17 and dev process wise, improves our assurance that we are still compatible with older Nix by having (in-tree-only) automated tests for older Nix versions.
Thanks for the notification @zowoq in https://github.com/NixOS/nixpkgs/pull/247475
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Thanks!


Debugging a library source code is not working

Hi,
Problem :
I have a Java maven project with for example an apache commons-io  dependency. When I put a breakpoint on one of the line in the library source codes then debugger won't stop there.
code sample
public static void main(String[] args) {
        System.out.println("Hello World!");
        IOUtils.toString("hi".getBytes());
    }

I have a breakpoint inside toString method inside IOUtils

I can confirm that the debugger does not stop when putting a breakpoint into IOUtils.toString. Thanks for the report.


If the inputs don't make sense, don't panic

If inputs are received with only SELLs, but no BUYS, we currently panic.
Instead detect this and use a cost basis of zero for those sells.
    "__main__", mod_spec)
  File "/usr/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/home/rk/code/yabc/src/yabc/__main__.py", line 42, in <module>
    main()
  File "/home/rk/code/yabc/src/yabc/__main__.py", line 36, in main
    reports = processor.process()
  File "/home/rk/code/yabc/src/yabc/basis.py", line 293, in process
    reports, pool = _process_all(self.method, self.txs)
  File "/home/rk/code/yabc/src/yabc/basis.py", line 257, in _process_all
    ops = process_one(tx, pool)
  File "/home/rk/code/yabc/src/yabc/basis.py", line 128, in process_one
    amount += pool[pool_index].quantity
IndexError: list index out of range

Fixed! Flags get raised.

And the cost basis is zero for affected transactions


virtio-mem Windows guest support

MmAddPhysicalMemory has just been documented
In follow-up of https://ourwindowsman.wordpress.com/2020/11/03/virtio-mem-goes-to-windows/, the virtio-mem Windows guest support can continue.

@ohault Thanks!

Hello @YanVugenfirer, may I ask if it's related to the feature I've asked about https://github.com/virtio-win/kvm-guest-drivers-windows/discussions/989 ?
Thank you in advance.

@Directox01 It is an alternative method for memory over commit in the guest, when the memory is added\removed by the hypervisor and the driver.

virtio-mem implementation was added to the tree.

@YanVugenfirer , thank you. Would it be possible to have a public release soon on https://github.com/virtio-win/kvm-guest-drivers-windows/releases or somewhere else ?

There was a discussion: https://github.com/virtio-win/kvm-guest-drivers-windows/pull/794#issuecomment-2074467063

@ohault I think the latest build should contain it.

Yes, viomem is a part of virtio-win ios and rpm
https://github.com/virtio-win/virtio-win-pkg-scripts/commit/1431fa0624d7f16077030a1d42c81023bc29c185
and also included in installer https://github.com/virtio-win/virtio-win-guest-tools-installer/commit/daf2701f3430c9285743cc1124b6af21afd8c94e
Just be advice that if I'm not mistaken, the driver itself is still release as a preview.
Vadim.


⚠ Bofrost.lu has degraded performance

In 538356b, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1101 ms

Resolved: Bofrost.lu performance has improved in 0885100 after 13 minutes.


Fix dataProviderName in useForm hook

When using the useForm hook with a non-default data provider (i.e., setting the dataProviderName param) on an edit-page, it still tries to load the data via the default data provider.
This PR fixes this problem by passing the dataProviderName param down to the internally used useOne hook.
Test plan (required)
See related issue to see how to reproduce the bug.
Closing issues
Closes https://github.com/pankod/refine/issues/1631

Hey @Bastian ,
Looks so cool! Thank you!


Update Docker images to use community images

The node images are built on Jessie which no longer supports ppc64le or s390x, so upgrading to node-stretch fixes issues while doing apt-get we were having.


Add Code of Conduct

Ola...i will take this one as well :)

@ows-ali how is the mailadresse for the code of conduct?

Yes @codingCookie I have provided further details on your PR #71


Rearranging HomePage

"As a user, I want to view the multiple features on the Home Page in different tabs. "
[SP: 7 ]
[Value: high ]
[Risk: low ]
Tasks breakdown:

[x]  Define the implementation breakdown [0.5 hours]

[ ] Implement the feature [12 hours]

Implementation Breakdown:

[x] Create category fragment #154

[x] Create the different tabs on the home page #155

[x] Implement instrumented tests #156

[ ] Implement unit tests #156

Testing:
todo
Demonstration Steps:
todo

Demoed. Tabs are there. Still to be done move the random button and search results will be moved to a new page.
UI tests so far are done, unit still to be done.

@guipadua This User Story is now fully implemented. It is eligible for TA signoff.


Unable to Install GraphLab on Python 3.5

I executed he following command with my specified email and token but I got an error:
pip install --upgrade --no-cache-dir https://get.graphlab.com/GraphLab-Create/2.1/Email/Token/GraphLab-Create-License.tar.gz
ERROR:

Could not find a version that satisfies the requirement graphlab-create>=2.1 (from GraphLab-Create-License==2.1) (from versions: )
No matching distribution found for graphlab-create>=2.1 (from GraphLab-Create-License==2.1)

This link says that 3.5 is supported.
Although, In have tried changing the versions as well.
I have also manually downloaded the compressed file and used the following command to install:
python setup.py install
But none of it is working.

Have you tried pip install https://static.dato.com/files/beta/GraphLab_Create-1.9-py3.4.tar.gz like it describes in the link you provided.  I don't think the typical  pip install --upgrade --no-cache-dir https://get.graphlab.com/GraphLab-Create/2.1/Email/Token/GraphLab-Create-License.tar.gz will work in this instance.

Hi @washcycle , the link you provided is not accessible, is there any other workaround?

I would give up on graphlab thanks to Apple buying Dato or download the source and compile it. See the other issue #373 which might help. One guy there got it to work on 3.4 by compiling it.

@washcycle Thanks for the info.

@washcycle I tried as per your first comment, but hard luck I'm getting following output
(gl-env) mrt@mymachine:~$ pip install --upgrade https://get.graphlab.com/GraphLab-Create/2.1/my-email-id/my-prod.key/GraphLab-Create-License.tar.gz
Collecting https://get.graphlab.com/GraphLab-Create/2.1/my-email-id/my-prod.key/GraphLab-Create-License.tar.gz
  Downloading https://get.graphlab.com/GraphLab-Create/2.1/my-email-id/my-prod.key/GraphLab-Create-License.tar.gz
Collecting graphlab-create>=2.1 (from GraphLab-Create-License==2.1)
  Could not find a version that satisfies the requirement graphlab-create>=2.1 (from GraphLab-Create-License==2.1) (from versions: )
No matching distribution found for graphlab-create>=2.1 (from GraphLab-Create-License==2.1)

Any ideas?
I'm currently using Python 3.6 and I need it work with it.
as mentioned on Turi
it shows 2.7 version to setup the environment. whereas on continuum which is (default download link given by turi as well) compatible to 3.6 but still throws the error.

I have a similar issue with this output :
(venv) ubuntu@ip-hey-hey-hey:~/Eclipse-Stats$ pip install graphlab.toolkits.recommender
Collecting graphlab.toolkits.recommender
  Could not find a version that satisfies the requirement graphlab.toolkits.recommender (from versions: )
No matching distribution found for graphlab.toolkits.recommender

According to Turi's Graphlab tutorial  we only need to have : Python 2.7.x environment and pip version >= 7 and Anaconda2 v4.0.0 (64-bit). IPython Notebook is recommended.
And I got :
(venv) ubuntu@ip-172-31-41-89:~/Eclipse-Stats$ python -V
Python 2.7.12
(venv) ubuntu@ip-172-31-41-89:~/Eclipse-Stats$ pip -V
pip 9.0.1 from /home/ubuntu/venv/local/lib/python2.7/site-packages (python 2.7)

I don't know for Anaconda but as far as I dowloaded following the tutorial, I don't know where the issue is.

I ran I ran pip install --upgrade graphlab-create and it saved this issue.

Hi guys,
I'm trying to install Graphlab on my MBP using the graphical and I keep getting this error :
UnsatisfiableError: The following specifications were found to be in conflict:

conda 4.0.8* -> conda-env <2.5 -> python 2.7* -> openssl 1.0.1*
python 3.6*
Use "conda info " to see the dependencies for each package.

should I update my anaconda? or should I abandon everything and use the graphical?

InvalidLicense: License check failed: Unable to communicate with service. Verify Internet connection and try again or visit https://turi.com/support for support options.
Please help

The readme for this repository says:
THIS REPOSITORY IS DEPRECATED.

THE FUNCTIONALITY HAS MOVED TO Turi Create.

See the Turi Create Repository. Turi Create support Python 3. Turi Create also does not require a license.

Hi, Have you run that command after switching to the new environment you created with conda? I was getting the same error, but I found out that it was there because I wasn't running it within the environment I created for it in Conda

pip install --upgrade --no-cache-dir<EMAIL_ADDRESS>Collecting<EMAIL_ADDRESS>Downloading https://get.graphlab.com/GraphLab-Create/2.1/MYEMAIL/MYLICENSE/GraphLab-Create-License.tar.gz
Collecting graphlab-create>=2.1 (from GraphLab-Create-License==2.1)
Could not find a version that satisfies the requirement graphlab-create>=2.1 (from GraphLab-Create-License==2.1) (from versions: )
No matching distribution found for graphlab-create>=2.1 (from GraphLab-Create-License==2.1)

Apple bought Turi and re-released here.
https://github.com/apple/turicreate, not sure if the new release works with
the Coursera stuff though.
Regards,
Matthew Landowski
On Fri, Dec 14, 2018 at 11:21 AM zoongit<EMAIL_ADDRESS>wrote:

pip install --upgrade --no-cache-dir
<EMAIL_ADDRESS>Collecting
<EMAIL_ADDRESS>Downloading
https://get.graphlab.com/GraphLab-Create/2.1/MYEMAIL/MYLICENSE/GraphLab-Create-License.tar.gz
Collecting graphlab-create>=2.1 (from GraphLab-Create-License==2.1)
Could not find a version that satisfies the requirement
graphlab-create>=2.1 (from GraphLab-Create-License==2.1) (from versions: )
No matching distribution found for graphlab-create>=2.1 (from
GraphLab-Create-License==2.1)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/turi-code/SFrame/issues/382#issuecomment-447392791,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABBp_g2GEjRGT9G_o8Pihv5M17lqMALeks5u494rgaJpZM4LaUwt
.

As mentioned clearly in their documenation "Graphlab installation requires a Python 2.7.x environment and pip version >= 7 and Anaconda2 v4.0.0 (64-bit). IPython Notebook is recommended.". So try to use python 2.7.x to install and try to do it in a virtual environment to avoid other conflicts and it should work fine.

Graph lab create must be installed in a Python 2.7.x  (best create a virtual env using python 2.7.x)  then the usual installation procedure in Turi create  will work.

@washcycle I tried as per your first comment, but hard luck I'm getting following output
(gl-env) mrt@mymachine:~$ pip install --upgrade https://get.graphlab.com/GraphLab-Create/2.1/my-email-id/my-prod.key/GraphLab-Create-License.tar.gz
Collecting https://get.graphlab.com/GraphLab-Create/2.1/my-email-id/my-prod.key/GraphLab-Create-License.tar.gz
  Downloading https://get.graphlab.com/GraphLab-Create/2.1/my-email-id/my-prod.key/GraphLab-Create-License.tar.gz
Collecting graphlab-create>=2.1 (from GraphLab-Create-License==2.1)
  Could not find a version that satisfies the requirement graphlab-create>=2.1 (from GraphLab-Create-License==2.1) (from versions: )
No matching distribution found for graphlab-create>=2.1 (from GraphLab-Create-License==2.1)

Any ideas?
I'm currently using Python 3.6 and I need it work with it.
as mentioned on Turi
it shows 2.7 version to setup the environment. whereas on continuum which is (default download link given by turi as well) compatible to 3.6 but still throws the error.
EDIT:
For the time being I've downgraded Python version by firing below command and Anaconda + GraphLab is working fine. Any help on Anaconda + GraphLab + Python 3.6 is still welcomed.

plase help me.i'm stuck with this problem.

how to install graphlab on google colab

I am trying to install graphlab using this command pip install --upgrade --no-cache-dir https://get.graphlab.com/GraphLab-Create/2.1/email/productkey/GraphLab-Create-License.tar.gz but i am getting this error:
ERROR: HTTP error 403 while getting https://get.graphlab.com/GraphLab-Create/2.1/email/productkey/GraphLab-Create-License.tar.gz
ERROR: Could not install requirement https://get.graphlab.com/GraphLab-Create/2.1/email/productkey/GraphLab-Create-License.tar.gz because of error 403 Client Error: Forbidden for url
I am with this problem any help will be appreciated.
Thank you

Can I use graphlab in google Colab? & how can I use it?


added new chatbot patterns

This update adds new response patterns to improve the chatbot. The following three patterns were added:
"Ich kann nicht (.*)"
"Warum passiert mir immer (.*)":
"Ich fühle mich (.*)"

There are three possible responses for each new pattern.

Your Pattern should be listening on Warum passiert mir immer, (.*) the , should be mandatory or optional. Not testing for it results in a false negative. It just falls back to the default phrase.
Commit 76257b2 is a fluke. Why would you check for fuhle vs fühle? Thats not a bug fix.
Check for f[uü]e{0,1} instead. That captures fuhle, fühle and fuehle.