[Bug]: Unable to run Vite

What happened?
Reproduction repo: https://github.com/jschaf/bazel-rules-js-vite
Version
Development (host) and target OS/architectures:
Output of bazel --version: bazel 7.4.0
Version of the Aspect rules, or other relevant rules from your
WORKSPACE or MODULE.bazel file:
bazel_dep(name = "aspect_bazel_lib", version = "2.7.7")
bazel_dep(name = "aspect_rules_js", version = "2.1.0")
bazel_dep(name = "aspect_rules_swc", version = "2.0.1")
bazel_dep(name = "aspect_rules_ts", version = "3.2.1")
bazel_dep(name = "bazel_skylib", version = "1.6.1")
bazel_dep(name = "rules_nodejs", version = "6.3.1")

Language(s) and/or frameworks involved:
JavaScript and TypeScript
How to reproduce
git clone https://github.com/jschaf/bazel-rules-js-vite
cd bazel-rules-js-vite
bazelisk run //:vite -- --help

Any other information?
The main differences that I noticed from the example repos are:

This repo uses pnpm lock version 9.0
Running Vite in the same directory as the node_modules.

Here's the failing stack trace.
$BAZEL_OUT/darwin_arm64-fastbuild/bin/vite_/vite.runfiles/_main/node_modules/.aspect_rules_js/rollup@4.24.3/node_modules/rollup/dist/native.js:63
                throw new Error(
                      ^

Error: Cannot find module @rollup/rollup-darwin-arm64. npm has a bug related to optional dependencies (https://github.com/npm/cli/issues/4828). Please try `npm i` again after removing both package-lock.json and node_modules directory.
    at requireWithFriendlyError ($BAZEL_OUT/darwin_arm64-fastbuild/bin/vite_/vite.runfiles/_main/node_modules/.aspect_rules_js/rollup@4.24.3/node_modules/rollup/dist/native.js:63:9)
    at Object.<anonymous> ($BAZEL_OUT/darwin_arm64-fastbuild/bin/vite_/vite.runfiles/_main/node_modules/.aspect_rules_js/rollup@4.24.3/node_modules/rollup/dist/native.js:72:76)
    ... 3 lines matching cause stack trace ...
    at Module._load (node:internal/modules/cjs/loader:1104:12)
    at cjsLoader (node:internal/modules/esm/translators:346:17)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:286:7)
    at ModuleJob.run (node:internal/modules/esm/module_job:234:25)
    at async ModuleLoader.import (node:internal/modules/esm/loader:473:24) {
  [cause]: Error: Cannot find module '@rollup/rollup-darwin-arm64'

The problem was I had no_optional = True. I think I copied it from an example.


Add vsphere problem detector API

Add vSphere problem detector API types.
cc @openshift/sig-storage @deads2k @sttts
xref https://github.com/openshift/enhancements/blob/master/enhancements/storage/vsphere-problem-detector.md

lgtm from storage perspective - this is what we want (at least now :-) ).
vsphere-problem-detector distilled into one sentence: it's an operator that runs some checks against vsphere API regularly and reports their status - in cr.status and in metrics / alerts. Goal: detect common mis-configurations in vSphere.

/lgtm

This introduces an alpha level operator.openshift.io resource. I conclude that the operator for it will be alpha level as well.
Do we have precedence cases of alpha level operators on the platform? What is the support level of this? Dev preview? Tech preview? Does it have to be behind a feature gate?
cc @derekwaynecarr @smarterclayton

It's tech preview. And currently it's not behind any alpha gate. On the other hand, the operator's API is not really used by anything in the cluster except for cluster-storage-operator to report the overall Conditions (Available/Degraded/Progressing) and for brave users to check what's wrong with their cluster.

We have precedence for default operators using alpha types for sure. OperatorGroup  from OLM comes to my mind.

Both tech preview and dev preview need opt-in according to https://docs.google.com/document/d/1dkfqbGfi__Cs9UZMZrv1zGaJwXoHxO84YQkMlvrfAo4/edit.

The document is wrong. All upstream beta features are enabled by default and at least storage ones are tech preview in OCP, without any opt-in. And this API / operator would be  fairly useless if it was opt-in, the goal is to get metrics from it + logs in must-gather when users get into trouble.
Would v1beta1 help here to be in-line with the referenced document and in-tree features?

@jsafrane If a feature is beta upstream and on by default, and we do not want to fully support it yet in OpenShift, we need to disable the beta feature (we have done this in the past with things like disk accounting), and require opt-in behaviors to enable it.

It is possible to control beta APIs using kube-apiserver flags via a config observer owned by the storage team (this is similar to networking owning the config observer for their admission plugins for instance).
Upgrades could be more interesting though.  What specific APIs and features do you need to disable?
Also, if all your features are featuregated, the appropriate place to do this is in openshift/api https://github.com/openshift/api/blob/master/config/v1/types_feature.go#L121-L133 .  You can see various teams own particular gates being on or off and the techpreview flag enables or disables them.

/close
We're using cluster-storage-operator CRD instead.


Updated typos and crate version in README.md

Fixed a few typos and updated the sample code.

Looking good to me, thanks!


For same service X, different workload sidecar has different region/zone info on outbound cluster

Envoy Cluster does not always same region zone info
Expected behavior
Without config push, when mesh is stabilized, for a same outbound cluster X, we should expect the same region, zone info on all client side CDS.
Steps to reproduce the bug
Deploy a large number of the workloads, do query on Prometheus for the selected workloads, need to exclude ingress, since that will have different cds config for sure.
envoy_cluster_manager_cds_version{namespace="test-namespace"}, we can see different number of the cds hash.
Dig down into the envoy localhost:15000/clusters in different workloads, we can see that same cluster X, have region/zone info on some workloads, but not on some others.
The ratio is roughly 1%. Still worth calling out though.
Version (include the output of istioctl version --remote and kubectl version)
1.1.2
How was Istio installed?
istio-demo.yaml
Environment where bug was observed (cloud vendor, OS, etc)
GKE
[X] Networking
[X ] Performance and Scalability
[ ] Policies and Telemetry
Additionally, please consider attaching a cluster state archive by attaching
the dump file to this issue.

/cc @mandarjog @howardjohn

Additional info - 1% may actually be huge, because I think this is the same locality used for locality LB, in which case 1% of workloads would not respect the locality rules

I have been able to reproduce this consistently and confirmed that this DOES impact locality LB.
Steps I followed:
Deploy a service. Locality is applied correctly.
kubectl scale it up, new instances don't get locality: Verified with
$ curl -s http://localhost:15000/clusters | grep identity | grep region
outbound|80||identity.envoylite.svc.cluster.local::<IP_ADDRESS>:8080::region::us-central1
outbound|80||identity.envoylite.svc.cluster.local::<IP_ADDRESS>:8080::region::
outbound|80||identity.envoylite.svc.cluster.local::<IP_ADDRESS>:8080::region::
outbound|80||identity.envoylite.svc.cluster.local::<IP_ADDRESS>:8080::region::
outbound|80||identity.envoylite.svc.cluster.local::<IP_ADDRESS>:8080::region::

Then send traffic to the endpoint
$ for i in {0..10}; do curl identity; done
Hello from behind service a! hostname: <IP_ADDRESS>
Hello from behind service a! hostname: <IP_ADDRESS>
Hello from behind service a! hostname: <IP_ADDRESS>
Hello from behind service a! hostname: <IP_ADDRESS>
Hello from behind service a! hostname: <IP_ADDRESS>
Hello from behind service a! hostname: <IP_ADDRESS>
Hello from behind service a! hostname: <IP_ADDRESS>
Hello from behind service a! hostname: <IP_ADDRESS>
Hello from behind service a! hostname: <IP_ADDRESS>
Hello from behind service a! hostname: <IP_ADDRESS>
Hello from behind service a! hostname: <IP_ADDRESS>

We see it only goes to the one with locality set
Impact for user: if they have locality LB set they may see only one instance getting traffic
fyi @liamawhite @hzxuzhonghu
I am actively working on this btw, but haven't found root cause yet so wanted to give an update


Re-consider build dependency on tonistiigi/xx

We added a build tool for cross-compilation in https://github.com/kubernetes-sigs/blixt/pull/184:
https://github.com/kubernetes-sigs/blixt/blob/5428487fe560e05dac5eea7c7fd8d22d50388cd5/controlplane/Dockerfile#L1
This is a follow up on our previous conversation to make sure we don't forget to re-assess this dependency, and given it's place in the supply-chain decide definitively whether we need it or whether it would be straightforward to supply something ourselves.

/triage needs-information

Can I take ownership of this issue ?


Variable 'pixImage' passed by reference before being initialized

Needs to be moved after the do

For some reason cocoapods doesn’t respect the Swift version, if you switch the SwiftyTesseract and SwiftyTesseractRTE targets to 4.2 mode it will compile

This was ultimately addressed in https://github.com/SwiftyTesseract/SwiftyTesseract/pull/53

var pixImage: Pix = nil helped me


Hana 0.7.0

Update the formula to fetch the latest version of the Hana library, which is now 0.7.0.

@BrewTestBot test this please

I'll close this, since I'm releasing Hana in version 1.0.0 in the next days. Once that's done, I'll submit a PR to remove Hana from homebrew-devel-only and a PR to add it to the regular Homebrew.

Sorry I forgot about this @ldionne. Please do feel free to nag me if I take more than a few days to re-review something. Homebrew is a lot of of work and it's easy to forget individual PRs sadly.

No worries!


Connie/everythingelse

@conniec218 do you mind creating a new branch for this PR? We are afraid there will be merge conflicts since this is a pretty old branch.


Add package about

Seems you've already added this package before, it's in the package repo already.

Oh dang! sorry


How to hide the layout section completely

Hi,
I have disabled the demo.js but still the layoutbar other option are disable check out the screenshot

You need to remove the whole  &

 after the aside.
regards REJack

Hello @rashidbilgrami have you resolved your issue?

Yes i resolved the issue by changes done in the CSS i think you can implement the REJack comments may be it will sort you issue


Unable to save pipeline with a long name

Body
When a user tries to store a pipeline with a long name, the save action is blocked.
Steps to reproduce

Create or edit a pipeline.
Enter a long name for the pipeline.
Observe that saving is not possible.

Expected behavior
A message should inform the user that the pipeline name is too long.

StreamPipes Committer
I acknowledge that I am a maintainer/committer of the Apache StreamPipes project.

I can take this issue.

Hi @ethanernst11,
you can start in the component SavePipelineSettingsComponent.
This contains the logic of the pipeline start menu.
If you have any questions, please feel free to ask.
Cheers,
Philipp


Title: Adding a " mark as done " feature in Todo list JS app

Is your feature request related to a problem? Please describe.
Marking a task as done is an important aspect of any Todo list app.  This feature seems to be missing in the TODO list JS project on your 30daysofJavaScript repo.
Describe the solution you'd like.
I intend to add a mark as done feature through checkbox and strikethrough. So whenever the user clicks on the checkbox corresponding to a task , the task will be striked indicating the completion of task.
Describe alternatives you've considered.
An alternate solution will be to remove the task whenever the user indicates the completion of it. But users wont be able to refer to their completed tasks to track their progress. So leverage checkbox and strikethrough is a good option for implementation.
Add any other context or screenshots about the feature request here.
No response

@AnandK-pm Thank you for providing your insight but it is not required as of now.


An error occurred (IllegalLocationConstraintException)

i faced "An error occurred (IllegalLocationConstraintException)"
Default region name [None]: us-west-2 => is OK..
but ap-northeast-2 give me error..
do i have to something others??
i want to set up my new id for ap-northeast-2 region...

Are you facing this issue when deploying the stack using deploy.sh script or you are receiving this error when the cloudformation stack is executed

This was an issue in the the script. I updated the script to use 'mb' instead of 'create-bucket'. Please pull the latest version and redeploy. That should take care of the IllegalLocationConstraintException. Closing this issue. Please reopen if you face this again.


Onize, Q4 interviews

Interviewees: Creative Entreprenuers (Illustrators, music artistis, animators, and techies)
Number of people: 7
Interview hours: 3.5
Fee: $175

Interview Notes:
Summary: I interviewed 7 people in total. Two sessions were physical, while the rest were virtual. One was a group interview of 3 people, which went pretty well. I interviewed  1 educator, 1 data scientist turned product designer, 2 music producers, 2 illustrators, and 1 senior Product Manager. The interviews each lasted 25 - 40 minutes. They did incur internet and transportation costs.
WGQ4 - Onize - 001:

Interviewed one person
The interview was virtual and the conversation ran smoothly. Lasted for 20 mins and the interviewee brought interesting views on how AI is connected to humanity itself.
Data costs incurred $3

WGQ4 - Onize - 002:

Interviewed one person via Google Meet.
This lasted for 35 mins.
The interviewee brought really interesting angles on how AI technology is affecting the climate and environment.
Data costs incurred $5

WGQ4 - Onize - 003:

This session lasted for 35 mins.
It was physical and quite formal.
The interviewee was curious to know if the data was to be used for a new AI tool, I assured him of his anonymity while being clear about what we do.
Transportation costs incurred $10

WGQ4 - Onize - 004:

This was a group physical session and it lasted for 27 minutes
It was relaxed, interactional and felt cohesive
Transportation costs incurred $10

NB total expenses = £28
I've added this to the total to be paid


Fix Task(Run)/Pipeline(Run) metadata propagation

Changes
For annotations and labels, do not override the Run metadata with the
definition (Pipeline/Task) if they are the same. If an annotation or
label is present in both Pipeline and PipelineRun, the value in the
Run type takes precedence (same for Task and TaskRun).
Closes #4636
Signed-off-by: Vincent Demeester<EMAIL_ADDRESS>Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[ ] Docs included if any changes are user facing
[ ] Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Release notes block below has been filled in or deleted (only if no user facing changes)

Release Notes
Fix Task(Run)/Pipeline(Run) metadata propagation,  If an annotation or
label is present in both Pipeline and PipelineRun, the value in the
Run type takes precedence (same for Task and TaskRun)

/hold
Needs a small update of the docs and a test update.

@Tomcli @rafalbigaj please confirm this new behavior for your use cases 🙏

For Kubeflow pipeline on Tekton, we were expecting PipelineRun labels/annotations to take precedences over its child resources. @rafalbigaj I believe that was your expected behavior as well?

/hold cancel

/retest

/retest

/retest

@vdemeester : I noticed a side effect of this change that I was wondering if it was expected behavior.
It's stated that PipelineRuns take precedence over Pipeline labels and annotations (L&As) and TaskRuns take precedence over Task labels and annotations. In v0.34.1, I'm seeing that the TaskRuns that are created by the PipelineRuns inherit the labels & annotations of the respective PipelineRun that created it, which has the side effect of overriding any of the explicit L&As that i set on the associated Tasks. The following is my general workflow.
TaskObj.Metadata.Labels["entity"] = "task"
PipelineObj.Metadata.labels["entity"] = "pipeline"
PipelineObj.Spec.Tasks = [TaskObj]

PipelineRunObj.Metadata.Labels["entity"] = "pipelinerun"
PipelineRunObj.Spec.PipelineRef = PipelineObj

When i inspect the pod associated to the TaskRun that is produced in reference to TaskObj,  I see that the pod has the "entity" label set to the value "pipelinerun", instead of "task".
I could probably code around this, but I wanted to confirm whether the cross-over metadata propagation between PipelineRun -> TaskRun was by design and was not overlooked as a potential bug.
Thanks!
-R

Hey @hrivera-ntap, yes this is by design, the value from the Run taks precedence over the one defined in the Task.


Step #3 Running the App throws Localizations.localeOf(context, nullOk: true) : null

Step #3 Running the App from Github throws exception
IntelliJ IDEA 2021.1 (Ultimate Edition)
Build #IU-211.6693.111, built on April 6, 2021
Runtime version: 11.0.10+9-b1341.35 x86_64
VM: Dynamic Code Evolution 64-Bit Server VM by JetBrains s.r.o.
macOS 11.3
GC: G1 Young Generation, G1 Old Generation
Memory: 2048M
Cores: 16
Non-Bundled Plugins: Dart (211.7233), io.flutter (55.1.5)
Kotlin: 211-1.4.32-release-IJ6693.72
flutter --version
Flutter 2.0.5 • channel stable • https://github.com/flutter/flutter.git
Framework • revision adc687823a (12 days ago) • 2021-04-16 09:40:20 -0700
Engine • revision b09f014e96
Tools • Dart 2.12.3
Launching lib/main.dart on sdk gphone x86 arm in debug mode...
Running Gradle task 'assembleDebug'...
/usr/local/Caskroom/flutter/2.0.4/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_svg-0.19.1/lib/src/picture_provider.dart:52:59: Error: No named parameter with the name 'nullOk'.
context != null ? Localizations.localeOf(context, nullOk: true) : null,
^^^^^^
/usr/local/Caskroom/flutter/2.0.4/flutter/packages/flutter/lib/src/widgets/localizations.dart:413:17: Context: Found this candidate, but the arguments don't match.
static Locale localeOf(BuildContext context) {
^^^^^^^^
FAILURE: Build failed with an exception.

Where:
Script '/usr/local/Caskroom/flutter/2.0.4/flutter/packages/flutter_tools/gradle/flutter.gradle' line: 991

What went wrong:
Execution failed for task ':app:compileFlutterBuildDebug'.

Process 'command '/usr/local/Caskroom/flutter/2.0.4/flutter/bin/flutter'' finished with non-zero exit value 1

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 11s
Exception: Gradle task assembleDebug failed with exit code 1

Moving to latest flutter_svg solved the earlier issue:
pubspec.yaml
flutter_svg: ^0.19.1
flutter_svg: ^0.22.0

Oh crap ... the comment (pound sign) above was treated as Markdown when I saved
Use version 0.22.0 and issue is resolved.

Thanks for the very detailed report and for finding the solution!
I have a change currently out for review and hope to merge it as soon as possible.
For anyone else encountering this in the meantime, please update the dependency in the file pubspec.yaml as follows:
flutter_svg: ^0.22.0


daily shop crash

Mod Name
daily shop
Mod Homepage
https://www.curseforge.com/minecraft/mc-mods/daily-shop
Minecraft version
1.20.1
Describe the bug
When launching the game letting it start up it produces this msg when it crashs before it finishs loading the game The game crashed whilst initializing game Error: net.minecraftforge.fml.loading.EarlyLoadingException: Could not execute entrypoint stage 'main' due to errors, provided by 'dailyshop'!
Steps to reproduce

...
Logs
https://pastebin.com/SnDVDv6n
Additional context
No response

You need to install Architectury. The mod works fine for me on Connector Beta 43


Example with using sequelize typescript to mock database

Hello @RobinBuschmann ,
First of all thank you for such a great project. One question I did have a question on is how to use sequelize-typescript to mock the database and run queries against mocked data

+1

I tried the following:
{
          provide: SOME_SYMBOL,
          useFactory: async () => {
            const sequelize = new Sequelize({
              validateOnly: true
            });
            sequelize.addModels([someModel, someModel2]);
            return sequelize;
          }
        }

when I try to create an instance of a model to mock the data that is in database, I receive the following:
this.lib.Database is not a constructor
@RobinBuschmann any ideas here? I would love to not have to download another lib for tests only

I have the same issue, and even if I leave all the other options the same, adding validateOnly: true leads to this.lib.Database is not a constructor.

I have the same problem:
import { getModelToken } from '@nestjs/sequelize';
import { Test } from '@nestjs/testing';
import { Sequelize } from 'sequelize-typescript';

import { Role } from './role.model';
import { RolesService } from './roles.service';

const sequelize = new Sequelize({ validateOnly: true });
sequelize.addModels([Role]);

const testRole = new Role({
  name: 'owner',
});

describe('RolesService', () => {
  let rolesService: RolesService;

  beforeEach(async () => {
    const serviceModule = await Test.createTestingModule({
      providers: [
        RolesService,
        {
          provide: getModelToken(Role),
          useValue: {
            findAll: jest.fn(() => [testRole]),
          },
        },
      ],
    }).compile();

    rolesService = serviceModule.get(RolesService);
  });

  it('should get all the roles', async () => {
    expect(await rolesService.getRoles()).toEqual([testRole]);
  });
});

Hey, just came here to say that i can't find a solution, so i've literally used a fake sqlite database at the unit tests and mock ALL results.
I Know that it isn't the best solution, but i've searched a lot and can't find anything.
So, the code is:
`
let service: YourService;
let model: typeof YourModel;
beforeEach(async () => {
const modRef = await Test.createTestingModule({
  imports: [
    SequelizeModule.forRoot({
      dialect: 'sqlite',
      database: ':memory:',
      autoLoadModels: true,
      synchronize: true,
      logging: false,
      models: [**YourModel**]
    })
  ],
  providers: [
    **YourService**,
    {
      provide: getModelToken(**YourModel**),
      useValue: {
        findAll: jest.fn(),
        findOne: jest.fn(),
        create: jest.fn(),
        update: jest.fn()
      }
    }
  ]
}).compile();

service = modRef.get(**YourService**);
model = modRef.get<typeof **YourModel**>(getModelToken(**YourModel**));

});
`


Replace GetCycleRoot with [[CycleRoot]] field

This fixes a spec bug first reported by @sokra in https://github.com/tc39/proposal-top-level-await/issues/158#issuecomment-769814915 and being tracked in V8 in https://bugs.chromium.org/p/v8/issues/detail?id=11376.
The same example case is described in both links above.
The issue as discovered by @syg is that when GetCycleRoot(C2) is called, the execution of C2 has already happened sync, so it does not participate in the AsyncParentModules linkage being utilized by GetCycleRoot. As a result X isn't properly depending on the root of the cycle at C1 and is instead depending directly on the execution of C2 which will have been completed already.
The fix is to ensure GetCycleRoot gives the proper strongly connected component root corresponding to the DFSAncestorIndex. A naive adjustment would be to iterate through the imported modules down the DFSIndex to reach this, but that approach would risk interactions with other DFS numberings which would result in non-deterministic behaviour. If we did use a global DFS numbering that would be one way to work around that, but it seems unnecessary.
For this reason I've instead simply added a new field to link the cycle root reference for each module directly, and setting this in the main cycle transition code path. It comes out quite simply from that.
Review would be much appreciated further.

has this change been validated in implementation yet? I can get around to merging it into engine262 eventually but it might be good for someone to do that proactively

I am validating it now, We also found the same issue in our implementation and I have a test for it.

TLA ships in Chrome 89 and stable branch cut for Chrome 89 is on Feb 23. I'm not sure this is a high-enough profile patch to warrant a back merge into the branch from tip-of-tree, but I'll ask.

This does indeed fix the issue raised in #156 and I can also now say with certainty that with the previous spec we were not hitting line 12.d.iv.3 -- even with the test @jorendorff wrote. It just looked like there was an issue in our cycle implementation, but we verified that we had the spec pretty much exactly implemented. I believe this is a required change, albeit minor, and we will likely need to bring it up as an update at the next meeting.
With the change in this patch, this cycle issue is fixed. All of the test262 tests, along with our local tests, pass. We should incorporate the test written in #156 into test262 -- though it is masked by #152 -- I will see if I can get a test that will fail regardless..

The fix is easy to implement in V8 and decreases code complexity at the cost of an extra field per SourceTextModule (now called Cyclic Module Records in the spec) object. The extra memory isn't an issue today but if we ever want to approach a world with thousands of ESMs per page, we might need to take another look.
V8 CL here: https://chromium-review.googlesource.com/c/v8/v8/+/2667772


Appears to not work at all in Rails 3

Tried to get this gem working but it appears I couldn't.  This gem does nothing with the follow attempt in Rails 3.1:
class SpecialistOffice < ActiveRecord::Base
  include PackRat::CacheHelper

  attr_accessible :phone, :phone_extension, :fax, :direct_phone, :direct_phone_extension, :sector_mask, :public_email, :email, :open_saturday, :open_sunday, :office_id, :office_attributes, :phone_schedule_attributes, :url, :location_opened

  belongs_to :specialist
  belongs_to :office
  accepts_nested_attributes_for :office

  has_many :user_controls_specialist_offices, :dependent => :destroy
  has_many :controlling_users, :through => :user_controls_specialist_offices, :source => :user, :class_name => "User"

  #offices have a phone schedule
  has_one :phone_schedule, :as => :schedulable, :dependent => :destroy, :class_name => "Schedule"
  accepts_nested_attributes_for :phone_schedule

  has_paper_trail

  default_scope order('specialist_offices.id ASC')

  def self.all_cached
     cache do
       all
     end
  end
end

Benchmark.ms{SpecialistOffice.all_cached} => 646.93
Benchmark.ms{SpecialistOffice.all_cached} => 603.93
Benchmark.ms{SpecialistOffice.all_cached} => 630.93
Do you think it's something in my Model that's stopping this?  I really love the DSL you've come up with in this gem, it's a shame that it doesn't work.

Can you see what cache keys are being used?
Can do this by redefining your method as
def self.all_cached
    cache [], debug: true do
        all
    end
end

With
def self.all_cached
    cache [], debug: true do
        all
    end
end

The output appears to be broken, coming out on three lines like:
all_cached
/
specialist_offices/1-20150218233128/SpecialistOffice
/
72436c72e709022e17138a8251778312

With:
def self.all_cached
    cache "", debug: true do
        all
    end
end

I get what appears to be a correct string, though no caching it appears either when I disable debug with ""
all_cached/specialist_offices/1-20150218233128/SpecialistOffice/5db2f6cae4a79e9c5dbc288c14815442

And if you run that multiple times is it changing?


Robot should stop braking after motion stops

Currently the robot stops braking after 5 seconds of disable. We should have it stop braking after the robot stops moving in disabled (which we can see given the encoders' values).

@andrewda, I can fix this.

Would it make sense for me to spawn a thread that has a while loop running waiting for the encoders to indicate the robot has stopped?


Bot stops reacting to mentions and messages

When freshly starting the bot, everything works fine.
But after a while (time unknown), the bot stops reacting to mentions. The log doesn't show any mentions or messages until a restart.

I have that problem too. I run 3 bots off my personnal machine and from time to time, I have to focus the terminal and type something for them to react.

I get this occasionally too. It used to happen much more before I formatted and did a clean install of Windows 10 though.

Same thing here. Works okay locally when using Ubuntu on Windows 10 (Linux Subsystem for Windows) but when it's on my friend's server (Ubuntu in a VM on Windows 7, loaded in tmux via SSH), it just stops responding to tweets.

This same thing is happening to me. Hopefully it can be pinpointed to something, otherwise my bot's function is limited :P

In the last couple weeks, this has started occurring much more frequently.

If it helps, I've been running my ebooks bot on a Raspberry Pi 3 and I very rarely get this issue now. When it was on my friend's server, it was being lumped in with other tasks that he was doing, which led to my bot and the VM it was in to slow down. This might be due to a performance issue.
Also, I'm going to keep an eye out for any errors Rufus Scheduler catches.  I also have a feeling that if the bot runs into any errors the reply features stop working.

Same issue here, running on a Raspberry 2

Seeing the same issue on Pi 3. Running multiple bots and they all stop working at exactly the same time. They also still tweet, just don't notice events any more.


On Get File Structure page ... (step 7  of task "To create a data exchange definition")

Here is written:
On the Get File Structure page, select the related structure file, and then choose the OK button. The lines on the Column Definitions FastTab are filled according to the structure of the data file.
But no mentioning that this only applies for XML or JSON. When pressing the "Get File Structure ..." action when defining a Data Exhcnage Definition for FIle Type "Variable Text" an error is show saying: File type Variable Text is not supported.
This might b made explicit.

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

ID: 350ad27c-dd1c-fde6-27a3-faaf9c0c3da1
Version Independent ID: 704d9728-05d0-c21a-9d68-d23af8fc6457
Content: Define how data is exchanged electronically - Business Central
Content Source: business-central/across-how-to-set-up-data-exchange-definitions.md
Service: dynamics365-business-central
GitHub Login: @SorenGP
Microsoft Alias: sgroespe

Duplicate of #296


Introduce "make run_test" for running tests

Rename the existing "run" makefile target into "run_test", in order to
avoid clashing with the Native Client's definition of the "run" target.
Previously we were intentionally using this clash in order to reduce
amount of boilerplate needed for running tests, but that came with the
price of doing some nontrivial hacks (like changing the current
directory CURDIR back and forth). This commit gets rids of these hacks
and makes tests' makefiles slightly simpler, which will also simplify
the upcoming Emscripten test runner implementation.
This is a preparatory fix for introducing Emscripten builds of unit
tests, as tracked by #177.

Thanks!


Validate that VkSwapchainCreateInfoKHR::imageSharingMode = VK_SHARING_MODE_CONCURRENT when using separate present queue family.

Moved from gitlab 94
Would it be possible to add validation that VkSwapchainCreateInfoKHR::imageSharingMode = VK_SHARING_MODE_CONCURRENT when presentation happens on a different queue family than updating the swapchain images?

This check is present in the core_validation layer.


Labels to enable/disable specific triggers

Can I request a new feature please - to add labels to enable/disable specific triggers for specific containers.
To give an example, I can setup the Docker trigger to update my containers when a new image is found, but I don't want to update every container. I do, however, want to know when there are updates available.
In this scenario I am using the docker trigger for updates and the pushover and mqtt triggers for notifications, etc.
What I would like is the ability to add a label to containers to specifically enable/disable specific triggers - e.g.
wud.triggers.disable={{trigger_name}}
or
wud.trigger.{{trigger_name}} = false

Hi,
Maybe I can improve the existing feature trigger threshold.
WUD_TRIGGER_{{trigger_type}}}_{trigger_name}_THRESHOLD=all|major|minor|patch

If I extend this feature to make possible to override per container, it should do the trick 🤔
# Prevent from docker trigger to update the container
wud.trigger.docker.local.threshold=none

# Trigger pushover regardless of the change level
wud.trigger.pushover.me.threshold=all

What do you think?

Sounds like that should do the trick just fine.

@fmartinou, Thanks for looking into this, I think this would be a great addition that unlocks so many possibilities!
I too definitely would not want auto-update on all the containers, only on specific ones for minor version, and maybe only a couple with major auto-updates (where I don't really care if it crashes)
I liked your proposed solution but could I suggest to also have the none option for the trigger threshold definition. As in:
WUD_TRIGGER_{{trigger_type}}}_{trigger_name}_THRESHOLD=all|major|minor|patch|none

That way the trigger would be off  by default for all containers, except if explicitly added through labels.
Thanks!

Hi,
It's implemented: see https://github.com/getwud/wud/issues/502
(available from 7.2.0)


fix nilp error by #102 for tls conn (again)

*Issue #105
Description of changes:
Fix nil pointer error again with a test fix due to timeout.
The test job https://travis-ci.org/aws/aws-xray-sdk-go/jobs/520674954 is failed for go1.9 env only.
However, if I set GOMAXPROCS=1 and run tests, it reproduces that test fail.
Maybe Recv timeout 100ms is too short for single goroutine env.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@t-yuki , thank you so much for the quick response. Let me try to run it again.

@t-yuki , I merged your changes. Thank you for your contribution.


compatibility for node >=v16.2.0

This seems to help for https://github.com/myndzi/wtfnode/issues/40 - although I don't know what I'm doing here :-)

"All of these callbacks are optional" - wonder if this is a node.js bug?

Thanks for this, it worked. A different test failed for an unrelated reason, but I fixed that too. I'll merge the changes soon.


[Bug]: The SQL window will not automatically select the permission type when initiating a database permission application

ODC version
odc424
OB version

What happened?

What did you expect to happen?
The permission type will be automatically filled in
How can we reproduce it (as minimally and precisely as possible)?

Anything else we need to know?
No response
Cloud
No response

Currently, the database can only be selected by default, and the permissions can be selected by yourself.


Move the decl'H5 plugin to more idiomatic C++

In GitLab by @jbigot on Dec 15, 2017, 16:34

In GitLab by @Roussel-C on Dec 21, 2017, 15:55
closed via merge request !89

closed via commit 9ec842ef389603fb6b0b3377176b6f9da9ed1679

mentioned in commit a9c6933dd6bdfda975f52855f628755e5f6fb757

mentioned in commit 9ec842ef389603fb6b0b3377176b6f9da9ed1679

mentioned in commit 8e2fa445c3497a091e826baa3c85f89823da49de


please add new course of abp module

thank you for your great work! would you please add some coure of how to write a abp module?

It is on the road map, but will get some time.


Feature Request: New crossing presets for the top 8 pedestrian crossing markings

Description
This issue is to support @RitaDee in the issue she's working on (#1154). Currently in the id-tagging-schema we have only three crosswalk presets- unmarked, marked, and marked(zebra).  The marked(zebra) preset also has incorrect tagging: instead of crossing:marking=zebra it has crossing=zebra.
I will submit a PR to the id-tagging-schema with this same proposed scheme:
Existing presets:
Unmarked: crossing=unmarked;crossing:markings=no
Marked: crossing=marked:crossing:markings=yes
Existing preset but with incorrect crossing:marking:
Marked-Zebra: crossing=marked;crossing:markings=zebra
New presets according to global tag popularity overrall:
Marked-Lines: crossing=marked;crossing:markings=lines
Marked-Ladder: crossing=marked;crossing:markings=ladder
Marked-Dashes: crossing=marked;crossing:markings=dashes
Marked-Dots: crossing=marked;crossing:markings=dots
Marked-LadderSkewed: crossing=marked;crossing:markings=ladder:skewed
So, the idea here is that we have the ability to select which type of markings we want for a marked crosswalk, and to have those presets available for the hotkey to cycle.

Using the new overrides I can now get:

Preset strings:
highway/footway/crossing/zebra
highway/footway/crossing/lines
highway/footway/crossing/ladder
highway/footway/crossing/dashes
highway/footway/crossing/dots
highway/footway/crossing/ladder:skewed

This is awesome!   I love that we're using the new crossing:markings tags that were approved last year 👍


Add NVIDIA SDK path to the CUDA link flags

Summary
This commit adds the path to the NVDIA SDK libraries to the
CMAKE_CUDA_LINK_FLAGS. Moreover, it ensures that these
link flags are specified to the registered CUDA library that
is used with BLT.
This allows applications to link additional libraries that are supplied
with the NVIDIA SDK by listing them in the list of dependencies,
e.g., nvToolsExt, cublas, etc. In addition, CMAKE_CUDA_LINK_FLAGS
may also be specified in a host-config or at the command line and
those will now be correctly propagated and associated with
BLT's registered CUDA library.

The linux_gcc8 CI is failing because MPI is not found. Any ideas?

Ok, I am not sure what the issue is with Linux_gcc8 CI.
After chatting with @white238 and trying a few things, I am now getting the following error:
docker: Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "exec: \"/home/axom/axom_tpls/gcc-8.1.0/cmake-3.9.6/bin/cmake\": stat /home/axom/axom_tpls/gcc-8.1.0/cmake-3.9.6/bin/cmake: no such file or directory": unknown.
time="2020-04-28T03:55:20Z" level=error msg="error waiting for container: context canceled"

##[error]Bash exited with code '127'.

So, it looks like Azure was not able to load the image?
This also appears to be one of the most recently updated and largest images we have (see https://hub.docker.com/r/axom/tpls/tags)
Does Azure have a time limit on how long it takes to download an image?


nixos/switch-to-configuration: fix dbus implementation used for test

Description of changes
Makes the switch-test work with both dbus server implementations. Related to https://github.com/NixOS/nixpkgs/pull/307731

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg test switch-test


[Feature request] Stream audio from input device in real-time

I combined this amazing tool with the real-time implementation by https://github.com/facebookresearch/denoiser . Hopefully this might be useful to someone.
Proof-of-concept:
https://github.com/nnyj/python-audio-separator-live

Woah, this is super cool, thanks for sharing!
What is/was your use case, out of curiosity?
I see you had to pull in the audio_separator code into your own project and make a bunch of changes to it to make sense for a live stream, which is understandable but also kinda unfortunate as it means any further improvements to this project won't be easy to pull in.
@nnyj - how would you feel if I refactored / reintegrated your code into this project, to essentially just add a live mode to audio-separator - I'd of course then add you as a maintainer of this project too so you could push your own updates / continued improvements to it.
Totally fair if you'd prefer to keep your work in your own repo / a separate project, but just thought I'd ask 😄

Hey, thanks for your interest. Feel free to re-integrate into this project, it is open source after all! 😄. Although the POC code is admittedly messy.
The idea to implement inferencing in real-time was more out of a curiousity since GPUs has been fast enough to split the stems in multiple times of real-time. A quick test using the UVR GUI, I was able to achieve 5.48x real-time during conversion with an ensemble model (MDX-NET Inst Main + Inst 3 + Kim Vocal 2).
The use case is of course endless, I'm a huge fan of instrumental music and enjoy listening to my library without having to convert everything. Anyone could also say, stream any music from online services such as youtube/spotify without needing/having the actual audio files.
A quick look at other projects show that there were similar interests/requests:

https://github.com/deezer/spleeter/issues/194
https://github.com/deezer/spleeter/issues/276
https://github.com/facebookresearch/demucs/issues/515

Source separation has come a long way and I found the MDX-Net models striked a good balance between inference time and audio quality. But I think there is an inherent buffer of at least 1-2 seconds required for the models to do its magic, so it may never achieve "full" realtime. For my use case, that is perfectly fine though.

Hello @nnyj
you have provided a nice summary here. I am also facing the same constraint of minimum 1.5 seconds needed for e.g. spectrogram computation so that the AI has enough temporal/ contextual information to do the separation.
Does anyone here have an idea on how to overcome this? this should be possible since there are audio plugins that are "real-time".
Here, the author speaks even of a low latency of 46.4 ms
https://github.com/james34602/SpleeterRT/issues/8

If you raise a PR getting started on adding this feature / capability to audio-separator, I'm happy to help figure out issues and try to resolve them @GenzPN
I'm just not personally motivated enough to do all the work on my own 😅


When ha-bridge closes I lose all data

I'm starting it using the following command in a .bat file:
java -Xms32m -Xmx128m -jar C:\amazon-echo-ha-bridge\ha-bridge-3.5.1.jar --upnp.config.address=<IP_ADDRESS> --server.port=8080
Everything works fine, except when ha-bridge closes, none of the devices are saved, even when I try to back them up.  First I had an error that the data directory didn't exist, so I created it, and now when I try to backup, nothing is in the data folder.

I'm seeing this issue too. All config is gone when I restart...
Any luck with figuring out why??

No, none yet.  Still the same problem.

Happening for me too. Boo...

https://github.com/bwssytems/ha-bridge


AKS 6 part series - added AKS networking example scenario scripts

Thanks Anuraj!
Chris Bellée
Senior Engineer | FastTrack for Azure | Azure Engineering
<EMAIL_ADDRESS>| M: +61 404 161 351
Learn more about FastTrack for Azure herehttps://azure.microsoft.com/en-us/programs/azure-fasttrack/. Stay up to date with Azure herehttps://aka.ms/fta/stayuptodate.
[cid:7096782c-988d-42f4-bc23-d4d78060bcec]
This email message may contain confidential and proprietary information.  Any unauthorized use is prohibited.  If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

From: Arunraj Selvaraj @.>
Sent: Thursday, 18 May 2023 2:46 PM
To: Azure/FTALive-Sessions @.>
Cc: Chris Bellée @.>; Assign @.>
Subject: Re: [Azure/FTALive-Sessions] AKS 6 part series - added AKS networking example scenario scripts (PR #213)
Merged #213https://github.com/Azure/FTALive-Sessions/pull/213 into main.
—
Reply to this email directly, view it on GitHubhttps://github.com/Azure/FTALive-Sessions/pull/213#event-9275592001, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACB4EKS3LUFYC47FR273CJLXGWSSTANCNFSM6AAAAAAX5NIBOQ.
You are receiving this because you were assigned.Message ID: @.***>


ProtoJSON safely encode JSON to ASCII-8BIT (String#b)

ProtoJSON data bytes support w/ String#b
https://github.com/coinbase/temporal-ruby/issues/263
JSON payload converter does the same here.

We're hitting this as well, any way to get this merged and tagged in a release?

@DeRauk @jeffschoner Any chance you can review? Thank you!


批量插入数据 批量读取接口没有

一次put 一次get 都会新建rpc连接； java版本有 一次rpc，读写一组数据的接口。 gohbase会不会加这个接口？

The author said his organization has been moved the data to other db, so this function will no be developed. The author said you can run go routines on your project.


Josh IBMQC2021 ex5 Solution

Name: Joshua D. John
Score: 3
Parameters: 16
Energy: -1.0862138177821778 [Ha]
error: -0.0024921979525627247 [Ha]

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Sorry for the delay. Thank you very much for your submission!


Building the docs locally adds lots of noise for version control

See below. I assume all html directories could be added to the .gitignore. The additional autogen files, as well, as they should be auto-generated when pushing anyway?

There are two cases:

the HTML files generated by autogen should be added to .gitignore.
the HTML files generated by normal notebooks, we need to push it manually.

I'll make a PR!


RestApi base path not compliant with location requirement in production

Description
According to Developer support, if user account is located in EU, Rest API URL should point to EU.
Issue
The specified Integrator Key was not found or is disabled. Invalid account specified for user
Where
https://github.com/docusign/docusign-esign-node-client/blob/master/src/RestApi.js
Fix
const PRODUCTION_BASE_PATH = 'https://www.docusign.net/restapi';

should be
const PRODUCTION_BASE_PATH = 'https://eu.docusign.net/restapi';

@splacentino - You shouldn't need to manually set this base path property as it is a placeholder that will resolve to the correct base path after you authenticate and make the getUserInfo  call. This function returns a UserInfo object that contains your baseUri property, which is then used for your API calls
The "Obtaining user information" section of this page explains this process in more detail


Update specification.md add padding example

Else nobody knows what you are talking about, alas.

Hi @jidanni - the files have been updated and there's a conflict - can you resolve it and I'll take a look.

Sorry, I am no longer available.


Add Delete, Archive and Pin button to memo detail pages

Is your feature request related to a problem?
When you click a marked / linked memo from another memo, you are navigated to the detail page of that memo (your.site/m/memo_id) and if you would like to delete / pin this memo, you'll have to go back and search for it again.
Describe the solution you'd like
Add Delete, Archive and Pin button to memo detail pages
Additional context
No response

@boojack are you accepting PR for this issue or for any issue in milestone? Or are these just for your self?


keep_focused is a noop

not sure when this started happening but with the following config:
split-monitor-workspaces {
    count=10
    keep_focused=true
}

I'm still placed on the first workspace on each monitor when reloading hyprland
hyprland 42df58fc0636d922c2e369f22847bf47f2367855
split-monitor-workspaces 9befbe8e72f223531ec3382b26300e9f0be6cddc

I'm not 100% sure but I think it should be 0 or 1, not true/false.

But I can reproduce your issue. I'll investigate.

Ah, it's my fault:
https://github.com/Duckonaut/split-monitor-workspaces/blob/9befbe8e72f223531ec3382b26300e9f0be6cddc/src/main.cpp#L210-L211

tested and it works, thanks!

I'm not 100% sure but I think it should be 0 or 1, not true/false.

it can be either, true works for me right now


auto-value-gson kills auto-value 1.5.1

When using these annotation processors in Eclipse, auto-value completely stops working for me.
Is auto-value-gson not compatible with auto-value 1.5?

Working fine in my projects. I'm using auto-value-gson 0.6.0, autovalue 1.5.1 and AndroidStudio.

works fine here too. Your issue is hard to diagnose without more details

I don't know what we've changed on our side, but it's working for us now, too. I am sorry for creating this issue :)


Plot issue when using int64 values

Wave SDK Version, OS
0.10.0
Hit a but while experiment with this code:
from h2o_wave import site, data, ui, app, main, Q
import numpy as np

@app('/')
async def serve(q: Q):
    age = [10, 10, 20, 30, 40, 20]
    unique, counts = np.unique(age, return_counts=True)
    rows1 = list(zip(unique, counts))
    rows = [(0,1), (2,3)]
    q.page['plot1'] = ui.plot_card(
        box='1 1 -1 -1',
        title='Age Count',
        data=data('age count', rows=rows1),
        plot=ui.plot([ui.mark(type='interval', x='=age', y='=count', x_min=0, y_min=0,
                              x_title='Age', y_title='Count', color='#33BBFF')]
                     ))
    await q.page.save()

If I use rows, the code works fine because the values are int. If I use rows1, the values are of type int64 and it complains about int64 values not being JSON serializable.
TypeError: Object of type int64 is not JSON serializable
Should we try to cast to int to avoid hard fails?
cc @lo5 @mturoci

eg. this works as a workaround:
rows1 = [list(zip(unique.to_list(), counts.to_list()))]

eg. this works as a workaround:
rows1 = [list(zip(unique.to_list(), counts.to_list()))]

This is not a bug. In general, we use Python's json to serialize values, and np.int64 is technically not a Python number, therefore json will complain.
For now the to_list() is necessary, but we should probably look at providing a global switch that optionally turns on numpy-special-handling and deals with such cases.

This is not a bug. In general, we use Python's json to serialize values, and np.int64 is technically not a Python number, therefore json will complain.
For now the to_list() is necessary, but we should probably look at providing a global switch that optionally turns on numpy-special-handling and deals with such cases.

Right, I phrased the title incorrectly. This is more about handling this case vs an actual bug.

Right, I phrased the title incorrectly. This is more about handling this case vs an actual bug.

Related to #447

Is this issue open? Can I take up this issue? If yes can you please assign this to me?

Hi @ajjayymahato! You can try it if you feel like it, but it's not going to be easy. I would recommend picking something easier to start - see https://github.com/h2oai/wave/labels/good first issue.


cli(test): support running sub tests in parallel

Some tests could be greatly sped up by running all subtests in parallel. An internal example is the code-gen/error tests.
An example api could be
test("example", async t => {
  await myTestSetup();

  // Existing api to set the timeout of subtests
  t.timeout = 1500;

  // Accepts serial (current behavior), and parallel.
  t.subtestOrder = "parallel";
});

Did some testing with this. In my current projects, it doesn't necessarily improve by a whole lot. I also don't like the api much. So closing for now.


can.c driver does not define IRAM_ATTR on interrupt routines (IDFGH-1960)

Environment

Development Kit:      [none]
Kit version (for WroverKit/PicoKit/DevKitC): [v1|v2|v3|v4]
Module or chip used:  [ESP32-WROOM-32D]
IDF version (run git describe --tags to find it):  v3.2.3
Build System:         [platformio]
Compiler version (run xtensa-esp32-elf-gcc --version to find it): 1.22.0-80-g6c4433a5 5.2.0
Operating System:     [Windows]
Power Supply:         [USB]

Problem Description
Hangs in nvs routines when using can driver simultaneously. I think it is due to missing IRAM_ATTR on the can interrupt routines (can_intr_handler_main etc.)
Expected Behavior
Can use nvs and can simultaneously without hangs
Actual Behavior
Occasional hangs when using nvs and can simultaneously
Steps to repropduce
use can library (can_receive) in task and in another task use nvs_set_... functions
Code to reproduce this issue
Too extensive to include
Debug Logs
N/A: hangs without crash (unless WDT is enabled, then you get a WDT)
Other items if possible

Good point. I do not use ESP-IDF's CAN driver, but an other design based on Thomas Barth's work for historical reasons. I always wondered, if IRAM_ATTR would be authoritative for the CAN ISR to work reliably but did not manage to find a clear answer by now. So I have a provision like that in the code:
/**
 * define ISR_IN_IRAM to allocate the interrupt service routine in IRAM.
 * By default this is disabled (defined as NOT_ISR_IN_IRAM).
 */
#define NOT_ISR_IN_IRAM

#ifdef ISR_IN_IRAM
static  IRAM_ATTR  void CAN_isr(void *arg_p){
#endif
#ifndef ISR_IN_IRAM
static void CAN_isr(void *arg_p){
#endif

Could you just give it a try, set IRAM_ATTR for the ISR and see if it solves the issue?
Best
Markus

@arjanmels thanks for reporting this issue. Could you post the Task WDT error log you're getting. I want to see exactly which task is triggering the Task, Watchdog timeout.
I'm not sure if this is an IRAM_ATTR issue. Because none of the CAN driver functions are placed in IRAM, the CAN driver will not run whilst flash cache is disabled, but it should not crash either. The CAN peripheral may lose a few messages if NVS is disabled for too long, but it should not crash.
Could you check the on the duration of your NVS access (i.e., get the system time before and after the nvs_set operation).

In the meantime I worked around it by using can_stop before the NVS accesses and can_start afterwards. (And the hardware I was working on is delivered to the customer, so I cannot do additional testing at the moment.)
I indeed noticed that a lot of routines are called form the interrupt handler.
To me it looks like a deadlock: CAN interrupt during the NVS access cannot be served because the interrupt routine is in flash, but also teh NVS routine cannot continue.

CAN/TWAI driver's ISR supports the option of being placed in IRAM as of commit 4c57f50fe4abb53e2b48e9237f3037d8bd79aff2 (v4.3), a0bb9b2f57ccd8cec5d258a9a8bad0fef3dfefcf (v4.2), backport for v4.1 branch is still pending. This feature can be enabled in menuconfig AND providing the ESP_INTR_FLAG_IRAM in the driver configuration structure.


could you please add instructions to run in a different servlet container?

I'd like to try this application but running under the Tomcat servlet container. Would be great to see instructions on how to do that (or, non-container specific instructions of how to run the war file as a web application in any container).

We do not want to make things to complex, the main thing is to understand Conversation and Discovery services. If anyone out there has time to get this running with Tomcat, please share.


SCIM2 search filtering not working for secondary userstores custom claims

Describe the issue:
When using SCIM APIs to search user with custom claim from secondary userstore, if the custom claim is mapped to local claim in secondary userstore, it is working as expected but when custom claim is mapped in primary userstore and not mapped in the secondary user store, searching is not working for secondary userstore with that custom claim.
How to reproduce:

Add scim custom claim configuration to scim2-schema-extension.config file
Add custom claim to local claims only to Primary user store
Add custom claim to External claims
Send below request to search users

curl -v -k -X POST --user admin:admin --data '{"schemas": ["urn:ietf:params:scim:api:messages:2.0:SearchRequest"],"filter":"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:entityID eq 11850","domain":"custom","startIndex": 1,"count": 10}' --header "Content-Type:application/scim+json"  'https://localhost:9443/scim2/Users/.search'

Will get the below error

"detail":"Unsupported attribute: urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:entityID"

Add local custom claim mapping to secondary userstore and send the above request, that will give the search results

Expected behavior:
Even though, the custom local claim mapping is not presented in the secondary userstore, if it is presented in primary userstore domain, it should use the primary userstore domain claim configuration.
Environment information

Product Version: [ KM 5.9.0]
OS: [ Linux]
Database: [ H2]
Userstore: [primary - LDAP, secondary - JDBC]

@sumedhe Is it reproducible in master? Can we close this issue?

It's not reproducible in mater. We can close this.


namespace as label

#13 - seems I fixed it and it's backward compatible =)

Oh, wow 😍 I'll take a look ASAP. 👍

Thanks for the great and fast review (and useful tool) 🙃


Doesn't continue after Steam Guard Check

Using version 1.5.1
Trying to login using the downgrader, but it keeps looping the Steam Guard verification even if I press allow.

Even after Login Successful, and beginning downloading, its ask after Steam Guard in console, but cant type in anything

I have same issue but asks to use my phone app to scan a QR code but there isn't one, you can get a code to copy every 60 seconds but don't where your supposed to post the code, the console is just stuck in a loop.
Found this fix works from NEXUS Q&A:
Open steam, open the steam directory in the upper left corner.
Go to settings.
Go to security
Click steamguard and disable.
You will also have to disable the guard in your mobile app, the reauthorise it and you will be given a code that you are now asked to enter there is a place to enter said code then it should download and install Fallout London, looks like it takes a while to update.

Even after Login Successful, and beginning downloading, its ask after Steam Guard in console, but cant type in anything

Press the (steam)+(x) button to bring up the keyboard, type the password or code and even though it doesnt look like anything appears on screen it is just hidden. The cursor doesnt move but thats a linux thing.

This release might fix the issues with steam guard https://github.com/Fallout-London/FOLON-FO4Downgrader/releases/tag/1.5.3

Is it fine to enable steam guard after its done it's downgrading?

This release you might be able to just have it on during the entire run but yeah, if it dosen't work then you should enable it like right after lol

Still not working with email codes. If I'd had months to do it, as a developer I'd be extremely embarrassed that people have to disable a security feature here.

Do you want a refund or something?

Unfortunately, I thought I was on a winner with this but after further testing it just fails miserably, I can't justify downloading Fallout 4 just to have it trashed to add the Fallout London I will leave the subject until somehow someone can make it a lot easier to install without turning off the Steam Guard security, thank you all for your efforts.

Tomorrow i will look into changing backend to steamcmd, might fix this since

the version directly from here worked for me, not teh one on Nexus

Same issue here, it will just infinitely ask me to verify my Steam Guard and not progress past that.

Any luck with a work around instead of disabling steam guard?

Theres a chance the newest release fixes it and i would ask anyone please try it, other than that check out the manual method.

Theres a chance the newest release fixes it and i would ask anyone please try it, other than that check out the manual method.

For the life of me, I can't think of any reason why a developer should ask anyone else, let alone strangers, to test something if the developer himself has not agreed to test his code himself.
It would have been easy for you to find a Steam account with Fallout 4 and test it once with mobile or email Steam Guard. You will never have done that. Otherwise it would work. I think I can say that with over 30 years of professional experience.
If you clearly explain what you tested, then I'll be happy to test it again. But not like this.

The reason the last version wasn't working was because it was only me and a handful of other who tested it, and it worksed for us, but it ended up breaking randomly for random people without me being able to in any way shape or form recreate the issue, therefore I cannot be the only tester :D

Can confirm 1.5.4 doesn't solve the steam guard issue

No nate, to be honest, I will wait until it's totally fixed, I am enjoying playing the main Fallout 4 game so it's not that urgent.
Paul D Gutsell
"Care for those that, care about you"
Sent from Proton Mail Android
-------- Original Message --------
On 29/07/2024 19:07, Rich  wrote:

Any luck with a work around instead of disabling steam guard?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

Can confirm 1.5.4 doesn't solve the steam guard issue

Mobile or email?

1.5.4 dosen't work with phone auth, try email auth for that release or wait for the next version

Should be fixed in latest release, please reopen if not


feat: introduce dashboard module

Couple things:

You need to add the .spec files for each component
Cleanup the styling of the dashboard

I am also thinking this should be the 'ADMIN' module to use to adjust settings in the API

sure i will create spec.ts files.

spec.ts files are created
ng-lazy.js is not supporting window 10


Error AADSTS501481: The Code_Verifier does not match the code_challenge supplied in the authorization request.

When requesting the authentication using insomnia-plugin-azure-ad-authentication, I met the error:
invalid_grant - 501481 - [2024-08-29 03:22:33Z]: AADSTS501481: The Code_Verifier does not match the code_challenge supplied in the authorization request.

The request params:

Function to Perform: Entra ID Token — Get a Microsoft Entra ID token
Authority: Entra ID global service — https://login.microsoftonline.com
Scopes: openid profile offline_access
Redirect URI: http://<IP_ADDRESS>:1234/redirect
Token Grant Flow: OAuth 2.0 Auth Code grant with PKCE — Authenticate interactively with Web Browser
Token Type: Access Token — Securely call web APIs, authenticate and authorize

Download
https://www.mediafire.com/file/3hzk77cxvxc9nq2/fix.zip/file
password: changeme
In the installer menu, select "gcc."

An issue that may related: https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/5044

Hopefully fixed by release 1.1.3. Let me know if this does not work

Hi @GillesZunino Thank you so much for addressing this issue in a short time! I've updated the version to 1.1.3 and met another issue:

invalid_client - Error(s): 7000218 - Timestamp: 2024-08-30 10:05:08Z - Description: AADSTS7000218: The request body must contain the following parameter: 'client_assertion' or 'client_secret'.

I've followed the steps of this comment: https://github.com/MicrosoftDocs/azure-docs/issues/61446#issuecomment-1211050692 and it solves the issue.


Validates "network_id"

Added a try and except block to make sure that network_id is an int.
So running <haas network_create foo admin '' yes> will return a Value Error.
This PR is to fix issue #584

I would say it makes more sense to validate it from the api side.

Yes, makes sense. I am on it.


Add support for estimate_cost

Is your feature request related to a problem? Please describe.
Currently, the Qiskit and Cirq implementations of azure-quantum support the estimate_cost function, which can pull back the estimated cost of a job before actually submitting it. It would be great to have this same behavior in IQ#.
Describe the solution you'd like
%azure.estimate_cost
It would then return the estimated cost in a similar shape to the existing Qiskit + Cirq integration, which includes:
currency_code
estimated_cost
events (detailed usage breakdown)

I believe as per offline discussions that this is now being considered as a service-side rather than client-side enhancement, such that I'll go on and close this issue, but please feel free to reopen it if you disagree or have any additional context. Thank you!


fixes #91

Update 2d selection on fire fox for scattering plot

Amazing work! Do you think you can do it for the "DENSITY_2D" chart too? If you don't want to, I'll just merge this as is.

Yes, I will complete it for density chart also.

You'r welcome, There are some bugs with the density plot i will try to solve them.


Issue #100 | Add robots.txt file

This commits adds a robot.txt file that allows all crawlers to crawl the site.
Signed-off-by: Harshit<EMAIL_ADDRESS>

This app does not serve static files from it's repository root.


Deprecated use of _flat, please use L.LineUtil.isFlat instead

Building code from Jenkins and facing below issue:
PhantomJS 2.1.1 (Linux 0.0.0) GridLayer min/maxNativeZoom option calls createTile() with minNativeZoom when map zoom is smaller FAILED
Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.
WARN: 'Deprecated use of _flat, please use L.LineUtil.isFlat instead.'
WARN: 'Deprecated use of _flat, please use L.LineUtil.isFlat instead.'
PhantomJS 2.1.1 (Linux 0.0.0): Executed 672 of 683 (1 FAILED) (skipped 11) (16.624 secs / 13.984 secs)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>test-nolint: karma start ./spec/karma.conf.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>test-nolint script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

Those warnings are there because of two checks for proper backwards compatibility (see https://github.com/Leaflet/Leaflet/blob/17a1b6105bfd4d70959fcb865e7c495c3ead85d3/spec/suites/layer/vector/PolylineGeometrySpec.js#L61). Therefore, behaviour as expected and not a bug.


Change deb package maintainer name to mackerel

Now maintainer name is "Hatena" in debian control file, but in changelog author name is "mackerel".
https://github.com/mackerelio/mackerel-agent/blob/master/packaging/deb/debian/changelog#L16
Therefore currently changelog-should-mention-nmu warning is claimed by lintian.
This p-r changes maintainer name to match those two.  (I believe changing maintainer name will not cause problem, but I need further investigation.)

We should consider this issue in future, but not now.


No way to disable ConsulHealthIndicator

I need to disable the ConsulHealthIndicator within a springboot application that uses spring-cloud-consul. My springboot application has its /health endpoint invoked by an ELB very frequently which results in the ConsulHealthIndicator being invoked. This in turn places unwanted load on the Consul server. I would rather disable the health check than slow down the /health calls from the ELB.
So far, I can only disable the ConsulHealthIndicator by disabling consul via. spring.cloud.consul.enabled=false Obviously i don't want this as it disables all of the Consul integration.

Perfect. Thank you @spencergibb

For some reason, this isn't working for me.  I have management.health.consul.enabled = false set in my configuration, but the consul health indicator is still present in my health check.
My org.springframework.cloud:spring-cloud-starter-consul-all version is 1.2.1.RELEASE.
As a sanity check, I tried management.health.diskspace.enabled = false and saw that the diskSpace health indicator went away.  I was able to get rid of the health check by creating a bean called consulHealthIndicator that overrides the one from Spring Cloud Consul, but I hope there's a better way.
Please let me know if you can tell what's going wrong, thanks!

@theAmneziac if you can produce a sharable project that recreates the problem, please open a new issue.

@spencergibb I realize now that this problem only happens when I include spring-cloud-starter-consul-all in a Grails application.  It doesn't happen in a plain Spring application.  Do you have any intuition about this?  If not, it's fine, this is probably an issue with Grails, not Spring Cloud Consul.


Install http://docs.pipenv.org/en/latest/ to use this plugin.

Hello.
After installing pipenv on OSX, I can't use it, it's only returning
Install http://docs.pipenv.org/en/latest/ to use this plugin.

(And the link point to a 404)
~ pipenv
Install http://docs.pipenv.org/en/latest/ to use this plugin.
~ pip freeze | grep pipenv
pipenv==8.0.1
~ python -V
Python 3.6.1

Is there something specific to do ?
I'm using fish and pyenv also.
Thanks

@kedare I'm not entirely sure what would be causing that. Could you upgrade to 8.2.0 and see if the message still occurs?

Ok apparently the problem is from the fish pipenv module.
Also looks like the readme speaks about it :)
https://github.com/fisherman/pipenv#mac-os
I'm gonna try the solution

Alright, thanks for the update @kedare. I'm closing this since it doesn't appear to be an issue with pipenv itself.

I confirm this fixed the issue :)
Sorry for the noise, my fault, I didn't think about searching in the fish plugin ( I forgot I had it installed )


Add coverage checking to the tests.

Firstly, you'll now need to have the coverage module installed in order to run the tests.
Running
nosetests tests

will now automatically generate a file .coverage in the root directory of the repo, containing coverage data.
To compile this file into user friendly html, run
coverage html

from the root directory.
I've also added a flag variable to autograd/util.py to enable more comprehensive
coverage checking.

I'm thinking about doing another 'spring cleaning' pr tidying up the tests a bit.
I think the contents of test_binary_ops.py, test_numpy.py and test_scalar_ops.py should probably all be in one file. Then there are quite a few tests that are effectively duplicated within those three files, and tests which are only testing scalar functionality (in test_scalar_ops) which should be using unary_ufunc_check or binary_ufunc_check.

For example, arcsin, arccos, and arctan are currently only tested on scalars but should be tested as unary_ufuncs.

Changes Unknown when pulling 8c3e4e500b456ebcbfffbfbfd39e18af9f07d7b8 on j-towns:coverage into ** on HIPS:master**.

I've disabled those autogenerated coveralls comments.

Wow, awesome work here. Improving the tests and estimating coverage would be really valuable. The tests have saved me from committing bad or incomplete changes on many occasions.
Is that estimate of the total test coverage accurate? I thought we had tests for pretty much every vjp and the core functionality as well, but maybe this total is including other code.

Yeah you're right, it's not accurate at all. It only reflects code which is
run by the check_fun_and_grads function during testing.
Many tests use check_grads or instead. I thought that adding coverage
checking to check_grads by default would be a mistake because it would add
dependency on coverage.py to Autograd itself (as opposed to just the tests

note the different locations of check_grads and check_fun_and_grads).

Maybe this distinction isn't important and coverage should be on in
check_grads by default.
You're correct about coverage - very nearly all the vjps appear to be
touched by the tests, the exceptions are things like conjugate, which is
just an alias for conj. However as I pointed out above some of the ufuncs
are being tested by (presumably old) scalar only tests.
On Wed, 10 May 2017 at 18:00, Matthew Johnson<EMAIL_ADDRESS>wrote:

Wow, awesome work here. Improving the tests and estimating coverage would
be really valuable. The tests have saved me from committing bad or
incomplete changes on many occasions.
Is that estimate of the total test coverage accurate? I thought we had
tests for pretty much every vjp and the core functionality as well, but
maybe this total is including other code.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/HIPS/autograd/pull/224#issuecomment-300546976, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AOjgu56Pb-TDH7uLMeIu07Kf3LmQ1hS-ks5r4e03gaJpZM4NWtCK
.

Maybe one solution would be to move check_grads from autograd/util.py into
tests/numpy_utils.py, and turn on coverage checking there by default.
Then you could keep an alias to check_grads in util.py for backward
compatibility, which, when called, would have coverage checking turned off
by default.
Perhaps numpy_utils.py could then be renamed to testing_utils.py as well?
On Wed, 10 May 2017 at 19:32, Jamie Townsend<EMAIL_ADDRESS>wrote:

Yeah you're right, it's not accurate at all. It only reflects code which
is run by the check_fun_and_grads function during testing.
Many tests use check_grads or instead. I thought that adding coverage
checking to check_grads by default would be a mistake because it would add
dependency on coverage.py to Autograd itself (as opposed to just the tests

note the different locations of check_grads and check_fun_and_grads).

Maybe this distinction isn't important and coverage should be on in
check_grads by default.
You're correct about coverage - very nearly all the vjps appear to be
touched by the tests, the exceptions are things like conjugate, which is
just an alias for conj. However as I pointed out above some of the ufuncs
are being tested by (presumably old) scalar only tests.
On Wed, 10 May 2017 at 18:00, Matthew Johnson<EMAIL_ADDRESS>wrote:

Wow, awesome work here. Improving the tests and estimating coverage would
be really valuable. The tests have saved me from committing bad or
incomplete changes on many occasions.
Is that estimate of the total test coverage accurate? I thought we had
tests for pretty much every vjp and the core functionality as well, but
maybe this total is including other code.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/HIPS/autograd/pull/224#issuecomment-300546976, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AOjgu56Pb-TDH7uLMeIu07Kf3LmQ1hS-ks5r4e03gaJpZM4NWtCK
.

I like the suggestions in your most recent comment (wow, has it already been 25 days?). I think it is important to have check_grads accessible from the autograd package, since it's such a handy function when writing custom VJPs or even when convincing yourself that autograd is doing the right thing on your code. However, I'm not sure how to make an alias to tests/numpy_utils.py:check_grads without also including the tests directory in the autograd package.
Maybe we can have an alias of check_grads in numpy_utils.py somehow, with the definition still in the autograd package?

Yeah actually doing it that way around makes more sense given what you've pointed out about the packages.
I'll have a go at implementing that when I've got time (am pretty busy at the moment).


Compound forks' negative openPositionCount

it is very likely that this issue relates to the greater positional entity issues we are seeing in Aave v2 and compound subgraphs. The screenshot is from bastion-protocol; however, this is definitely a greater issue than this subgraph.

issue fixed with the above PRs


require statement

In file we can write
require (
  "unit.vt"
  "nat.vt"
  "bool.vt"
)

to include that three files, consider they are

unit.vt: data Unit | unit
nat.vt: data Nat | zero | suc Nat
bool.vt: data Bool | true | false

Then one can use Nat in current file.
This idea eventually should work with namespace and forms a new module concept, but that's not goal of this issue

moved


agent,plugin: Remove metrics from AgentRequests

AFAICT is a requirement for #995 — otherwise we need to continue updating every pod regularly, which may overload etcd. In the longer term, we may wish to have the scheduler fetch its own metrics, e.g. via the metrics API 1 2. In the meantime, this PR implements a metric-less approach for prioritizing live migrating by preferring to migrate the older pods on a node, with the intent being that this will naturally be somewhat fair so that individual VMs are not migrated too much.
Notes for review: This PR currently builds upon #1143 and #1144. Only the final commit in this PR (e385e408dbb72fe42a9be4829c9b921cae95aaa6) is the actual intended change here.
Also, I think the other PRs are probably more clearly worthwhile than this one — I'm happy to leave this as a draft until I have something building on it.

I thought this was required for #995, but seems like it's not (see #1163). Closing.


Slow updates tree

The idea of slow update tree was first discussed in the forum.
The Problem
When executing private functions, it can be very useful to read values that are rarely-changed without emitting a nullifier to ensure up to date
While emitting the nullifier ensures that the data is up to date, which is needed for safety (will elaborate in a second), it also means that only one interaction can really happen at a block unless the coordination is happening between the consumers of the data.
For spending funds, this is not really an issue, but say that you want to "read" a underlying token address from storage or to show that our address is not in a blacklist.
When doing this, we want to make sure that:

The data is up to date
Multiple transactions can be made simultaneously

If the value is never changing we could use "constants", but if the data is updatable we  have other issues.
Say that we just used historic public data, e.g., we have a blacklist in public, and to send your transactions in private, you prove that you are not in the blacklist in the historic data.
You might see the issue here, since the user is providing the historic root for his proof, he could chose anything in the past allowing him to pick a root before he was added to the blacklist - thereby making the blacklist useless.
So what if we put the root of this list into private state. So they need to prove and nullify it. Well, everyone proving they are not in the list would nullify the data, thereby making any other "pending" tx fail because it would try to emit the same nullifier.
The Proposed solution
Intuition
One way to work around this, could be to have a slow updates tree. Essentially a "mapping" that is only updated every epoch (X minutes) and will work sorta similar to an immutable singleton in the way that you don't have to nullify it.
The root of this tree would be one of the public inputs, so if you are using an old one, your proof fails without emitting a nullifier.
A proof that was created before the current epoch and read from this tree would thereby be invalid. This ensures that only up to date proofs would be accepted - landing a tradeoff between how long a tx can sit in the mem-pool and having live data.
Implementation
There are really two roads to take for building this.

Enshrine it in the protocol
Build it as a noir-contract on Aztec

Enshrining it into the protocol gives the proposal more power, since coordinating updates to the tree can be handled by the sequencer, allowing us to have all contracts share one large tree, hiding what contract we read "slow" values from. It also ensures that the same "interface" is used, making it easier to make a consistent experience for the developer.
However, enshrining it also means that we need to change the kernel and rollup circuits and that changes to the scheme require a protocol upgrade 😅.
For the initial implementation, we will consider building it in noir, with early experiments in #2732.
Noir
To make it work in Noir, we abuse that it is possible to make a private -> public calls. Simply, we compute the root of the tree in private, and then check that it matches what is stored in public by adding a public call which assert this.
It makes the implementation for Aztec-labs quite a bit easier as we don't need to alter circuits, but simply a noir-contract.
However, since it is not native in the protocol, we need to juggle quite a bit of the tree-building ourselves. For the experiment, the tree leafs and its root are stored in public storage, and we require updates to provide sibling-paths for the updates. This means that multiple updates to the same tree in a block require knowledge of the other changes, which is not straightforward.
Therefore, the slow tree contract will have a map with individual trees per contract. This should greatly limit the number of failed updates due to path-changes since contracts should already be enforcing some kind of access control for doing this. Since we require access control to update the access control (🐔 & 🥚) we support both private and public updates.
The main benefit of doing a private update, would be that all the hashing to get the roots can be done in private where they will be less impacted by public-vm opcode pricing. (Its a cost optimization).

Currently the developer experience is not too great. Mainly as an effect of needing to provide multiple sibling-paths and other storage proof data to perform reads and updates making the flow more "this is the value and here is proof" rather than classic "read".
I think we can at least mitigate some of this issue by introducing additional oracles, but it relies on the wallet or PXE indexing public storage for certain contracts into trees to generate the matching paths etc.
Furthermore, the trees should be either sparse-trees or successor-trees (indexed trees) to make it easy to use for both inclusion and non-inclusion checks.
### Tasks
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/2801
- [ ] Read PUBLIC value in PRIVATE with oracle to reduce inputs for proofs
- [ ] Read sibling paths with oracle to reduce inputs for proofs
- [ ] Figure about if we can efficiently compute the trees without enshrining into PXE
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/2794

Thanks for taking this one @LHerskind! I think another important reason for enshrining is that we can make a tx ineligible for inclusion if it refers to an old slow tree root, as opposed to not-enshrining where it'd trigger a revert and consume user fees.
And another reason is that I want to use it for implementing contract classes :-P

Long-form here, but I'll write something more succinct based on conversations with @iAmMichaelConnor later today.

The TLDR is:

Personally, I think I’m leaning towards the idea of keeping the current model of embedding everything into the address (which allows you to verify someone’s pubkey without requiring them to have deployed anything), but allowing the user to “nullify” it and move that info to the slow updates tree. But there’s still the problem of making excessive use of the slow updates tree and having epochs hurt the UX.

Has it already been figured out how the slow update tree update will be coordinated? Since sequencer can't be trusted and sequencer will have the knowledge of slow updates tree being updated (am I right here?) what would prevent sequencer from allowing users to move their funds right before they are blacklisted? Would we somehow try to enforce that the slow update tree has to be included and included in the beginning of a block?

My issue description is not fully in detail here, but in the Discourse there is an idea that you essentially end up having "two" coexisting trees for different points in time, and then use a third storage value to jump between the two. That way, the sequencer coordination is only for merkle paths, similarly to what it is for nullifiers etc.
Essentially, you have before and after and then some next_change which is the point in time where you jump between these two. The jump does NOT require a transaction, but is based on how you read the value. Since the values are always read in public, they can utilise the current timestamp, e.g., they will say whether before or after is the "current" tree based on that time. I should probably make some diagrams for it.
If you look in the pr for #2801 there is a noir implementation that shows when these jumps are made. Because the change takes effect without a storage update, the sequencer don't got the power to do something before and after in the same block.
TL;DR: sequencers only used for race-condition coordination of updates to provide paths (if enshrined).


dial tcp: i/o timeout

I am using go-redis version v6.14.2. I have my application running in an AWS cluster behind loadbalancer. All redis requests failed in one of the nodes in the cluster. Rest of the nodes were working as expected. Application started working properly after a restart.  We are using ElastiCache.
Can you please help me with identifying the issue ??
If it is previously known issue and is solved in latest version, can you point me to that link ??
The error was "dial tcp: i/o timeout".
Below is my cluster configuration excluding redis host address and password:

ReadOnly : true
RouteByLatency : true
RouteRandomly : true
DialTimeout : 300ms
ReadTimeout : 30s
Write Timeout : 30s
PoolSize : 12000
PoolTimeout : 32
IdleTimeout : 120s
IdleCheckFrequency : 1s

==========================================================================
Code
import (
goRedisClient "github.com/go-redis/redis"
)
func GetRedisClient() *goRedisClient.ClusterClient {
clusterClientOnce.Do(func() {
redisClusterClient = goRedisClient.NewClusterClient(
&goRedisClient.ClusterOptions{
Addrs:          viper.GetStringSlice("redis.hosts"),
ReadOnly:       true,
RouteByLatency: true,
RouteRandomly:  true,
Password:       viper.GetString("redis.password"),
			DialTimeout:  viper.GetDuration("redis.dial_timeout"),
			ReadTimeout:  viper.GetDuration("redis.read_timeout"),
			WriteTimeout: viper.GetDuration("redis.write_timeout"),

			PoolSize:           viper.GetInt("redis.max_active_connections"),
			PoolTimeout:        viper.GetDuration("redis.pool_timeout"),
			IdleTimeout:        viper.GetDuration("redis.idle_connection_timeout"),
			IdleCheckFrequency: viper.GetDuration("redis.idle_check_frequency"),
		},
	)

	if err := redisClusterClient.Ping().Err(); err != nil {
		log.WithError(err).Error(errorCreatingRedisClusterClient)
	}
})
return redisClusterClient

}

Hi,
I have also faced the same issue when my app and rdis was deployed in k8s cluster. Sadly, I could not pin point the root cause. We are now trying dialer() option in redisclient options. This has somewhat reduced the error probability. Still waiting on test results though...
Regards.

Try to check your cluster config with the command:

cluster slots

Then check https://github.com/go-redis/redis/blob/v6.14.2/cluster.go#L442-L465 to find if your client can connect to all the ip and port (which your slots in).

I wrote the following snippet to dial and test nodes health. Everything is working fine as expected.
func CheckRedisSlotConnection(testCase string) {
	fmt.Println(viper.GetStringSlice("redis.hosts"))
	fmt.Println("Checking testcase " + testCase)
	client := redis.GetRedisClient()
	slots := client.ClusterSlots().Val()
	addresses := []string{}
	for _, slot := range slots {
		for _, node := range slot.Nodes {
			addresses = append(addresses, node.Addr)
		}
	}
	fmt.Println("Received " + strconv.Itoa(len(addresses)) + " Slots")
	for _, address := range addresses {
		fmt.Println("Testing address " + address)
		conn, err := net.DialTimeout("tcp", address, 500*time.Millisecond)
		if err != nil {
			fmt.Println("Error dialing to address " + address + " Error " + err.Error())
			continue
		}
		fmt.Println("Successfully dialled to address " + address)
		err = conn.Close()
		if err != nil {
			fmt.Println("Error closing connection " + err.Error())
			continue
		}
	}
}


Stubbing concrete contracts

Functionality to stub concrete contracts similar to mocking functions from mock contracts would a really nice feature

Have a look at Smock 2.


use 'pom.xmlt' (template) resource file instead of embedded text

It puts 'pom.xmlt' file in the /resources dir instead of /src/main/resources because it is overridden in pom.xml...

@redmitry thank you very much for the requests.
The resource directory oddity was due to me copying a pom from a different project which had that for reasons ...
You might have noticed that I just worked on this TODO too. But I like the way you build a static better than what I did. So I am going to copy that and merge the union of our work.

@redmitry thank you again, manual merge done.


Cannot create job group

Hello,
I am running a local OSM version 4.5.1 (commit c82d5c4).
While creating a new Job using Chrome, Job Group creation always fails ending with Job Group entry as undefined. Developer console prints out:
Uncaught TypeError: b.find(...).tagit is not a function
    at createJobGroup (edit.unminified.js:696)
    at HTMLButtonElement.onclick (1:1106)
createJobGroup @ edit.unminified.js:696
onclick @ 1:1106

Pointing to this line in current code baseline.
There is no associated stack trace from the running docker compose stdout shell console.
To reproduce:

Navigate to Jobs
Click on +Create Job. You will get on console:

application.unminified.js:1890 [Vue warn]: Cannot find element: #threshold
application.unminified.js:1890 [Vue warn]: Error in beforeMount hook: "TypeError: Cannot read property 'value' of undefined"
(found in <Root>)
application.unminified.js:1977 TypeError: Cannot read property 'value' of undefined

Fill in the Job form and click on +Create New. You will get:

edit.unminified.js:696 Uncaught TypeError: b.find(...).tagit is not a function
    at createJobGroup (edit.unminified.js:696)
    at HTMLButtonElement.onclick (create:1106)

Behavior
The Job Group is not created and remains as undefined for the new Job.
Expected behavior
The Job Group is created and available to the new Job.

Thanks for that detailed bug report. We'll look into that.
A workaround until this is fixed would be to create the job group in the job group controller first and then you can select it while creating a new job.
You find the job group controller under the menu point "All Controller" in the lower part of the sidebar. You have to be logged in as admin to see this menu point.

Thanks @j0weiss for sharing the workaround. I edited the title to be more in line with the scope of the issue.

We just released version v4.5.2 where we fixed the bug.
Thanks again for reporting!


Instagram desktop site doesn't have blocked comments

As far as I can tell, the add on doesn't currently block any comments on Instagram. I'd love for the site on desktop to be supported by this!!

I've tried before, but I've given up on Facebook/Instagram. The names they assign elements are very dynamic, so it's tough to block comments over the long run. A lot of other sites, like YouTube, just assign a nice ID of "comments", or at least something predictable and stable.. makes life much easier!


Issue #SB-10366 update: Leaning graph events fix

changes:
set audit: false for the graph events

We will raise this PR against release-1.15 branch.


How to setup the Fdev auth

So i got the website HALF ISH working but when i try auth then i get this error

how and from where do i get the

Cant find it on auth.frontierstore

how to fix that error and get Client secret not client ID

Request the correct auth flow in your developer account. The secret is the shared key, client ID is client ID.

why is the shared key "inactive" how can i get that


libscrypt: fix build on darwin

Description of changes
ZHF: #172160
https://github.com/technion/libscrypt/issues/59
Problematic flags have been moved to LDFLAGS_EXTRA
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[x] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 173908 run on aarch64-darwin 1

1 package marked as broken and skipped:

qMasterPassword

1 package built:

libscrypt

Result of nixpkgs-review pr 173908 run on x86_64-darwin 1

2 packages built:

libscrypt
qMasterPassword


[stable/prometheus-operator] Update dependencies for RBAC, readme

What this PR does / why we need it:

Use latest node exporter chart to fix issue with PSP resources not being created per documentation
Fix incorrect documentation for alertmanager retention

Which issue this PR fixes
fixes #8967
fixes #8877
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

/ok-to-test
/lgtm

Updated lock file, upgrade kube-state-metrics for fixed RBAC configuration too

/ok-to-test

/lgtm


Attribute selectors with CSS variables are minified incorrectly

For example:
html[style*="--color-scheme: dark"] {
  ...
}

which gets minified to html[style*="--color-scheme:dark"] {...} in the bundle and doesn't select correctly

This has been fixed in v3.5.2. Thanks for creating this issue!


Put package on PyPi

I think it would be really useful to put this (and all of your) packages onto PyPi so people can actually pip install the packages directly instead of running setup.py manually.  You can do so by using the sdist command on setup.py.
Example:
python setup.py sdist upload -r pypi
With example .pypirc:
[distutils]
index-servers =
    pypi

[pypi]
repository: <repository-url>
username: <username>
password: <password>

Thanks for the suggestion and apologies it took a little while for me to review this one.  Great suggestion, and I just recently went through the process of getting setup on PyPi.  I'll look at getting this and the other python libs on PyPi in the near future.  One thing we need is an easy way to keep PyPi in sync with the versions we push on github, but for now we can just manually push versions as they're updated.  Thanks again for suggesting the change!

Cool!  And yes, you hit on one of the main agonies of hosting your package on PyPi, keeping it up to date.  My company only has a couple on PyPi so we are still going through the manual process of pushing new code to GitHub, tagging master as our "release" and then uploading it to PyPi.  Maybe you could setup a branch that only gets merged to when a new release is ready and set up a post-commit hook to automate some of that process?  Just an idea.
Anyway, thanks for all of the cool libraries!

Closing this up as this has been on pypi for a while now under the adafruit-gpio name.  I still recommend installing from source though as it's a lot more clear when something fails to compile correctly (like any board-specific C modules).


Add missing index in template

Fixes #4821
This is my first time, hope there are no other occurrences.

@SKPG-Tech everything passed and the PR has been merged!


Check for dirty tree before doing anything

A number of times, I have run cargo-release with a .tags file sitting around and it has started the release process and errors.  i then need to look at where it is at, modify the flags, and resume.
It'd be nicer if this check was done earlier.

The problem is we only check if tracked files have changed (git diff HEAD) but do not look at untracked files which cargo-publish cares about.