Error: undefinedVercel CLI 28.0.1

Hello, since 28.0.1 is live since yesterday, and my  CD with github action not working anymore since 28.0.1 I wonder the action need an update.
Do you have any idea beceause I can't use a custom version. Thanks :)
Run<EMAIL_ADDRESS>Creating GitHub deployment Deployment #629186761 created Deployment #629186761 status changed to "pending" Creating deployment with Vercel CLI Setting environment variables for Vercel CLI Starting deploy with Vercel CLI Error: undefinedVercel CLI 28.0.1 Retrieving project…

⚠ This issue has not seen any activity in the past 2 months so I'm marking it as stale. I'll close it if it doesn't see any activity in the coming week.


Add  AWSServiceRoleForVPCTransitGateway AWS Managed Role To Network Mgmt Role

In order for hive accounts to create VPC attachmetns to Transit Gateways in external accounts, the above AWS managed role is required.
Reference:
https://docs.aws.amazon.com/vpc/latest/tgw/tgw-service-linked-roles.html

ROSA Change Freeze exception approved, based on:
Merging this

Won't make any changes to stage or prod automatically
Will need to be deployed manually
Won't change installation at all; would only affect federated roles

/lgtm
Merging the PR and rolling the changes only to stage shards for now.


feat: add useWheel option

Details
Added useWheel to ConveyerOptions. The default value is true.
useWheel decides whether to use the mouse wheel input for same scroll direction.
If direction is horizontal and useWheel is true, the mouse wheel can move the Conveyer horizontally.
If direction is horizontal and useWheel is false, the Conveyer moves only by drag as same as before.
If direction is vertical and useWheel is true, the Conveyer moves by drag and mouse wheel as same as before.
If direction is vertical and useWheel is false, the Conveyer moves only by drag.
If you want to use it as the same Conveyer as before, set useWheel to true for vertical and false for horizontal.

The current implementation is whether or not to use the vertical mouse wheel for scrolling the conveyor.
But it is considered more appropriate to support option like "Whether to use the wheel input in a direction different from that of the conveyor".
And for that implementation, it need to handle horizontal mouse wheel in WheelInput of Axes.
Will close the PR until Axes supports that feature.


Fix wrong link in synchronization-functions.md

Fix SetEvent link pointing to ResetEvent page

@dimaver : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Extensions Marketplace won't connect

Issue Type: Performance Issue
Got a new Macbook Pro and installed vscode, and extensions marketplace is not available. There is a error message called:
"We cannot connect to the Extensions Marketplace at this time, please try again later." This is a personal machine with no proxy. Insiders mode works, however.
VS Code version: Code 1.52.1 (ea3859d4ba2f3e577a159bc91e3074c5d85c0523, 2020-12-16T16:30:02.420Z)
OS version: Darwin x64 20.2.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz (4 x 2300)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
2, 3, 2

Memory (System)
8.00GB (0.36GB free)

Process Argv
--crash-reporter-id f61cc233-0515-4f0d-91fa-791aa14f19fd

Screen Reader
no

VM
0%

Process Info
CPU %	Mem MB	   PID	Process
    6	    98	  3364	code main
    1	    41	  3367	   gpu-process
    0	    25	  3371	   utility
    0	   229	  3372	   window (Settings)
    0	    66	  3377	     extensionHost
   93	    90	  3378	   shared-process
    0	     0	  3421	     /bin/ps -ax -o pid=,ppid=,pcpu=,pmem=,command=
    1	    57	  3419	   window (Issue Reporter)

Workspace Info
;

Extensions: none

Console:

Network: (typing on extensions)

Console:

Network: (typing on extensions)

Shared Process:

View > Open View > Window, Shared

Shared Process:

View > Open View > Window, Shared


chore: fix cpe generation task

Example of earlier failure: https://github.com/anchore/syft/runs/18167378102#step:5:7

Attempting a run real quick, just to catch things before merging if something silly is wrong: https://github.com/anchore/syft/actions/runs/6692892787

https://github.com/anchore/syft/pull/2271 was opened by manually running the workflow as defined in this branch. It seems to have done what it was supposed to, so I will merge this PR.


[DRAFT] Replace go-bindata with //go:embed and upgrade to go 1.18

This is the code from https://github.com/hound-search/hound/pull/430
Needed in a branch within this repo to merge as fork didn't have permissions to push merge conflict fixes

replaced by https://github.com/hound-search/hound/pull/460


Confusion over the use of stackSize and stackPtr in Thread class constructor

The Thread class constructor based on thread_entry_t takes stackSize and stackPtr arguments which default to 0 if omitted. The stackSize (which becomes m_stackSize) is then used in the Thread::start() methods of the Windows, FreeRTOS and Zephyr ports (curiously, the Pthreads port ignores this argument entirely and just creates the thread with libpthread defaults). (There also appear to be some differences in which ports create the thread in the Thread::start() method vs the Thread::init() method, but that's a separate topic.)
Now, looking the TCP transport code which creates a thread to listen for connections using the above-mentioned Thread constructor here, there is absolutely no place where it could possibly be setting the m_stackSize value to anything other than the 0 that the constructor uses by default. That in turn means that the TCP transport's listening thread would be attempted to be created with a 0-sized stack (which maybe works in the Pthreads case since it is not used).
So, the questions are:

How is the TCP transport constructor supposed to influence the stack size of its listening thread (even if the stack is static, a valid non-zero size needs to be used)?
Is the TCP transport working just by luck and/or only on Pthreads (I realize this transport is marked "mostly for testing," but I'm failing to understand how it could be working even for the most basic testing cases on anything other than Pthreads)?

Thank you! 🙏

Hi, i will look on your question asap ;)

One more nudge @Hadatko?

Hi @berendo , sorry that it took so much time. I was busy with other work. Current tcp implementation is only for Linux/Mac where pthreads doesn't need stack attribute, so transport layer doesn't count with it.

Here are some information regarding to init:


Missing LIS Ids, Causing Votes Scanner to Fail

Throwing this out while I continue to debug, but it looks like the LIS id is missing for the following Senators:
Vote could not find legislator "S389"!
Vote could not find legislator "S391"!
Vote could not find legislator "S385"!
Vote could not find legislator "S386"!
Vote could not find legislator "S387"!
Vote could not find legislator "S388"!
Vote could not find legislator "S390"!

This is output from my own script which takes the votes data and applies it to members.  Votes for the House have a bioguide_id and votes for the Senate have a lis_id.  These are failing because they cannot be found.

We have a script for this -- see the commit. Fixed. Thanks.

Thank you, sir.


Multiple fonts in a fontFamily does not work

We cannot set multiple fonts for a fontFamily definition in our tailwind because on tw() render  it concatenates with   (space) instead of concatenating with , (comma), so for :
// tailwind.config.js
{
    fontFamily: {
      body: ["Inter", "sans-serif"],
    }
}

we got :
/* once` transpiled on runtime : ... */
font-family: "Inter sans-serif";

and "Inter sans-serif" isnt an existing font.

Yep, noticed the same thing.
Looks like it's joined incorrectly: https://github.com/arlyon/stailwc/blob/master/crates/tailwind-parse/src/eval/plugin.rs#L241

Thanks for the report. Fixing now!


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v2.6.35 to before v4.9.290",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f931551bafe1f10ded7f5282e2aa162c267a2e5d",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=3f57c3f67fd93b4da86aeffea1ca32c484d054ad"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "f931551bafe1f10ded7f5282e2aa162c267a2e5d",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "3f57c3f67fd93b4da86aeffea1ca32c484d054ad",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v4.9.290 by commit 3f57c3f67fd93b4da86aeffea1ca32c484d054ad, it was introduced in version v2.6.35 by commit f931551bafe1f10ded7f5282e2aa162c267a2e5d. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1001943


Bug - no checking if event is null before accessing to title on completer-editor

issue resolved in RP


Activities

An activity is a group of recursive events.
TODO:

I would cool it a project, not an activity.


Image component not rendering image from url properly

The Image component is not rendering the image properly from the URL
https://mav-fb.imgix.net/https%3A%2F%2Fcdn.hiremav.com%2F404.png?ixlib=rb-3.0.0&w=100&h=100&mask=ellipse&fit=focalpoint&fm=png32&s=e4ef2680df3f5f8e54548a827c5f0c44
From the onError I got the message Failed to load

React Native version:
  React Native Environment Info:
    System:
      OS: macOS 10.14.4
      CPU: (4) x64 Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz
      Memory: 53.52 MB / 8.00 GB
      Shell: 5.3 - /bin/zsh
    Binaries:
      Node: 12.3.1 - /usr/local/bin/node
      Yarn: 1.16.0 - /usr/local/bin/yarn
      npm: 6.9.0 - /usr/local/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
      Android SDK:
        API Levels: 26, 28
        Build Tools: 28.0.3
        System Images: android-26 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom
    IDEs:
      Android Studio: 3.2 AI-181.55<IP_ADDRESS>14246
      Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.8.3 => 16.8.3
      react-native: 0.59.9 => 0.59.9
    npmGlobalPackages:
      react-native-cli: 2.0.1

Steps To Reproduce
Add the following component:
<Image  resizeMode="contain" source={{uri: 'https://mav-fb.imgix.net/https%3A%2F%2Fcdn.hiremav.com%2F404.png?ixlib=rb-3.0.0&w=100&h=100&mask=ellipse&fit=focalpoint&fm=png32&s=e4ef2680df3f5f8e54548a827c5f0c44'}} />

Describe what you expected to happen:
Render the image properly without errors
Snack, code example, or link to a repository:
https://snack.expo.io/@mbackermann/image-error

@mbackermann You need to provide a cleaner url. No weird symbols :1234:

Actually this is not the problem. I realized that although the URL is showing the image, it returns HTTP Status 403. This is probably the problem.

@mbackermann If you load the image, you will notice that the problem is that the server is returning an http 403 state.

It was the status code from the HTTP request that was returning 403.


added code for kth smallest element in bst

Fixes #2089
Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have created a helpful and easy to understand README.md
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works

kindly review my pr and merge it @Ayush7614 @ravikr126 @Saurabh4626

@SnehaAgarwal361 delete the other file

Done, kindly merge it.


elixir typo - stray parenthesis

This fixes a documentation typo in PR #568

Thank you for spotting this!  Merged.

This fixes a documentation typo in PR #568


Error during 'annotation' bootstrap locally

During local bootstrap of annotation (with docker-compose) we have this:
annotation             | 09-Dec-22 10:33:03 - [INFO] - uvicorn.error - (server.py).serve(84) - Started server process [9]
annotation             | INFO:     Waiting for application startup.
annotation             | 09-Dec-22 10:33:03 - [INFO] - uvicorn.error - (on.py).startup(45) - Waiting for application startup.
annotation             | 09-Dec-22 10:33:13 - [WARNING] - kafka.conn - (conn.py).dns_lookup(1527) - DNS lookup failed for kafka:9092, exception was [Errno -3] Temporary failure in name
resolution. Is your advertised.listeners (called advertised.host.name before Kafka 9) correct and resolvable?
annotation             | 09-Dec-22 10:33:13 - [ERROR] - kafka.conn - (conn.py)._dns_lookup(315) - DNS lookup failed for kafka:9092 (AddressFamily.AF_UNSPEC)
annotation             | 09-Dec-22 10:33:13 - [INFO] - kafka.conn - (conn.py).check_version(1205) - Probing node bootstrap-0 broker version
annotation             | 09-Dec-22 10:33:23 - [WARNING] - kafka.conn - (conn.py).dns_lookup(1527) - DNS lookup failed for kafka:9092, exception was [Errno -3] Temporary failure in name
resolution. Is your advertised.listeners (called advertised.host.name before Kafka 9) correct and resolvable?
annotation             | 09-Dec-22 10:33:23 - [ERROR] - kafka.conn - (conn.py)._dns_lookup(315) - DNS lookup failed for kafka:9092 (AddressFamily.AF_UNSPEC)
annotation             | 09-Dec-22 10:33:23 - [WARNING] - app.logger - (main.py)._init_search_annotation_producer(957) - Error occurred during kafka producer creating: NoBrokersAvailab
le
annotation             | INFO:     Application startup complete.
The app tries to find kafka, but doesn't find it

Duplicate: #460


Make queries anchorable

Resolves #50
This will be a new major release since it changes slightly what is returned from the category and quantity queries, from simply an array of samples to:
type ResponseType = {
  samples: Sample[], // category or quantity sample
  deletedSamples: DeletedSample[],
  newAnchor: string
}

and also adds (non-breaking) the anchor parameter as an optional input to the query:
const firstRes = await queryQuantitySamples(HKQuantityTypeIdentifier.stepCount, {
  limit: 2,
})

const nextRes = await queryQuantitySamples(HKQuantityTypeIdentifier.stepCount, {
  limit: 2,
  anchor: firstRes.newAnchor,
})

I've given this a quick run in the example app - maybe you could have a run on it as well @ha3 and see if you have any feedback before we merge this?

@robertherber thank you for the effort! I'd been naively hoping that native side just could return the diff between the previous and the current call. But now I understand the API more, I see that it is impossible to do this without persisting the anchor...
So, for an app that needs to sync HealthKit data back to its own API; I guess the below approach could be used:
const anchor = storage.getItem('anchor');
let options;

if (!anchor) {
  // this is either the first time we are making the call to HealthKit or storage data is somehow wiped out.
  options = {
    ...
  };
} else {
  options = {
    anchor,
    to: new Date()
  };
}

const res = await queryQuantitySamples(HKQuantityTypeIdentifier.stepCount, options);

storage.setItem('anchor', res.anchor);

I will test it with the way I described above tomorrow and will let you know about the results. If you have any feedback regarding the approach, please let me know!

@robertherber I thought that we could compose all options with anchor, like in a paginated REST API; but if not, maybe we could throw an error if limit is not used along with anchor in dev mode?
In that case, I think your approach would be the way to go.  Only downside I can think of is that, if there is more data than the limit, there will be more trips between native and JS sides than using to: new Date(). But I'm not sure if it is a serious problem.

@ha3 I do believe we can compose all options. Although I'm assuming it's important that an anchor is used together with the exact same filters as specified in it's original query.
So if passing a to filter (to: new Date() in your example) I would assume it's important that the exact same date is passed when using the anchor at a later stage. But maybe I misunderstood the example.. :)

@ha3 Yeah, and I think this is both a good and bad thing. The good thing is that it seems it can be used for both paginating a query as well as fetching changes since last a query was run. I find even the Apple docs a bit unclear about the ins and outs of anchors, including what happens if an anchor is passed to a query with different parameters than the initial query.
Regarding the crash - I’m fairly sure this is how it’s been working before as well. It seems to be by design by Apple - crashing the app when requesting data you haven’t asked for access to. Although when a user denies permission it won’t crash, but instead return no data. Personally as a developer I’d prefer a warning to a crash, but I think it’s out of scope of this library to try to mitigate for this.

@robertherber sorry for the late response but we conducted some tests that I think will provide new insights.

About the crash, I phrased the status of the user as unauthorized; but I what I meant was that authorization prompt is presented to the user but they didn't give permission for the identifier. Previous behavior for this case was that API returns an empty array. But now it crashes. I added a comment for the concerning line that causes this.
Anchor seems to be corresponding to a particular object. I guess we can think of it as some hash of the object's uuid. This means that using dynamic filter options works as expected.
There was a problem with limit + anchor approach you recommended. It starts sending from the first entry but stops near end–in our case it halted at fourteen days ago. I have no idea why; but supplying from and to options solves it. Here's a working example:

/**
  * This is important because HealthKit API seems only accepting dates initialized with a date string (i.e. 2020-06-10)
*/
const formatDate = (date) => {
  const pad = (n: number) => {
    return n < 10 ? '0' + n : n;
  };

  return (
    date.getFullYear() + '-' + pad(date.getMonth() + 1) + '-' + pad(date.getDate())
  );
};

const addDays = (date, days) => {
  date.setDate(date.getDate() + days);
  return date;
};

const getRecursiveData = async ({ limit = 10, anchor }) => {
  if (!anchor) {
    anchor = (await storage.getItem('key')) ?? undefined;
  }

  const to = new Date(formatDate(addDays(new Date(), 1)));
  const from = addDays(to, -365);

  const { deletedSamples, samples, newAnchor } = await HealthKit.queryQuantitySamples(
    HKQuantityTypeIdentifier.activeEnergyBurned,
    {
      limit,
      from,
      to,
      anchor
    }
  );

  if (samples.length > 0) {
    // persist create
  }

  if (deletedSamples.length > 0) {
    // persist delete
  }

  const hasNext = samples.length >= limit;

  if (!hasNext) {
    if (newAnchor && newAnchor !== anchor) {
      await storage.setItem('key', newAnchor);
    }
    return;
  }

  return getRecursiveData({ anchor: newAnchor, limit });
};

@ha3 Good catch on the nil anchors, thanks!
Regarding the dates I don't see anything odd when using non-date timestamps. What have you experienced?
I'm guessing the 2 week default limit is done with performance in mind. I've made a slight change to default to from: new Date(0) when a limit is specified, does that make sense and work on your data?

@robertherber we tested with the latest state of the PR; all the issues, including the one concerning timestamps are solved. As far as our tests are concerned, this PR is good to go! Thanks again!

Released in 6.0.0!


299 Show Supported Rules in CLI

Closes #299
TODO:

[x] Add integration test
[x] Clean up code around API Client

Codecov Report

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

@@           Coverage Diff           @@
##           master     #324   +/-   ##
=======================================
  Coverage   90.11%   90.11%
=======================================
  Files          36       36
  Lines         334      334
  Branches       18       18
=======================================
  Hits          301      301
  Misses         29       29
  Partials        4        4

Flag
Coverage Δ

#webui
90.11% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

@fmueller thanks for your early feedback, I find it super useful. I will address the comments in next commits

Ready.
@fmueller , could you please check once you'll have a moment?

👍


File Manager - collections

Use horizontal tabs to allow a user to select between the folder structure browser/Collections/Bookmarks in one narrow tall column
Ie: use the entire vertical column to view one of the tabs at a time
something like the attached image

added at commit 401de0bf723cad588e63b5b9b46b7db87893b869

deployed to test, version 2.1.10

love it


Hey sorry, I was busy running behind a release and deployment the past week.

          Hey sorry, I was busy running behind a release and deployment the past week.

Here's a summary:

[ ] Yeah, I only prefer using a real device to test my apps. And it's USB debugging latched to my PC with a cable, not wireless ADB.
[ ] The device I used was Samsung Galaxy S22.
[ ] Normal debugging breakpoints hit easily. No issues at all. XAML won't update
[ ] Works fine with Windows, Fails sometimes random with Android real device
[ ] Tried other devices other than my Galaxy S22, Same issue randomly. I believe it's originating from VS, not the smartphone
[ ] This is mostly prominent when building after updating Visual Studio MAUI workload for first time

Originally posted by @sangeethnandakumar in https://github.com/dotnet/maui/issues/16267#issuecomment-1666448073

Please use the relevant issues in the dotnet/maui repo.


VSTest 17.0.0 with /EnableCodeCoverage skips some DLLs in .coverage file

Description
We have Azure DevOps agent deployed on own machine. After updating VS2019 to VS2022 we discovered change in code coverage reports. Pipeline is configured to build ~20 solutions and run tests for all of them.
Steps to reproduce
Set test platform version to Visual Studio 2019 and run pipeline, then set test platform to Latest and run pipeline again. Compare produced coverage files for each run.
Expected behavior
List of files in each raport should be this same.
Actual behavior
Some files (DLLs) are not included in reports.
Example

Environment
Azure DevOps Agent v.2.195.0
Microsoft (R) Test Execution Command Line Tool Version 16.11.0
Microsoft (R) Test Execution Command Line Tool Version 17.0.0
Windows Server 2012 R2

Few questions:

Do you have .NET core or .NET framework projects?
Do you have any C++/CLI code?

Could you please send your .coverage file? If some data you don't want to be public you can generate new feedback here: https://developercommunity.visualstudio.com/
Could you please try to rerun your scenario using this latest package: https://dev.azure.com/dnceng/public/_packaging?_a=package&feed=test-tools&package=Microsoft.TestPlatform&protocolType=NuGet&version=17.2.0-preview-20211210-01&view=overview ?

Closing as no data provided. Please reopen if needed.


remove codecov!

disabling codecov but not removing.
we need to redo the test suite for graphiql anyways, and the LSP server coverage info is useful, however I tend to use it more for adding coverage with coverage codecov gutter extensions.
also i sometimes feel like the codecov diff data is innacurate  anyways, probably because of misconfifguration
also clutter. this shrouds the CLA bot and changeset bot comments which are more important
we have many practical ways to display coverage as needed when adding coverage, and perhaps we will want to show coverage diffs in comments again

tried using codespaces for this and it was a lil funky 👀


Vagrant Update base box to 128.

Got Ian commit and apply some changes.
Fix https://github.com/cilium/packer-ci-build/issues/116

This change is

test-me-please

Coverage decreased (-0.02%) to 43.031% when pulling 936ffdf41c4e5aec3d20ab0a005c412682b340a6 on eloycoto:Vagrant128 into 3c116d7d6eb52d6624601d91d5b575c1daa41b01 on cilium:master.

Got hit by the same issue with the latest ubuntu-next.

test-me-please

test-me-please

The unit tests passed fine, but Coveralls failed:
make[1]: Leaving directory `/home/travis/gopath/src/github.com/cilium/cilium'
Bad response status from coveralls: 422
{"message":"Couldn't find a repository matching this job.","error":true}
travis_time:end:09af9f78:start=1550507575566829998,finish=1550508001092656763,duration=425525826765
The command "./.travis/build.sh" exited with 1.

Unit test failures are unrelated - the PR is only for updating the VM version, which the Travis CI does not run in. Given that build passed with the VM version being updated, the fix is self-evident, so am merging.


Discussion: the road to 0.3

In 0.3, I'm planning to continue my sweep of various widget APIs with a focus on:

refactoring them
documenting them
expanding them to cover as much of the upstream API as possible

I don't yet know how much work will be done in 0.3, but at least these are planned:

normal popups
modal popups
trees
collapsing headers

Previous release discussions:

0.2: https://github.com/Gekkio/imgui-rs/issues/238
0.1: https://github.com/Gekkio/imgui-rs/issues/167

I just want to give some feedback that the migration to 0.2 was very easy thanks:

Useful deprecation notes in the documentation
Up to date examples for integration with gfx (and friends)
Please keep up the good work for 0.3.

The one thing I found a bit disappointing was that I was no longer able to query the size of the application window from the ui object that is passed around everywhere. I ended up having to pass that data around to a couple places where I wanted to keep popups centered on screen.

0.3.0 is now out, but most of the planned things never happened. Maybe in some future release :slightly_smiling_face:
0.4 discussion:
https://github.com/Gekkio/imgui-rs/issues/301


Entities

Adds entities, thanks to https://github.com/GlowstoneMC/Glowstone/pull/282. I also added monster egg support, but it only spawns pigs right now.

Maybe we could do something like this: (I'm not sure the API but basic idea)
	case PIG_METADATA:
		GlowPig pig = new GlowPig(target.getLocation());
		break;
	case SHEEP_METADATA:
		GlowSheep sheep = new GlowSheep(target.getLocation()):
		//Then we could make it spawn colours randomly
		break;
}

@mastercoms ^

Maybe, instead we could make it so you do
Entity entity = new Entity(entityId, location);

This way we can then send an add entity packet with the entityId. This will then spawn that mob.
@mastercoms


Batch scrobbling support

Scrobbles can be submitted to the Last.fm API in batches (for example adding whole albums listened to in the past, or for migrating data to a new account). Depends on #2 to make sense.

Committed


chore(backend): Remove pocket-ic

Motivation
Remove unnecessary finary file pocket-ic from repository.
Changes

Remove pocket-ic

Tests
Still running backend tests.

@peterpeterparker please review

LGTM, thanks
Should we add it to .gitignore?

It's already there. It was probably pushed before I added it there.


Tesla Landing page

I will make Try my best to make clone of Tesla landing page with the use Html, Css and js , this will help me to increase the skills of my frontend skills.

Hey @Rayman-Sodhi ,
I want to work on this issue under @GSSOC'22 ,

@ayush-sleeping all the best!!
happy contributing🚀

@ayush-sleeping all the best!!
happy contributing🚀

Hey maintainer , Because of some urgent Problem, I unable to puch PR .
My project is completed, As soon as I will reach home , I will push PR . ☺


RE-Fix Install-module cmdlet example on site

Rollbacking change from #195  . Turns out I had an old/wrong version that had the -module parameter for install-module.
-name is the right one according to MS docs: https://technet.microsoft.com/en-us/library/dn807162.aspx

Kudos to @todthomson for spotting this one


WIP: Annotations / data layers concept

WIP, opening for an early days feedback.

Closing in favor of https://github.com/grafana/scenes/pull/325 https://github.com/grafana/scenes/pull/328


Apple Silicon: error: failed to legalize operation 'mhlo.pad'

Description
When following the MNIST example from flax (https://github.com/google/flax/tree/main/examples/mnist/), the following error occurs when using the latest jax-metal plugin installed as described at https://developer.apple.com/metal/jax/ :
jaxlib.xla_extension.XlaRuntimeError: UNKNOWN: /Users/max/jax-metal/lib/python3.11/site-packages/flax/linen/pooling.py:69:6: error: failed to legalize operation 'mhlo.pad'
  y = lax.reduce_window(inputs, init, reduce_fn, dims, strides, padding)

What jax/jaxlib version are you using?
jax 0.4.11, jaxlib v0.4.10
Which accelerator(s) are you using?
MPS
Additional system info
Python 3.11, macOS 13.4, Mac Mini M2 Pro
NVIDIA GPU info
No response

@kulinseth @shuhand0

@mlaves is there more to the error? In particular, I think more details about the operation should be printed?

I get the same error, with almost identical specs. Except python 3.9, and Apple Mac M2 Pro.
File ~/mambaforge/envs/mrff/lib/python3.9/site-packages/jax/_src/dispatch.py:465, in backend_compile(backend, module, options, host_callbacks)
    460   return backend.compile(built_c, compile_options=options,
    461                          host_callbacks=host_callbacks)
    462 # Some backends don't have `host_callbacks` option yet
    463 # TODO(sharadmv): remove this fallback when all backends allow `compile`
    464 # to take in `host_callbacks`
--> 465 return backend.compile(built_c, compile_options=options)
XlaRuntimeError: UNKNOWN: io.py:164:0: error: failed to legalize operation 'mhlo.pad'

Thanks for sending the bug report. JAX-Metal plugin do not support pad with non-zero interior_padding. We will look into expanding the  coverage and update here.

I am running a pretrained model, I wonder if there is a way to change my inputs/tokenisation to try and add interior_padding to circumvent this issue?

@BradBalderson It will be impossible to say without more details on how the operator is used in the model. If it is applied to one of the model inputs, perhaps.

Ah OK, I will see if it is due to the inputs. Thanks for the fast reply and feedback @hawkinsp and @shuhand0

BTW, you can implement interior padding with edge padding, if the interior padding is from your user code.
For example, to pad the innermost dimension, you do this:

Reshape the input to add a new inner dimension of size 1.
Pad that new dimension to size 1 + interior_padding
Reshape back to the original number of dimensions, flattening the new inner dimension into the original inner dimension
Truncate interior_padding elements off the end.

But... it might just be better to wait for our colleagues from Apple to fix the plugin :-)

I encountered the same bug by trying to calculate the grad of a loss function for a physics informed NN problem in a mac M1.
Jax version: 0.4.20
Bellow is the slacktrace. I am trying to construct a minimum reproducible problem, I will update with a new comment but the problem is very complex and difficult to recreate a more simple version of it.
{
	"name": "XlaRuntimeError",
	"message": "UNKNOWN: /var/folders/l6/g1b2w7y10rg8qzc142j02b240000gn/T/ipykernel_73686/1915339887.py:2:47: error: failed to legalize operation 'mhlo.pad'
/var/folders/l6/g1b2w7y10rg8qzc142j02b240000gn/T/ipykernel_73686/1915339887.py:2:47: note: see current operation: %99 = \"mhlo.pad\"(%98, %1) {edge_padding_high = dense<0> : tensor<2xi64>, edge_padding_low = dense<[0, -1]> : tensor<2xi64>, interior_padding = dense<0> : tensor<2xi64>} : (tensor<1024x2xf32>, tensor<f32>) -> tensor<1024x1xf32>
",
	"stack": "---------------------------------------------------------------------------
JaxStackTraceBeforeTransformation         Traceback (most recent call last)
File <frozen runpy>:198, in _run_module_as_main()

File <frozen runpy>:88, in _run_code()

File ~/miniconda3/envs/metal/lib/python3.11/site-packages/ipykernel_launcher.py:17
     15 from ipykernel import kernelapp as app
---> 17 app.launch_new_instance()

File ~/miniconda3/envs/metal/lib/python3.11/site-packages/traitlets/config/application.py:1077, in launch_instance()
   1076 app.initialize(argv)
-> 1077 app.start()

File ~/miniconda3/envs/metal/lib/python3.11/site-packages/ipykernel/kernelapp.py:701, in start()
    700 try:
--> 701     self.io_loop.start()
    702 except KeyboardInterrupt:

File ~/miniconda3/envs/metal/lib/python3.11/site-packages/tornado/platform/asyncio.py:195, in start()
    194 def start(self) -> None:
--> 195     self.asyncio_loop.run_forever()

File ~/miniconda3/envs/metal/lib/python3.11/asyncio/base_events.py:607, in run_forever()
    606 while True:
--> 607     self._run_once()
    608     if self._stopping:

File ~/miniconda3/envs/metal/lib/python3.11/asyncio/base_events.py:1922, in _run_once()
   1921     else:
-> 1922         handle._run()
   1923 handle = None

File ~/miniconda3/envs/metal/lib/python3.11/asyncio/events.py:80, in _run()
     79 try:
---> 80     self._context.run(self._callback, *self._args)
     81 except (SystemExit, KeyboardInterrupt):

File ~/miniconda3/envs/metal/lib/python3.11/site-packages/ipykernel/kernelbase.py:534, in dispatch_queue()
    533 try:
--> 534     await self.process_one()
    535 except Exception:

File ~/miniconda3/envs/metal/lib/python3.11/site-packages/ipykernel/kernelbase.py:523, in process_one()
    522         return
--> 523 await dispatch(*args)

File ~/miniconda3/envs/metal/lib/python3.11/site-packages/ipykernel/kernelbase.py:429, in dispatch_shell()
    428     if inspect.isawaitable(result):
--> 429         await result
    430 except Exception:

File ~/miniconda3/envs/metal/lib/python3.11/site-packages/ipykernel/kernelbase.py:767, in execute_request()
    766 if inspect.isawaitable(reply_content):
--> 767     reply_content = await reply_content
    769 # Flush output before sending the reply.

File ~/miniconda3/envs/metal/lib/python3.11/site-packages/ipykernel/ipkernel.py:429, in do_execute()
    428 if accepts_params[\"cell_id\"]:
--> 429     res = shell.run_cell(
    430         code,
    431         store_history=store_history,
    432         silent=silent,
    433         cell_id=cell_id,
    434     )
    435 else:

File ~/miniconda3/envs/metal/lib/python3.11/site-packages/ipykernel/zmqshell.py:549, in run_cell()
    548 self._last_traceback = None
--> 549 return super().run_cell(*args, **kwargs)

File ~/miniconda3/envs/metal/lib/python3.11/site-packages/IPython/core/interactiveshell.py:3051, in run_cell()
   3050 try:
-> 3051     result = self._run_cell(
   3052         raw_cell, store_history, silent, shell_futures, cell_id
   3053     )
   3054 finally:

File ~/miniconda3/envs/metal/lib/python3.11/site-packages/IPython/core/interactiveshell.py:3106, in _run_cell()
   3105 try:
-> 3106     result = runner(coro)
   3107 except BaseException as e:

File ~/miniconda3/envs/metal/lib/python3.11/site-packages/IPython/core/async_helpers.py:129, in _pseudo_sync_runner()
    128 try:
--> 129     coro.send(None)
    130 except StopIteration as exc:

File ~/miniconda3/envs/metal/lib/python3.11/site-packages/IPython/core/interactiveshell.py:3311, in run_cell_async()
   3308 interactivity = \"none\" if silent else self.ast_node_interactivity
-> 3311 has_raised = await self.run_ast_nodes(code_ast.body, cell_name,
   3312        interactivity=interactivity, compiler=compiler, result=result)
   3314 self.last_execution_succeeded = not has_raised

File ~/miniconda3/envs/metal/lib/python3.11/site-packages/IPython/core/interactiveshell.py:3493, in run_ast_nodes()
   3492     asy = compare(code)
-> 3493 if await self.run_code(code, result, async_=asy):
   3494     return True

File ~/miniconda3/envs/metal/lib/python3.11/site-packages/IPython/core/interactiveshell.py:3553, in run_code()
   3552     else:
-> 3553         exec(code_obj, self.user_global_ns, self.user_ns)
   3554 finally:
   3555     # Reset our crash handler in place

Cell In[288], line 1
----> 1 jax.grad(los1)(params)

Cell In[286], line 1, in los1()
----> 1 def los1(params): return jnp.mean(los_physics1(params,tt,xx)**2)

Cell In[243], line 15, in los_physics1()
     13 rho_V_x_x = lambda t,x: jax.grad(lambda t,x: jnp.sum(rho(t,x)*Vx_x(t,x)),1)(t,x)
---> 15 return rho_t(tc,xc)+rho_V_x_x(tc,xc)

Cell In[243], line 13, in los_physics1.<locals>.<lambda>()
     12 #rho_V_x_t = lambda t,x: jax.grad(lambda t,x: jnp.sum(rho(t,x)*Vx_x(t,x)),0)(t,x)
---> 13 rho_V_x_x = lambda t,x: jax.grad(lambda t,x: jnp.sum(rho(t,x)*Vx_x(t,x)),1)(t,x)
     15 return rho_t(tc,xc)+rho_V_x_x(tc,xc)

Cell In[243], line 13, in los_physics1.<locals>.<lambda>()
     12 #rho_V_x_t = lambda t,x: jax.grad(lambda t,x: jnp.sum(rho(t,x)*Vx_x(t,x)),0)(t,x)
---> 13 rho_V_x_x = lambda t,x: jax.grad(lambda t,x: jnp.sum(rho(t,x)*Vx_x(t,x)),1)(t,x)
     15 return rho_t(tc,xc)+rho_V_x_x(tc,xc)

Cell In[243], line 10, in los_physics1.<locals>.<lambda>()
      9 rho_t= lambda t,x: jax.grad(lambda t,x: jnp.sum(rho(t,x)),0)(t,x)
---> 10 Vx_x= lambda t,x: jax.grad(lambda t,x: jnp.sum(Vx(t,x)),1)(t,x)
     12 #rho_V_x_t = lambda t,x: jax.grad(lambda t,x: jnp.sum(rho(t,x)*Vx_x(t,x)),0)(t,x)

Cell In[243], line 10, in los_physics1.<locals>.<lambda>()
      9 rho_t= lambda t,x: jax.grad(lambda t,x: jnp.sum(rho(t,x)),0)(t,x)
---> 10 Vx_x= lambda t,x: jax.grad(lambda t,x: jnp.sum(Vx(t,x)),1)(t,x)
     12 #rho_V_x_t = lambda t,x: jax.grad(lambda t,x: jnp.sum(rho(t,x)*Vx_x(t,x)),0)(t,x)

Cell In[243], line 6, in los_physics1.<locals>.<lambda>()
      5 rho=lambda t,x: NN(params,t,x)[0]
----> 6 Vx=lambda t,x: NN(params,t,x)[1]
      7 #p=lambda t,x: NN(params,t,x)[2]

JaxStackTraceBeforeTransformation: jaxlib.xla_extension.XlaRuntimeError: UNKNOWN: /var/folders/l6/g1b2w7y10rg8qzc142j02b240000gn/T/ipykernel_73686/1915339887.py:2:47: error: failed to legalize operation 'mhlo.pad'
/var/folders/l6/g1b2w7y10rg8qzc142j02b240000gn/T/ipykernel_73686/1915339887.py:2:47: note: see current operation: %99 = \"mhlo.pad\"(%98, %1) {edge_padding_high = dense<0> : tensor<2xi64>, edge_padding_low = dense<[0, -1]> : tensor<2xi64>, interior_padding = dense<0> : tensor<2xi64>} : (tensor<1024x2xf32>, tensor<f32>) -> tensor<1024x1xf32>

The preceding stack trace is the source of the JAX operation that, once transformed by JAX, triggered the following exception.

--------------------

The above exception was the direct cause of the following exception:

XlaRuntimeError                           Traceback (most recent call last)
Cell In[288], line 1
----> 1 jax.grad(los1)(params)

    [... skipping hidden 21 frame]

File ~/miniconda3/envs/metal/lib/python3.11/site-packages/jax/_src/compiler.py:255, in backend_compile(backend, module, options, host_callbacks)
    250   return backend.compile(built_c, compile_options=options,
    251                          host_callbacks=host_callbacks)
    252 # Some backends don't have `host_callbacks` option yet
    253 # TODO(sharadmv): remove this fallback when all backends allow `compile`
    254 # to take in `host_callbacks`
--> 255 return backend.compile(built_c, compile_options=options)

XlaRuntimeError: UNKNOWN: /var/folders/l6/g1b2w7y10rg8qzc142j02b240000gn/T/ipykernel_73686/1915339887.py:2:47: error: failed to legalize operation 'mhlo.pad'
/var/folders/l6/g1b2w7y10rg8qzc142j02b240000gn/T/ipykernel_73686/1915339887.py:2:47: note: see current operation: %99 = \"mhlo.pad\"(%98, %1) {edge_padding_high = dense<0> : tensor<2xi64>, edge_padding_low = dense<[0, -1]> : tensor<2xi64>, interior_padding = dense<0> : tensor<2xi64>} : (tensor<1024x2xf32>, tensor<f32>) -> tensor<1024x1xf32>
"
}

Hello - I'm getting this error when running the following, very simple operation
import jax.numpy as jnp
jnp.cumprod(jnp.arange(10))

jax.errors.SimplifiedTraceback: For simplicity, JAX has removed its internal frames from the traceback of the following exception. Set JAX_TRACEBACK_FILTERING=off to include these.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/martin/miniconda3/envs/jax-metal/lib/python3.10/site-packages/jax/_src/numpy/reductions.py", line 657, in cumulative_reduction
    return _cumulative_reduction(a, _ensure_optional_axes(axis), dtype, out)
jaxlib.xla_extension.XlaRuntimeError: UNKNOWN: <stdin>:1:0: error: failed to legalize operation 'mhlo.pad'
<stdin>:1:0: note: called from
<stdin>:1:0: note: see current operation: %43 = "mhlo.pad"(%42, %1) {edge_padding_high = dense<1> : tensor<1xi64>, edge_padding_low = dense<0> : tensor<1xi64>, interior_padding = dense<1> : tensor<1xi64>} : (tensor<1xsi32>, tensor<si32>) -> tensor<2xsi32>

My env
>>> jax.print_environment_info()
jax:    0.4.20
jaxlib: 0.4.20
numpy:  1.26.4
python: 3.10.13 (main, Sep 11 2023, 08:16:02) [Clang 14.0.6 ]
jax.devices (1 total, 1 local): [METAL(id=0)]
process_count: 1

Would be really cool if someone could fix this, as it makes jax-metal pretty much unusable for me :(

For the  pad with interior_padding, the fix will be in the upcoming  jax-metal release and work in 14.4 OS.

@shuhand0 is this fix part of the macOS 14.4 rc yet? can't find it in release notes.

The fix is in jax-metal 0.0.6. Some output from running  flax/examples/mnist:
python main.py --workdir=/tmp/mnist --config=configs/default.py \
--config.learning_rate=0.05 --config.num_epochs=5
I0312 14:30:01.288698<PHONE_NUMBER> xla_bridge.py:660] Unable to initialize backend 'cuda':
I0312 14:30:01.288793<PHONE_NUMBER> xla_bridge.py:660] Unable to initialize backend 'rocm': module 'jaxlib.xla_extension' has no attribute 'GpuAllocatorConfig'
I0312 14:30:01.290362<PHONE_NUMBER> xla_bridge.py:660] Unable to initialize backend 'tpu': INTERNAL: Failed to open libtpu.so: dlopen(libtpu.so, 0x0001): tried: 'libtpu.so' (no such file), '/System/Volumes/Preboot/Cryptexes/OSlibtpu.so' (no such file), '/Users/shuhan/miniconda3/envs/test/bin/../lib/libtpu.so' (no such file), '/usr/lib/libtpu.so' (no such file, not in dyld cache), 'libtpu.so' (no such file), '/usr/local/lib/libtpu.so' (no such file), '/usr/lib/libtpu.so' (no such file, not in dyld cache)
W0312 14:30:01.290431<PHONE_NUMBER> xla_bridge.py:758] Platform 'METAL' is experimental and not all JAX functionality may be correctly supported!
2024-03-12 14:30:01.290494: W pjrt_plugin/src/mps_client.cc:563] WARNING: JAX Apple GPU support is experimental and not all JAX functionality is correctly supported!
Metal device set to: Apple M1 Max

systemMemory: 64.00 GB
maxCacheSize: 24.00 GB

I0312 14:30:01.301946<PHONE_NUMBER> main.py:50] JAX process: 0 / 1
I0312 14:30:01.302008<PHONE_NUMBER> main.py:51] JAX local devices: [METAL(id=0)]
I0312 14:30:01.302042<PHONE_NUMBER> local.py:45] Setting task status: process_index: 0, process_count: 1
I0312 14:30:01.302149<PHONE_NUMBER> local.py:50] Created artifact workdir of type ArtifactType.DIRECTORY and value /tmp/mnist.
I0312 14:30:01.302522<PHONE_NUMBER> dataset_info.py:358] Load dataset info from /Users/shuhan/tensorflow_datasets/mnist/3.0.1
I0312 14:30:01.303414<PHONE_NUMBER> dataset_info.py:411] Field info.citation from disk and from code do not match. Keeping the one from code.
I0312 14:30:01.303492<PHONE_NUMBER> dataset_info.py:411] Field info.splits from disk and from code do not match. Keeping the one from code.
I0312 14:30:01.303527<PHONE_NUMBER> dataset_info.py:411] Field info.module_name from disk and from code do not match. Keeping the one from code.
I0312 14:30:01.303578<PHONE_NUMBER> dataset_builder.py:351] Reusing dataset mnist (/Users/shuhan/tensorflow_datasets/mnist/3.0.1)
I0312 14:30:01.303609<PHONE_NUMBER> logging_logger.py:35] Constructing tf.data.Dataset mnist for split train, from /Users/shuhan/tensorflow_datasets/mnist/3.0.1
WARNING:tensorflow:From /Users/shuhan/miniconda3/envs/test/lib/python3.9/site-packages/tensorflow_datasets/core/dataset_builder.py:622: get_single_element (from tensorflow.python.data.experimental.ops.get_single_element) is deprecated and will be removed in a future version.
Instructions for updating:
Use `tf.data.Dataset.get_single_element()`.
W0312 14:30:01.332822<PHONE_NUMBER> deprecation.py:50] From /Users/shuhan/miniconda3/envs/test/lib/python3.9/site-packages/tensorflow_datasets/core/dataset_builder.py:622: get_single_element (from tensorflow.python.data.experimental.ops.get_single_element) is deprecated and will be removed in a future version.
Instructions for updating:
Use `tf.data.Dataset.get_single_element()`.
I0312 14:30:01.966295<PHONE_NUMBER> logging_logger.py:35] Constructing tf.data.Dataset mnist for split test, from /Users/shuhan/tensorflow_datasets/mnist/3.0.1
I0312 14:30:07.488775<PHONE_NUMBER> train.py:146] epoch:  1, train_loss: 0.2369, train_accuracy: 93.05, test_loss: 0.0590, test_accuracy: 98.07
I0312 14:30:10.687863<PHONE_NUMBER> train.py:146] epoch:  2, train_loss: 0.0611, train_accuracy: 98.11, test_loss: 0.0547, test_accuracy: 98.17
I0312 14:30:13.719958<PHONE_NUMBER> train.py:146] epoch:  3, train_loss: 0.0423, train_accuracy: 98.68, test_loss: 0.0330, test_accuracy: 98.73
I0312 14:30:16.748282<PHONE_NUMBER> train.py:146] epoch:  4, train_loss: 0.0308, train_accuracy: 99.00, test_loss: 0.0302, test_accuracy: 99.04
I0312 14:30:19.781277<PHONE_NUMBER> train.py:146] epoch:  5, train_loss: 0.0250, train_accuracy: 99.21, test_loss: 0.0306, test_accuracy: 99.03


Added environment variable to spire-agent to inject node name

Introduce injecting node name into spire agent instead of calling kubelet on localhost

What does this change? MY_NODE_NAME is just an environment variable. Whats using it?

oh. here we go:
https://github.com/spiffe/spire/blob/main/pkg/agent/plugin/workloadattestor/k8s/k8s.go#L42
does openshift not set the hostname on the pod to the hosts hostname like vanilla k8s on a net=host pod?

oh... its not hostname related, but how the agent talks to kubelet... default if unset is:
https://github.com/spiffe/spire/blob/main/pkg/agent/plugin/workloadattestor/k8s/k8s.go#L519-L522 <IP_ADDRESS>
so, depending on how the hosts firewall is setup, changing it to hostname could be a breaking change....
we should probably make it setable but still default to to the existing behavior for now...

oh... its not hostname related, but how the agent talks to kubelet... default if unset is: https://github.com/spiffe/spire/blob/main/pkg/agent/plugin/workloadattestor/k8s/k8s.go#L519-L522 <IP_ADDRESS>
so, depending on how the hosts firewall is setup, changing it to hostname could be a breaking change....
we should probably make it setable but still default to to the existing behavior for now...

Ive run into this issue before where the spire agent was not able to make the DNS request because of firewall issues. I agree with making it setable.

So, that leaves discussion around it being a potential breaking change left....
Does openshift not allow <IP_ADDRESS> to kubelet out of the box? Trying to figure out how to get a good default, or at least some logic in here for it without breaking existing folks.

So, that leaves discussion around it being a potential breaking change left....
Does openshift not allow <IP_ADDRESS> to kubelet out of the box? Trying to figure out how to get a good default, or at least some logic in here for it without breaking existing folks.

I think a simple bool like nodeNameFromSpec default to false should do it. The new section can be gated on the bool being set.

Easiest would be to enable a new "env" value where the end user can define their own environment variables. It would be the default in the set of openshift values but would remain as prior logic elsewhere unless they would want to opt in

Yeah. but I'm thinking it may be useful outside of openshift....
maybe a value like spire-agent.kubelet.contactByHostname true/false, default it to false everywhere but forced true if global.openshift=true? there ever a reason to use <IP_ADDRESS> still with openshift?

@kfox1111 The reason for the original approach is that it follows the same pattern used by the csi-driver chart
https://github.com/spiffe/helm-charts-hardened/blob/main/charts/spire/charts/spiffe-csi-driver/templates/daemonset.yaml#L50

@kfox1111 The reason for the original approach is that it follows the same pattern used by the csi-driver chart
https://github.com/spiffe/helm-charts-hardened/blob/main/charts/spire/charts/spiffe-csi-driver/templates/daemonset.yaml#L50

Hmm.... I think the usage there is slightly different though. its used as a unique name, but it isn't contacted over tcp, just unix sockets. so won't have the dns/firewall issues that tcp to kubelet would have with the proposed change.

I'll test this tomorrow on my test cluster, to see if there is a breaking change at all. I think this might just work with backwards compatibility.
In the end spec.nodeName should be the same as the value currently retrieved I guess.

I'll test this tomorrow on my test cluster, to see if there is a breaking change at all. I think this might just work with backwards compatibility.
In the end spec.nodeName should be the same as the value currently retrieved I guess.

Totally depends on the firewall on the host, so you cant test them all. I do have some hosts I think it will break on. I have some pretty tight firewalls.

And there's this bit of logic:
https://github.com/spiffe/spire/blob/main/pkg/agent/plugin/workloadattestor/k8s/k8s.go#L471-L496
that is otherwise inaccessible I think.
no, I think it has to be optional rather then always just set.

And there's this bit of logic: https://github.com/spiffe/spire/blob/main/pkg/agent/plugin/workloadattestor/k8s/k8s.go#L471-L496 that is otherwise inaccessible I think.
no, I think it has to be optional rather then always just set.

What approach should we use? the env or the nodeNameFromSpec? Personally, im favoring the env approach

when you say env, do you mean, adding an extraEnv setting to https://github.com/spiffe/helm-charts-hardened/blob/main/charts/spire/charts/spire-agent/values.yaml and then setting it via values?

when you say env, do you mean, adding an extraEnv setting to https://github.com/spiffe/helm-charts-hardened/blob/main/charts/spire/charts/spire-agent/values.yaml and then setting it via values?

Yup exactly

IMO, we should have extraEnv for that chart anyway, but don't currently it looks like. So, one way or another we probably should add that part.

extraEnv works for me.

K. lets go with that  for now, and can revisit usability improvements later?

@kfox1111 Should be updated to not change version of charts. Also did not change how the extraEnvVars are being injected as charts will uniformly be refactored later on


Clojure REPL is not bootstrapped

Hello folks!
I was investigating the possibility of have a double repl in a unique boot session and I saw your project. It looks like you were able to achieve this at some point but at the moment this project only bootstraps a cljs repl on port 5710.
Is there a direction I can take in order to fix that?
Thanks and keep up the good work!

Ok my bad, there is a typo in the project (or in the README), the port for the clojure nRepl is 5600

Probably a typo in the readme! Those ports sound right.
On 27 April 2016 17:57:19 BST, Andrea Richiardi<EMAIL_ADDRESS>wrote:

Ok my bad, there is a typo in the project (or in the README), the port
for the clojure nRepl is 5600

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/juxt/edge/issues/3#issuecomment-215147535

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Also, if you end your frontend task with (target :dir #{"target/dev"}) you are actually serving the files, just dumping them, is it the intended behavior?

What do you mean by bootstrapping the clojure repl?
On 27 April 2016 18:03:43 BST, Andrea Richiardi<EMAIL_ADDRESS>wrote:

Also, if you end your frontend task with (target :dir #{"target/dev"}) you are actually serving the files, just dumping
them, is it the intended behavior?

You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/juxt/edge/issues/3#issuecomment-215149398

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Ok no there is just a typo in the Readme, I am going to close this ok?


Improve performance reports

Differences less than 10 seconds seem to happen quite regularly just due to random variations in GitHub Actions, so don't report performance changes if the difference is less than 10 seconds. We're only really interested in major improvements or regressions here (the variations will be too big for anything more precise), and major improvements or regressions will generally manifest themselves in differences >10 seconds.
Clarify that it's mypy that got faster/slower, not the package we're running mypy on :-)

Thanks, this looks good! Agreed that we're only going to be able to detect really large shifts. That said, I'd like to hold off a week or two before merging, I'm finding it interesting to see how much noise there is.

This has some big conflicts now -- are you still interested in this/should I rebase? :)

I feel like I see noisy output from the performance report fairly regularly and I basically trained myself to ignore it.

Yeah, I agree that there have been PRs where we can be confident that <10s speedups were real, because they were very consistent in the mypy_primer reports. However I feel like I've seen more PRs with random noise from the performance reports, and I think those can be pretty confusing to new contributors (especially at typeshed, where it's pretty unlikely that something will have a significant performance impact unless somebody's adding a massive Union somewhere).
So I guess I can see it both ways? Maybe the ideal would be if the artifact contained a complete performance report, but the comment posted on PRs filtered out any differences <10s. That would be more complex to implement, of course.
Whatever the case, I do think it would be good to clarify that it's the typechecking of these projects that's getting faster/slower — not sure the wording is ideal at the moment 😄

I think those can be pretty confusing to new contributors (especially at typeshed, where it's pretty unlikely that something will have a significant performance impact

IMO we should disable performance reports in typeshed, maybe with a command-line flag to mypy_primer? We don't really care if one package becomes slightly slower, as long as it is reasonably fast overall. This is different in mypy, because changes in mypy affect all/most packages, and also pile up unlike improvements to different packages.

unless somebody's adding a massive Union somewhere).

Mypy handles big unions reasonably fast in most practical cases. There is a fast path that skips the bottleneck, and it has been expanded to cover pretty much anything that comes up in practice.

Mypy handles big unions reasonably fast in most practical cases. There is a fast path that skips the bottleneck, and it has been expanded to cover pretty much anything that comes up in practice.

Hmm, well, every typeshed sync over at mypy at the moment we religiously cherry-pick a commit to revert a change I made to typeshed a while back that allegedly caused a large performance regression for mypy due to the use of a big union: https://github.com/python/mypy/blob/e14cddbe31c9437502acef022dca376a25d0b50d/misc/sync-typeshed.py#L183
See e.g. the third commit in https://github.com/python/mypy/pull/15165

Consensus seems it's too noisy, so let's up the threshold to 10s (like this PR does), and see how we feel about noise?
I've definitely caused huge perf regressions with typeshed changes, so I think there's value to it in typeshed if the number can be believable.
I agree that it makes sense to target wording at infrequent contributors, maybe something like "in a single noisy sample, checking was 1.14x slower"
re the sum literal change: Could be worth trying out again? I've lost track of what it was trying to solve though and I haven't yet spotted what is undesirable in mypy's current behaviour

Apparently I was wrong about big unions :)
They used to be really broken. Specifically, there was a nested for loop that did n^2 iterations for a union of n members, so with some AWS related stubs with a union of 200 strings, it took a few minutes to type-check a very short file. But I didn't realize this isn't the only union slowness bug.

Cool I'll update this PR based on the consensus here!


Hack 2315

Related issues
(put links to related issues here)
Short description and why it's useful
(describe in a few words what is this Pull Request changing and why it's useful)
Screenshots of visual changes before/after (if there are any)
(if you made any changes in the UI layer please provide before/after screenshots)
Screenshot of passed e2e tests (if you are using our standard setup as a backend)
(run yarn test:e2e and paste the results. If you are not using our standard backend setup or demo.vuestorefront.io you can ommit this step)
Upgrade Notes and Changelog

[x] No upgrade steps required (100% backward compatibility)
[ ] I've updated the Upgrade notes and Changelog on how to port existing VS sites with this new feature

Contribution and currently important rules acceptance

[x] I read and followed contribution rules
[x] I read the TypeScript Action Plan and adjusted my PR according to it
[x] I read about Vue Storefront Modules and I am aware that every new feature should be a module

Not sure why You've removed the zeroPrice support? @filrak @MarcoGrecoBitbull. I think it's a pretty useful feature and we should keep it. However, it's not a main reason of the issue with this Yoga training product (the key reason there is the product options)


Minor: Add usecase to comments in LogicalPlan::recompute_schema

Which issue does this PR close?
Rationale for this change
As part of the review https://github.com/apache/datafusion/pull/10410 @yyy1000 had a good question https://github.com/apache/datafusion/pull/10410#discussion_r1594990402
Adding some additional explanation I think will help make this clearer
What changes are included in this PR?
Add doc comments

Are these changes tested?
by CI doc checks

Are there any user-facing changes?
More docs

Thanks for the review @Jefffrey  and @yyy1000


Update oracle-database-backup-azure-backup.md

Remove the extraneous use-case of restoring individual disks and focus on the primary use-case of restoring and recovering an entire VM with all onboard databases

@cro27

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Side traces

I am really happy to discover this project! I am also interested in writing code that specifically exploits the strengths of LuaJIT. I find your example on the README very powerful.
There is one optimization challenge on my mind that I think we share: how to prevent unwanted side-traces. I have written a little bit about this over at luajit/luajit#208 and had some success with optimizations - but not really nailed the issue closed.
Here is an illustration of how it seems to affect luafun. Consider this example program that is based on the README but with multiple operations:
require("fun")()
local n = 100
print(reduce(operator.add, 0, map(function(x) return x^2 end, range(n)))) -- first
print(reduce(operator.add, 0, map(function(x) return x^2 end, range(n)))) -- second

The first call does indeed compile down to a tight loop of around 10 instructions. However, the second call compiles down to around 62 instructions - even though it is exactly the same code! The difference is that the second call is compiling to a side trace within the reduce() subroutine and on each iteration it re-enters the root trace and repeats all of the loop invariant code. So you end up with the first call compiling very tight while the subsequent ones are less efficient. There is a cumulative effect too: each call will create a new side-trace, and the side traces will be chained together, and each link in the chain will add around 9 more instructions.
Just wondering: are you already aware of this issue? If not then you may be able to solve it in a neat way using the tips from @corsix in luajit/luajit#208. If you are already aware of this I would be very interested in your view e.g. if you already have some recommendations that you make to users to explain the best usage and generally set expectations.
Sadly it seems like the simplest workaround would be to avoid programming in a functional style :-) because the problem only arises when many different pieces of code are all executing the same loop statement (for, while, etc) in the source code. If you would write for ... end every time then you have no problem because each for bytecode will have a separate trace complex.

(One "magical" solution to give each call a separate root trace might be for reduce() to internally use the debug API to inspect the stack and determine where it is being called from. Then you could use the specialize() function from luajit/luajit#208 to make a table providing each call site with a separate copy of the reduce subroutine. This is a kludge but it might work and I cannot immediately think of an elegant alternative.)

Could not resist continuing this line of investigation a little bit. I made an empirical test case that repeatedly (100x) runs this same snippet of code (10M iterations) and uses the x86 Performance Monitoring Unit to measure how many instructions are executed per iteration. On each of the 100 runs the snippet is loaded with loadstring() to simulate being 100 separate calls in a large program (rather than the same call being made 100 times.)
Code and results for 100 iterations is here: https://gist.github.com/lukego/5c64368bdfdcf7ffcc4dc067fc630182
Here is the summary as I see it:

First call takes 9 instructions. Trace with a loop.
Second call takes 63 instructions. Side-trace without a loop.
Calls 3..92 each take 3 more instructions that the previous one. Side-traces are forming a chain. Ends up with 333 instructions for trace 92.
Calls 93..100 each take 865 instructions. The JIT has given up at this point and fallen back to the interpreter.

Quite an undertaking to understand and optimize code with a tracing JIT!
Solution will be to find a way to give each call a separate root trace. Then they should each take only 9 instructions like the first one.

Could not resist continuing this line of investigation a little bit. I made an empirical test case that repeatedly (100x) runs this same snippet of code (10M iterations) and uses the x86 Performance Monitoring Unit to measure how many instructions are executed per iteration. On each of the 100 runs the snippet is loaded with loadstring() to simulate being 100 separate calls in a large program (rather than the same call being made 100 times.)
Code and results for 100 iterations is here: https://gist.github.com/lukego/5c64368bdfdcf7ffcc4dc067fc630182
Here is the summary as I see it:

First call takes 9 instructions. Trace with a loop.
Second call takes 63 instructions. Side-trace without a loop.
Calls 3..92 each take 3 more instructions that the previous one. Side-traces are forming a chain. Ends up with 333 instructions for trace 92.
Calls 93..100 each take 865 instructions. The JIT has given up at this point and fallen back to the interpreter.

Quite an undertaking to understand and optimize code with a tracing JIT!
Solution will be to find a way to give each call a separate root trace. Then they should each take only 9 instructions like the first one.


Add a Managed Identity example

Is your feature request related to a problem? Please describe.
Support for authentication using Manage Identities was added in #114, but the documentation was note updated with any examples on how to use this. On the surface it would appear that you simply pass in a DefaultAzureCredential to the TokenCredential property, however this does not work out of the box for me.
Given a Startup.cs that looks like:
public override void Configure(IFunctionsHostBuilder builder)
{
    IConfigurationRoot config =
        new ConfigurationBuilder()
            .SetBasePath(Directory.GetCurrentDirectory())
            .AddJsonFile("local.settings.json", optional: true, reloadOnChange: true)
            .AddEnvironmentVariables()
            .Build();

    DefaultAzureCredential credential = new DefaultAzureCredential();

    builder.Services.AddCosmosRepository(options =>
    {
        options.CosmosConnectionString = config["Cosmos:ConnectionString"];
        options.DatabaseId = config["Cosmos:DatabaseId"];
        options.ContainerPerItemType = true;
        options.TokenCredential = credential;

        options.ContainerBuilder.Configure<DeviceTwinUpdate>(
            containerOptions =>
                containerOptions
                    .WithContainer("DeviceTwinUpdates")
                    // TODO: Configure Partition Key
        );

        options.ContainerBuilder.Configure<DeviceTelemetry>(
            containerOptions =>
                containerOptions
                    .WithContainer("DeviceTelemetry")
                    // TODO: Configure Partition Key
        );
    });
}

and a Function1.cs that looks like:
private readonly IRepository<DeviceTwinUpdate> _deviceTwinUpdateRepository;
private readonly IRepository<DeviceTelemetry> _deviceTelemetryRepository;

public Function1(IRepositoryFactory factory, CosmosClient cosmosClient)
{
    _deviceTwinUpdateRepository = factory.RepositoryOf<DeviceTwinUpdate>();
    _deviceTelemetryRepository = factory.RepositoryOf<DeviceTelemetry>();
}

[FunctionName("Function1")]
public async Task<IActionResult> Run(
    [HttpTrigger(AuthorizationLevel.Function, "get", "post", Route = null)] HttpRequest req,
    ILogger log)
{
    try
    {
        var twin = await _deviceTwinUpdateRepository.GetAsync((a) => a.Id.Equals("321"));
        var telemetry = await _deviceTelemetryRepository.GetAsync((a) => a.Id.Equals("123"));
    }
    catch (Exception ex)
    {
        var t = "";
    }

    return new OkObjectResult("Success");
}

where both models directly inherits from Item
public class DeviceTwinUpdate : Item
{
}

public class DeviceTelemetry : Item
{
}

I expect to be able to retrieve data successfully.
However, I encounter the following error "Invalid URI: The URI scheme is not valid.", the stack trace is:
at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
at System.Uri..ctor(String uriString)
at Microsoft.Azure.Cosmos.CosmosClient..ctor(String accountEndpoint, TokenCredential tokenCredential, CosmosClientOptions clientOptions)
at Microsoft.Azure.CosmosRepository.Providers.DefaultCosmosClientProvider.GetCosmoClient()
at System.Lazy`1.ViaFactory(LazyThreadSafetyMode mode)
at System.Lazy`1.ExecutionAndPublication(LazyHelper executionAndPublication, Boolean useDefaultConstructor)
at System.Lazy`1.CreateValue()
at System.Lazy`1.get_Value()
at Microsoft.Azure.CosmosRepository.Providers.DefaultCosmosClientProvider.UseClientAsync[T](Func`2 consume)
at Microsoft.Azure.CosmosRepository.Services.DefaultCosmosContainerService.GetContainerAsync[TItem](Boolean forceContainerSync)
at Microsoft.Azure.CosmosRepository.Providers.DefaultCosmosContainerProvider`1.<>c__DisplayClass1_0.<<-ctor>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---

I have isolated the error to be something with my DefaultAzureCredential that I pass to TokenCredential. I am running this inside Visual Studio 2019 which I am signed into with my Azure Account and this account is selected in the Azure Service Authentication section of my settings.
If I remove the setting of options.TokenCredential then my call succeeds. I have investigated the properties available for the DefaultAzureCredentialOptions parameter of DefaultAzureCredentials but none look particularly applicable or relevant for my use case.
Describe the solution you'd like
As outlined above there needs to be better guidance on how to use Managed Identities with this package.
Describe alternatives you've considered

I have managed to access data using the standard CosmosClient class from the C# SDK using a connection string.
I have also reviewed all of the samples in this repo and there is no example of using Managed Identity.
There is a guide here that outlines how to use Managed Identities with the standard library, but I'd much rather use this package as opposed to rolling my own.

Additional context
None

I'll pick this issue up @IEvangelist .Thanks for the opportunity and providing such a great library!

Hey @IEvangelist @BeigeBadger sound's great, look forward to seeing your PR, thanks for taking the time to contribute.


Added support for retrieving a Fieldhand record as a string

The #dump method on a Fieldhand::Record returns the item as a string in
its original format.

@mudge I've addressed your comments, and added support for Unicode characters


Update README.md

Added overarching goals (why do it, how easy it is).
Added feature "receive crypto payments".
Fixed some typos.

Incorrect goals.


Release/v4.0.6

READY FOR REVIEW
Summary

#365

Review By (Date)

Soonish

Criticality

3

Review Tasks
Setup tasks and/or behavior to test

Check the preview and the code diff

Front End Validation

[ ] Is the markup using the appropriate semantic tags and passes HTML validation?
[ ] Cross-browser testing has been performed?
[ ] Automated accessibility scans performed?
[ ] Manual accessibility tests performed?
[ ] Design is approved by @ user?

Backend / Functional Validation
Code

[ ] Are the naming conventions following our standards?
[ ] Does the code have sufficient inline comments?
[ ] Is there anything in this code that would be hidden or hard to discover through the UI?
[ ] Are there any code smells?
[ ] Are tests provided? eg (unit, behat, or codeception)

Code security

[ ] Are all forms properly sanitized?
[ ] Any obvious security flaws or new areas for attack?

General

[ ] Is there anything included in this PR that is not related to the problem it is trying to solve?
[ ] Is the approach to the problem appropriate?

Affected Projects or Products

Does this PR impact any particular projects, products, or modules?

Associated Issues and/or People

JIRA ticket(s)
Other PRs
Any other contextual information that might be helpful (e.g., description of a bug that this PR fixes, new functionality that it adds, etc.)
Anyone who should be notified? (@mention them here)

Resources

AMP Tool
Accessibility Manual Test Script
HTML Validator
Browserstack and link to Browserstack Credentials

@forrestglick Prepping a release for the Source Sans 3 and Source Serif 4 font update that is in dev already. Please let us know when you'd like us to push this to production. Thanks!

FYI @forrestglick is running Diffy comparison (no rush Forrest 😄 ). We shall wait.

@forrestglick ran Diffy spot check across the site and confirm that this is ok to go live. Thanks Forrest! 🎉


Break of root & selector

PR https://github.com/thysultan/stylis/commit/cd6750d8d91b2e79ff8a935acc9a0620885e2830 support the feature that not convert & when at root. But this breaks the usage case that create a help util to be nest case:
const sampleUtilStyle = `& a { color: red; }`;  // Just a sample

// This can be reused in both root and nest case for origin:
const rootStyle = `${sampleUtilStyle}`; // since `&` at root is not valid in css spec which will be break
const nestStyle = `.cls { ${sampleUtilStyle} }`;

I'm not sure support nesting CSS spec in stylis is a good idea since we use stylis is to handle the case that not support nest css.
ref issue: https://github.com/ant-design/ant-design/issues/50533

I have encountered a similar issue and hope to get a definite answer.
Thanks 🙏🏻

It's not clear to me how it broke. Please include a repro that involves calling stylis APIs

4.3.3
https://stackblitz.com/edit/react-sxn6wd?file=package.json,demo.tsx

4.3.2
https://stackblitz.com/edit/react-sxn6wd-kuzwkb?file=package.json,demo.tsx

Note that & is not invalid in CSS, it represents the current scoping root if it's not used in a nested rule.
Tbh, it feels to me that you were relying on a very implicit pattern that relied on implementation details of the previous Stylis versions removing those root &. It wasn't a well-defined behavior.

Note that & is not invalid in CSS...

& is to be follow parent selector in prev version. I'm not sure escape it as & in root is a good way. As above mentioned, stylis is the CSS Preprocessor which help to convert nest style into flatten and fill prefix for browser compatible. So keep the & in root to support nest case is not what it should do since it will be unclear of the & definition.
a {
  &:hover { // should this keep as `&` to trade as native nest css?
    color: red;
  }
}

Should be:
a:hover { color: red; }

or:
/** Just keep as nest css since I want to let stylis not to process this part */
a {
  &:hover {
    color: red;
  }
}

If we want to support & escape, maybe add a new feature like ~& instead of auto detect:
a {
  ~&:hover { // Tell stylis keep the sctructure
    color: red;
  }
}


[GSSoC'23] Guess The Flag Game Completed

Title and Issue number

Title - Guess The Flag Game
Tech used - HTML, CSS and JS
Close #2072

Checklist:

[x] I have mentioned the issue number in my Pull Request.
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md

@pranjay-poddar @Saurabh-kumar09 @MohitGupta121 Sirs, please review this pull request and requested to merge it into the main branch for a successful contribution under GSSoC'23 open-source program

@MohitGupta121 Sir, now the folder size is 686 KB. So, please review this pull request and requested to merge into the main branch.

@MohitGupta121 Sir Project completed. Please again review my pr.
Sorry sir for the disturbance.


Update devices.js

Added Fibaro Thermostat. - I'm new to this zwave and mqtt stuff, but this config seemed to work for me.
Also thanks for this great project!

Thanks @frago711 ! Take a look also to: https://github.com/zwave-js/zwavejs2mqtt#why-zwavejs
It has auto discovery for climates and much more :)

Thanks @frago711 ! Take a look also to: https://github.com/zwave-js/zwavejs2mqtt#why-zwavejs
It has auto discovery for climates and much more :)

Yes, I already stumbled across it, when I checked the last pull request to this file. Will have a look at it in the netxt days. Thanks!


Integration with dask-xgboost.

Hi, I want to work on the integration between dask-ml and dask-xgboost.  Specifically, I want to implement GridSearchCV and RandomizedGridSearchCV for estimators like dask-xgboost, which are already distributed by themselves.  I tried to look into the existing grid search cv implementation in dask-ml, which seems to be written by manipulating the dask task graph instead of using documented public API.  I would like to ask for some guidance before I go ahead and try to implement yet another grid search cv. Some questions are:

What's the best way to handle algorithms that are already aware of dask and can run on distributed systems?
Why is the GridSearchCV written in this way instead of using public API? Should I be using it in a downstream project? If so is there a good place to learn more about it?
Any chance of upstreaming the integration into dask-ml if I were able to implement it?  It will be useful not only for XGBoost, but also for other similar projects like LightGBM.

Related:
https://github.com/dask/dask-ml/issues/833
https://github.com/dmlc/xgboost/issues/5676
https://github.com/dask/dask-ml/issues/758

cc @TomAugspurger (in case you have thoughts here 🙂)

@trivialfis - Quick clarification. Do you want to use Dask for both HP tuning and estimator training?

Yes.

No thoughts. Happy to hear what comes out of this.
On Feb 23, 2022 at 7:39:31 AM, Jiaming Yuan @.***>
wrote:

Yes.
—
Reply to this email directly, view it on GitHub
https://github.com/dask/dask-ml/issues/906#issuecomment-1048792255, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKAOIQQTW4YD6L74HNTNEDU4TPRHANCNFSM5PC46B2A
.
You are receiving this because you were mentioned.Message ID:
@.***>


improve heroku preset

heroku is very customisable but mostly this is done with buildpacks. Here's the node one.
By default the node buildpack will build, prune dev dependencies + package the entire app folder into a docker image. This is lots more space than Nitro needs. Options:

create our own heroku buildpack
create docker image (which can be shared with other platforms): https://github.com/unjs/nitro/issues/54

If you use the default heroku buildpack, you'll need to run heroku config:set HOST=<IP_ADDRESS>

heroku is very customisable but mostly this is done with buildpacks. Here's the node one.
By default the node buildpack will build, prune dev dependencies + package the entire app folder into a docker image. This is lots more space than Nitro needs. Options:

create our own heroku buildpack
create docker image (which can be shared with other platforms)

@danielroe Can you confirm that this issue is still open to optimise the Heroku preset ?

Considering it is an unattended issue for long time and we have a working preset, closing this tracker. docker support might allow improving Heroku preset too.


no support for set_authorizer

I wonder why its not there and not mentioned. I could add it but I am scared off by the dire warning about trying to build it myself

I have a pr out for that: https://github.com/ericsink/SQLitePCL.raw/pull/35

It might need to be updated with the changes Eric made to fix callback functions a couple months back.

I'll take a look and try to get that PR incorporated as part of the current wave of changes I'm working on.

@ericsink saw you merged my PR. I just did a cursory look at it. Are you going to update it to store the the authorizer_hook per database before release?

Yes, I will.
--
E
On Thu, Jul 9, 2015 at 10:42 AM, Dave<EMAIL_ADDRESS>wrote:

@ericsink https://github.com/ericsink saw you merged my PR. I just did
a cursory look at it. Are you going to update it to store the the
authorizer_hook per database before release?
—
Reply to this email directly or view it on GitHub
https://github.com/ericsink/SQLitePCL.raw/issues/51#issuecomment-120040862
.

I have pushed 0.8.1-pre1 to nuget.  It contains this fix.  Any testing on that build would be appreciated.

I'll try to update SQLite.pretty to support this feature and add some tests
over the weekend. Been pretty busy lately though :/
On Thu, Jul 9, 2015 at 1:49 PM, Eric Sink<EMAIL_ADDRESS>wrote:

I have pushed 0.8.1-pre1 to nuget. It contains this fix. Any testing on
that build would be appreciated.
—
Reply to this email directly or view it on GitHub
https://github.com/ericsink/SQLitePCL.raw/issues/51#issuecomment-120140461
.

0.8.1 has been pushed to nuget.  The test case provided in the PR does pass.  Closing this issue.


questions about getting test scores

Are the scores in tableⅠ of MedSedDiff the official test scores or 5-fold cross validation scores? nii.gz files are needed to be uploaded to BraTS2020 website to get the official test score, but I cannot find nii.gz generating section in related source code so I don't know how to get the test score of trained model.

Hi, I've also encountered a problem in this area, how do I perform, for example, a dice test after generating an image? Do I need to write a test.py program?

Hi, I've also encountered a problem in this area, how do I perform, for example, a dice test after generating an image? Do I need to write a test.py program?

I just add a dice score calculate function after generating an image in sample.py. I noticed that this V1-version code is a 2-class segmentation task instead of 4-class(official), thus the official testing is not available. Maybe V2-version code will fix that.

Thanks for your reply and one more question to seek your advice. When the hyperparameter - num_ensemble 5 - samples out 5 images, how do you select the images among them or what is the strategy to select these images to calculate dice with ground truth.

嗨，我在这方面也遇到了一个问题，例如，生成图像后如何执行骰子测试？我需要编写 test.py 程序吗？

我注意到这个 V1 版本的代码是 2 类分段任务而不是 4 类（官方），因此官方测试不可用。所以我只是在 segmentation_sample.py 中生成图像后添加一个骰子分数计算函数。也许 V2 版本的代码可以解决这个问题。

Can you share your code for calculating dice score？

Are the scores in tableⅠ of MedSedDiff the official test scores or 5-fold cross validation scores? nii.gz files are needed to be uploaded to BraTS2020 website to get the official test score, but I cannot find nii.gz generating section in related source code so I don't know how to get the test score of trained model.

I am a beginner,Can you share your code for calculating dice score？Thank you!

Are the scores in tableⅠ of MedSedDiff the official test scores or 5-fold cross validation scores? nii.gz files are needed to be uploaded to BraTS2020 website to get the official test score, but I cannot find nii.gz generating section in related source code so I don't know how to get the test score of trained model.

I am a beginner,Can you share your code for calculating dice score？Thank you!

Change the dataset loader code a bit to load the test set's mask, so that dice are calculated after the sample.

我试了好几次但是都不行，可以加你的联系方式请教你一下吗？

Are the scores in tableⅠ of MedSedDiff the official test scores or 5-fold cross validation scores? nii.gz files are needed to be uploaded to BraTS2020 website to get the official test score, but I cannot find nii.gz generating section in related source code so I don't know how to get the test score of trained model.

I am a beginner,Can you share your code for calculating dice score？Thank you!

Change the dataset loader code a bit to load the test set's mask, so that dice are calculated after the sample.

可以看下代码吗？还没解决

Are the scores in tableⅠ of MedSedDiff the official test scores or 5-fold cross validation scores? nii.gz files are needed to be uploaded to BraTS2020 website to get the official test score, but I cannot find nii.gz generating section in related source code so I don't know how to get the test score of trained model.

I am a beginner,Can you share your code for calculating dice score？Thank you!

Change the dataset loader code a bit to load the test set's mask, so that dice are calculated after the sample.

Hello, I also tried many unsuccessful. How to modify the code to get the dice score? Could you please share or elaborate? Thank you very much. If you would like to share with me, that would be great.Thank you again!


Feature Request: Implement mkYara

https://pypi.org/project/mkYARA/ is a pretty excellent tool for generating Yara rules based on arbitrary binary data in executables. I think it would make a valuable addition to the FLARE-VM arsenal.
Would it be possible to consider it for inclusion in a future release?

@agithubuserlol We've added this to our Python libraries. You can update them with:

choco upgrade libraries.python2.fireeye
choco upgrade libraries.python3.fireeye


unused variables - false positive when usage is inside MESSAGE statement

REPORT zfoobar.

CLASS lcx_syntax_error DEFINITION
  CREATE PRIVATE.

  PUBLIC SECTION.

    CLASS-METHODS invalid_calculation_attempt
      IMPORTING operator TYPE string
                left     TYPE string
                right    TYPE string
                previous TYPE REF TO cx_root.
  PRIVATE SECTION.

ENDCLASS.

CLASS lcx_syntax_error IMPLEMENTATION.

  METHOD invalid_calculation_attempt.
    RAISE EXCEPTION TYPE lcx_syntax_error MESSAGE e016 WITH operator left right
      EXPORTING previous = previous.
  ENDMETHOD.

ENDCLASS.

operator, left right are reported as unused variables

thanks 👍

with less whitespace,
CLASS lcx_syntax_error DEFINITION CREATE PRIVATE.
  PUBLIC SECTION.
    CLASS-METHODS invalid_calculation_attempt
      IMPORTING operator TYPE string
                left     TYPE string
                right    TYPE string
                previous TYPE REF TO cx_root.
ENDCLASS.

CLASS lcx_syntax_error IMPLEMENTATION.
  METHOD invalid_calculation_attempt.
    RAISE EXCEPTION TYPE lcx_syntax_error MESSAGE e016 WITH operator left right
      EXPORTING previous = previous.
  ENDMETHOD.
ENDCLASS.

@FreHu try again, 2.85.19


Unique Columns?

Many database solutions (read: all) have a way to make a column a "unique" column. I'd like to do this in Isar too.
Describe the solution you'd like
Perhaps an @Unique tag on a field that perhaps just performs a query by that field and if it already exists throws an error?
Describe alternatives you've considered
I've been literally doing the previous in my repository - Something like this:
class GroupRepository {
  Future<void> addOne(Group group) async {
    if (await _isar.groups.where().filter().idEqualTo(group.id).findFirst() !=
        null) {
      throw NonUniqueException();
    }

    await _isar.writeTxn((isar) async {
      await isar.groups.put(group);
    });
  }
}

I should clarify that I know that the PK column is unique - but, I'm using uuid's in my database and so my model has two Id's: isar_id and id, the latter being a Uuid.
It'd be helpful to remove this boilerplate by having an @Unique flag on a field that doesn't allow inserts if this already exists.
Thanks, and thanks for the awesome package :)

It's already possible using indexes: https://isar.dev/indexes#unique-indexes
You can even define a "replace index" that replaces existing entries instead of throwing an error.

Ah! Thank you - just what I'm looking for.
you're awesome :)


can i config multiple  services with a same upstream ?

eg:  100 services  configed a same upstream id, target is <IP_ADDRESS>:80;
and 100 services configed 100 different upstream id, but their targets are same,<IP_ADDRESS>:80.
is there some diff  with performance that two way ?

100 services configed a same upstream id, target is <IP_ADDRESS>:80;
100 services configed 100 different upstream id, but their targets are same,<IP_ADDRESS>:80.

is there some diff with performance that two way ?

functional it would be the same, but option 2 would consume more resources (memory, cache). If you enable healthchecks then each upstream would perform its own healthchecks, so a lot of probes to your target.
If they really are the same, then I would stick with a single upstream.

(assuming this answered, if not, feel free to reopen)


markdown link not showing

https://github.com/resin-os/resinos/blob/master/templates/components/_story.html#L11
is showing as  [Docker to ARM chips in 2013](https://resin.io/blog/docker-on-raspberry-pi/).

Well spotted!
For clarity, this is displaying incorrectly on https://resinos.io/ under the "Why resinOS?" section.


Chinese translation

I translated it to Chinese about 2 years ago, and noticed the repo has been moved to heroku organization.
So i made a little repo update, and thought that it's cool if my translate could be merged to the official repo.
But i'm not sure about which way to manage the files. A new branch or a new folder?

@jonmountjoy i noticed you are working on this today, so i make a quick update to match the latest master version :D
I think you can merge it now.

Thank you so much!  It should be live shortly!


[Bug Report] Container exits with code 1 if unable to set backup directory permissions

Have you read the Important information text above

[X] Yes i did

Current behavior
My current docker-compose.yaml file defines the following (I removed the game options for simplicity):
version: '3.9'
services:
  palword-server-jnk:
    container_name: palworld-server-jnk
    image: jammsen/palworld-dedicated-server:latest
    restart: unless-stopped
    hostname: palworld-server
    ports:
      - 8211:8211/udp
      - 27015:27015/udp
    environment:
      - TZ=America/Chicago
      - PUID=1000
      - PGID=1000
      - ALWAYS_UPDATE_ON_START=true
      - MULTITHREAD_ENABLED=true
      - COMMUNITY_SERVER=true
      - BACKUP_ENABLED=true
      - BACKUP_CRON_EXPRESSION=0 * * * *
      - BACKUP_RETENTION_POLICY=true
      - BACKUP_RETENTION_AMOUNT_TO_KEEP=45
      - SERVER_SETTINGS_MODE=auto
      - STEAMCMD_VALIDATE_FILES=false
      - NETSERVERMAXTICKRATE=120
      - RCON_ENABLED=true
      - RCON_PORT=25575
    volumes:
      - /palworld:/palworld
      - /mnt/palworld_bkups/backups:/palworld/backups

Note that I export the backup volume to a different path. The destination is a Synology NAS NFS share that does not permit chown operations. The user running the container (1000) has permissions to write into that directory. When the container starts up, it tries to chown the app directory, which includes the backup path. This operation fails and the container exits.
Desired behavior
While the container files should be chown'd at startup to match PUID and PGID, failures for the backup path should not cause the container to exit.
Links to screenshots
No response
To Reproduce
Steps to reproduce the behavior:

Create container with the /palworld/backups directory redirected to a file system that does not allow chown operations. This can be done via all_squash or root_squash.
Set BACKUP_ENABLED to true
Start container

Software setup

OS: Ubuntu 20.04.6
Docker: version 24.0.2, build cb74dfc

Hardware setup

vCPU: 4
RAM: 12 GB
Disk: 40 GB

Additional context
Container output:
> Current steam user PUID is '1000' and PGID is '1000'
> PUID and PGID matching what is requested for user steam
chown: changing ownership of '/palworld/backups/palworld-save-2024-01-26_20-22-34.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/palworld-save-2024-01-26_22-49-56.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240203_090000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240203_100000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240203_110000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240203_120000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240203_130000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240203_140000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240203_150000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240203_180000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240203_190000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240203_200000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240203_210000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240203_220000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240204_090000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240204_100000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240204_110000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240204_120000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240204_130000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240204_140000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240204_200000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240204_210000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240204_220000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240206_070000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240206_123014.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240206_150000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240206_160000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240206_200000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240207_180000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240207_190000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240207_200000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240207_210000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240207_220000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240208_190000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240208_200000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240208_210000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240208_220000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240209_090000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240209_100000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240209_130000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240210_090000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240210_100000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240210_110000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240211_100000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240211_110000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240211_190000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240212_150000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups/saved-20240212_160000.tar.gz': Operation not permitted
chown: changing ownership of '/palworld/backups': Operation not permitted

Hey @nomad64 - This change was to support dynamic UID/GID switching for other problems with QNAP and Synology NAS'ses.
If you now go ahead and create an edge-case thats based upon that 1 directory doesnt support no permission-changes im not sure how to help here. Im really trying to help everyone out, but some edge-cases are just to weird to be supported in a docker-image to be honest.
Possible solution:
You could just go ahead and leave the directory local and the retention-policy mor conservative and use a cron/hourly to move the backups to the desired location.

Hey @nomad64 - Can this issue be closed?

@jammsen Sorry for the delay in getting back to you, life has been busy lately.
I understand the situation and that my setup is more of an edge case. I honestly can't remember why I setup squash for that mount and will have to revisit that config. In the interim, I simply removed the volume export for /palworld/backups and will make some Ansible changes to move the files to the correct place on server shutdown.
Keep up the great work on this container! :+1:

Thanks, good luck, Happy to help!


[IMPROVEMENT] : Links are opening in same tab

when I'm clicking any links on footer section it is opening in same tab but it should open in a new tab. You can achieve this by only adding target= "_blank" rel= "noreferrer" inside the <a> tag

Wow


#1186: Enable text selection for copy/past in widget

This enables user to select texte from widget as requested https://github.com/kitematic/kitematic/issues/1186

Thanks @mikaoelitiana for the changes - This ended up being pushed in PR https://github.com/kitematic/kitematic/pull/1201 as part of an overhaul of the access port/url.


Removing org members doesn't update UI (probably need to refresh GraphQL cache)

Removing a member from an org doesn't update the UI immediately, presumably because the GraphQL query cache isn't invalidated correctly. The UI refreshes when you reload the page, but it would be better for removing the org member to refresh the UI immediately.

Will be fixed once #887 is merged, because I found the reason why the GraphQL invalidation wasn't working for bulk-add, and while I was at it I also fixed it for adding and removing project members.


Update sync command to work in discord.py 2.4

Rationale

discord.py 2.4 updates the get_translated_payload and to_dict method signatures for application commands, making the CommandTree a required parameter.
Summary of changes made

Support the new function signatures without breaking backwards compatibility with discord.py <= 2.3
Supersedes #230
Checklist

[x] This PR changes the jishaku module/cog codebase

[ ] These changes add new functionality to the module/cog
[x] These changes fix an issue or bug in the module/cog
[x] I have tested that these changes work on a production bot codebase
[x] I have tested these changes against the CI/CD test suite
[ ] I have updated the documentation to reflect these changes

[ ] This PR changes the CI/CD test suite

[ ] I have tested my suite changes are well-formed (all tests can be discovered)
[ ] These changes adjust existing test cases
[ ] These changes add new test cases

[ ] This PR changes prose (such as the documentation, README or other Markdown/RST documents)

[ ] I have proofread my changes for grammar and spelling issues
[ ] I have tested that any changes regarding Markdown/RST syntax result in a well formed document

as discord.py version 2.4 released recently this can be merged as confirmed.

and if this gets merged
pr 230 can be closed too.