Using Javascript's mathematical functions and HTML's canvas to create animations

Proposed title of article
Using Javascript's mathematical functions and HTML's canvas to create animations
Introduction paragraph (2-3 paragraphs):
Animations are a great way to catch a user's attention and enhancing the look of your website. In this article, we will look at how Javascript's built-in functions such as math.min(), math.rand(), setTimeout() etc can be applied to create the animations. We will be creating an animation to simulate the planet system so that we see how the functions are applied.
Key takeaways:
The reader will look at how these are used in creating animations:

JavaScript's shape functions
HTML's canvas
JavaScript's timing functions
CSS styling

References:
N/A

@vinstex
Good afternoon and thank you for submitting your topic suggestion.
Your topic form has been entered into our queue and should be reviewed (for approval) as soon as a content moderator is finished reviewing the ones in the queue before it.

Just and FYI I will be closing this topic form just to help clear up the queue where possible - can be REOPENED at anytime when ready. 👍


Fixes #8794

@bpasero  @jrieken   take a look

We cannot hardcode keybindings like that. If someone defines Ctrl+A to let's say open file he is blocked by this. The commands that are bound by default to those keys should have a when condition which tells the keybindings service not run the command (and thereby consume the event).

@jrieken  selectAll actions maybe add a when condition editorTextFocus

Yes, we have a similar issue with cut, copy, paste and now have a when condition

@jrieken 	how about this? https://github.com/Microsoft/vscode/pull/8797/commits/77d061426e7bf981dcbe3c21ff677720f82dd542

@jrieken @f111fei while the change seems to enable dropping stuff into the web view, I see issues:

this disables any workbench related DND interaction if you go over the web view (e.g. you can no longer drop a file into the editor area to open the file)
I am able to drop a URL into the web view and have it opened (see screen shot below)

Should we just be strict here and say that the HTML preview feature is not intended for DND operations?

this disables any workbench related DND interaction if you go over the web view (e.g. you can no longer drop a file into the editor area to open the file)

Workbench related DND interaction is contradictory with my usage. We can only choose one.

I am able to drop a URL into the web view and have it opened (see screen shot below)

Default if you drop a link into an electron window it will try to navigate to that URL. We maybe can prevent the interaction in my html extension.

Closing as this needs further discussion/different changes


Machine Configuration Refactor

This PR refactors the Machine Configuration makefiles. This is necessary to support new types of heterogeneous machines (added new parameters), make it clearer which parameters are important (reordering), and what the important parameters affect (renaming).
This was motivated by adding Ruche Networks, a new parameter for X/Y origin, incoming BP integration and repeated questions from users about what the parameters mean.
In the meantime, I cleaned up some F1 bit-rot.
In general, CL_MANYCORE parameters have been renamed to BSG_MACHINE parameters. There are a few others that are important and should be noted:
BSG_MACHINE_GLOBAL_X -> BSG_MACHINE_NUM_CORES_X
BSG_MACHINE_GLOBAL_Y -> BSG_MACHINE_NUM_CORES_Y

These now reflect the number of cores, not the maximum x/y that each core can access (this is now computed). This was done to increase clarity in the machine definitions and the verilog top levels. GLOBAL_X/Y is now computed.
BSG_MACHINE_VCACHE_BLOCK_SIZE_WORDS -> BSG_MACHINE_VCACHE_LINE_WORDS
BSG_MACHINE_VCACHE_STRIPE_SIZE_WORDS -> BSG_MACHINE_VCACHE_STRIPE_WORDS
BSG_MACHINE_DRAM_SIZE_WORDS -> BSG_MACHINE_DRAM_WORDS
BSG_MACHINE_DRAM_BANK_SIZE_WORDS -> BSG_MACHINE_DRAM_BANK_WORDS

These are clarity renamings. Lines is more common than blocks when discussing caches. SIZE is more common for bytes.
Where a straight renaming wasn't possible (e.g. manycore depends on a parameter), I created an an alias. For example:
BSG_MACHINE_GLOBAL_X                  = $(BSG_MACHINE_NUM_CORES_X)
BSG_MACHINE_GLOBAL_Y                  = $(shell echo $(BSG_MACHINE_NUM_CORES_Y)+$(BSG_MACHINE_ORIGIN_COORD_Y)-1 | bc)
BSG_MACHINE_DRAM_BANK_WORDS           = $(BSG_MACHINE_DRAM_PER_CACHE_WORDS)
BSG_MACHINE_DRAM_BANK_SIZE_WORDS      = $(BSG_MACHINE_DRAM_BANK_WORDS)
BSG_MACHINE_VCACHE_BLOCK_SIZE_WORDS   = $(BSG_MACHINE_VCACHE_LINE_WORDS)

This way everyone gets the best of both worlds. The variables expected in bsg_manycore are still there, but users get clearer names.
I also changed the format of Makefile.machine.include files. All of the parameters that are important, and configurable, are now defined at the top of the file. The constants and re-computations are defined at the bottom, after a separator.
In addition, I have removed f1_paramters.vh, which contained macros that were read by verilog. These are now used to generate bsg_bladerunner_pkg.v, which defines a list of parameters that are a single-source-of-truth for the machine configuration. Packages are better for debugging and simulation since they are a verilog primitive, not a pre-processor.
The parameters in the bsg_bladerunner_pkg.v have a consistent naming scheme. Some names have been adapted to highlight their purpose -- for example addr_width_p has become bsg_machine_noc_epa_width_gp. All the parameters in bsg_bladerunner_pkg.v are printed when simulation starts.
Finally, I added new machines for infinite memory Ruche Networks, and renamed existing machines. Machine names are now a tuple: (timing, baseline, infinite)(mesh, ruche)(dimension).
To summarize:

Renamed variables for clarity
CL_MANYCORE -> BSG_MACHINE (affects all instances of Makefile.machine.include, hardware.mk)
Reorganized Makefile.machine.include files
Renaming of machine directories (v0 -> mesh, v1 -> ruche)
Removed all 64x32 machines.
Removed of f1_parameters.vh, replaced with bsg_bladerunner_pkg.v(affects hardware.mk fragments, cl_manycore_pkg.v, testbenches)
Renamed parameters in bsg_bladerunner_pkg.v for clarity

This PR passes on all major machines and platforms.
On dpi-vcs:

timing_mesh_8_4
timing_mesh_16_8
timing_ruche_8_4
timing_ruche_16_8
infinite_mesh_4_4
infinite_mesh_8_4
infinite_mesh_16_8
infinite_ruche_8_4
infinite_ruche_16_8

On dpi-vcs:

timing_mesh_8_4
timing_ruche_8_4
infinite_mesh_4_4
infinite_ruche_8_4

On aws-vcs

4x4_blocking_vcache_f1_model


"onMaxClick" does not work in windows

Hello,
I confronted with an issue during working with windows in Metro UI. I am going to use  event "onMaxClick", but it does not work. It is coded in codepen.
Thanks
https://codepen.io/vahidbabaveisi/pen/WNogRxw

fixed, thx


'finally': Tests against promises always pass.

Using should version 8.0.2 and q version 1.4.1, this test passes when it should fail:
it("should fail, because it doesn't resolve to the right number", function () {
      var deferred = Q.defer();
      deferred.promise.should.finally.be.exactly(5);
      deferred.resolve(3);
});

your promise is not evaluated. If we are talking about mocha, you need return promise (or use callback), like:
it("should fail, because it doesn't resolve to the right number", function () {
  var deferred = Q.defer();
  var p = deferred.promise.should.finally.be.exactly(5);
  deferred.resolve(3);
  return p;
});

This test now fail:

Thank you for your help and quick response! I was stuck for a while on this.

No problem. You are welcome.


Add support for cats effect with AHC backend

Looks good! Maybe you would like to add yourself to the credits in the readme?

Updated readme.
I have a version for fs2 with streaming as well, but there's some dependencies I need to sort out first.

Ok, I'll merge this and then we can work on fs2 in a separate PR
Thanks for the contribution!

Released in 0.0.5


add READMEs to dapr/proto folders for ease of information

Description
I added in READMEs to the dapr/proto/* folders to make it clearer what the APIs in the folders were for. I know there is a README in dapr/proto. I felt as though we may benefit from folder specific READMEs, as it was unclear that the protos in the dapr/proto/components were specifically for pluggable components with things as is. I then didn't want to just have a README in the dapr/proto/components, so I added one for each of the folders with a relevant service doc link. Feel free to comment if you feel the wording could be improved or expanded upon.

Since you're doing this, can I also recommend adding some links to:

How to re-generate the code after making changes to the protos (make gen-proto)
Where in the source code the generated files are: pkg/proto

I added this per README, by basically copying/tweaking the instructions from the /dapr folder


DP-1261: Add support for new status format

TODO before merge: Update SDK requirement; https://github.com/oslokommune/origo-sdk-python/pull/47

TODO before merge: Update SDK requirement

Upgrading the SDK will also require updating more of the existing tests. I've made the changes on the upgrade-origo-sdk-python branch that you can use if you'd like. :)


New package: Looper v0.1.0

Registering package: Looper
Repository: https://github.com/IanButterworth/Looper.jl
Created by: @IanButterworth
Version: v0.1.0
Commit: b3c271c5249eea2d74ba235b29f3157716fd4f3a
Reviewed by: @IanButterworth
Reference: https://github.com/IanButterworth/Looper.jl/commit/b3c271c5249eea2d74ba235b29f3157716fd4f3a#commitcomment-144815903
Description: A simple looper

Blocking for name discussion. Could also go with SimpleLooper if this is too general?

this reminds me of the ncall and nexpr we have in Base.Catesian, so maybe that could be a source for name

LoopDeLoop?
I'm tending away from Looper as it seems like too big of a name to take for something so meek.

Renamed to SimpleLooper https://github.com/JuliaRegistries/General/pull/112326


Jest 27: incorrect afterEach order with jest-circus

💥 Regression Report

In Jest 26, it was possible to set up afterEach callback in a setupFilesAfterEnv script which was correctly called after the tests specific afterEach callbacks. It makes sense to behave like this because it allows us to set up callbacks that are executed after any test was completed (including their specific afterEach callbacks).
It seems that Jest 27 calls the "global" afterEach before the test-specific afterEach which breaks our codebase. It's because some of the tests are calling jest.restoreAllMocks in afterEach and later we are checking (in the global afterEach) whether all console mocks were actually restored or not.
Use case: we are capturing unexpected console logs in a similar way like React, see:

https://github.com/facebook/react/blob/bb1c8215569f59b70276e8939bd8a59aa7f28f53/scripts/jest/setupTests.js#L159-L160
our code: https://github.com/adeira/universe/blob/adc8bdf25d253b8bb883a040b6bf0d4bd1b66404/scripts/jest/setupTests.js#L63-L92

Test file:
afterEach(() => {
  jest.restoreAllMocks();
});

Setup file:
afterEach(() => {
  // here we check whether `restoreAllMocks` (or any equivalent which restores console mocks) was called
  // HOWEVER, if this global callback is called first then the test-specific mocks are not restored yet breaking the logic
});

Last working version
Worked up to version: 26.6.3
Stopped working in version: 27.0.1
To Reproduce
Steps to reproduce the behavior:

setup afterEach callback in setupFilesAfterEnv script
setup afterEach callback in some test
check the order of execution of these callbacks (the test specific one should be run before the one from setupFilesAfterEnv)

Expected behavior

The order of afterEach callbacks is not changed from version 26 so it's still possible to register custom global afterEach callback.
Link to repl or repo (highly encouraged)

https://replit.com/@mrtnzlml/jest-afterEach-bug (try to change the Jest versions in package.json and check the difference in the order)
Run npx envinfo --preset jest
Paste the results here:
  System:
    OS: macOS 11.2.3
    CPU: (8) x64 Intel(R) Core(TM) i5-1038NG7 CPU @ 2.00GHz
  Binaries:
    Node: 16.2.0 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 7.14.0 - /usr/local/bin/npm
  npmPackages:
    jest: ^27.0.1 => 27.0.1

I'm not sure what makes the most sense. @jeysal?

@SimenB In case this issue gets dismissed, is there any other way how to have a global afterEach callback so we can achieve the same thing?

Tbh I would say the previous behavior is rather unexpected (and I certainly didn't know it used to behave that way), because in any other case afterEachs would be executed in the order they are declared.
There is no drop in replacement that comes to my mind to get the previous behavior, only things that require more changes like calling something explicitly at the end of each test file, or monkey patching things. But I suppose the same is true with the old behavior if you wanted your afterEach to be run before the test afterEachs. So maybe this issue should be about giving users a way to control that easily. Or maybe there is already a good enough way? Not sure

We ran into this issue as well. In several cases we have afterEach calls in our test files that do some localized cleanup, then we have a global afterEach that does things like clearing out the DOM. Upgrading to Jest 27 breaks a lot of tests for us as our code assumes that they are run in order of locality. In other words, we expect global beforeEach and afterEach callbacks to be the first and last in the chain respectively.
Putting the global afterEach before the local one causes confusing test behavior. Previously, it was a convenience that helped smooth the developer experience between tests. They could largely ignore it. Now it means developers have to be very aware of how it behaves whenever they're writing tests.

Where in the docs is this specified?

do not close, please

Still experiencing this issue with jest-circus... For now we have unblocked ourselves from upgrading past Jest 26 by using explicitly specifying jest-jasmine2 as our test runner.

Hi @jeysal ,
I would still vote for fixing a bug instead of documenting it.
There are many testing libraries around, which use hooks under the hood, and the expectation is that the order of their execution will be respected, as it is in all other testing frameworks. Not sure why jest decided to invent own way and to cause issues.
Let's take a look at a simple example: we want to backup a global variable for a test, and restore it afterwards.
To avoid copy-pasting of tons of lines of code, we decided to write a helper function:
const backupTest = (newValue: typeof globalVar): void => {
  let backup: typeof globalVar;

  beforeEach(() => {
    backup = globalVar;
    globalVar = newValue;
  });

  afterEach(() => {
    globalVar = backup;
  });
};

The idea is simple, our test should look like that:
describe('globalVar', () => {
  backupTest(1);

  it('equals 1', () => {
    expect(globalVar).toEqual(1);
  });
});

so instead of having 10 lines of code how to backup globalVar for each test, we have just 1.
Now, let's imagine that globalVar isn't primitive, but a complex object and backupTest does only 1 modification, whereas we need an additional modification, for example, another group of stub members.
In all testing libraries it will look like that:
describe('globalVar', () => {
  backupTest(1); // one group of stub members.
  backupTest(2); // another group of stub members.

  // tests
});

and it works well, after the test, globalVar will have its initial value before the suite, because the first executed afterEach belongs to 2 and the second executed afterEach belongs to 1.
However, with the new changes in jest, globalVar is going to be 1, because of the broken order, because first jest  executes afterEach for 1, and then afterEach for 2, which restores a wrong value.
let globalVar = 0;

const backupTest = (newValue: typeof globalVar): void => {
  let backup: typeof globalVar;

  beforeEach(() => {
    backup = globalVar;
    globalVar = newValue;
  });

  afterEach(() => {
    globalVar = backup;
  });
};

describe('backup', () => {
  it('equals 0 before all', () => {
    expect(globalVar).toEqual(0);
  });

  describe('globalVar', () => {
    backupTest(1); // setting globalVar to 1 and restoring it to 0 afterwards
    backupTest(2); // setting globalVar to 2 and restoring it to 1 afterwards

    it('equals 2 before each', () => {
      expect(globalVar).toEqual(2);
    });

    describe('each', () => {
      backupTest(3); // setting globalVar to 3 and restoring it to 2 afterwards
      backupTest(4); // setting globalVar to 4 and restoring it to 3 afterwards

      it('equals 4 after each', () => {
        expect(globalVar).toEqual(4);
      });
    });

    it('resets to 2 after each', () => {
      expect(globalVar).toEqual(2);
    });
  });

  it('resets to 0 after all', () => {
    expect(globalVar).toEqual(0);
  });
});

which fails on jest as
    expect(received).toEqual(expected) // deep equality

    Expected: 0
    Received: 1

      42 |
      43 |   it('resets to 0 after all', () => {
    > 44 |     expect(globalVar).toEqual(0);
         |                       ^
      45 |   });
      46 | });
      47 |

I was recently affected by this unexpected behavior too.
In my case, it was caused by different testing utilities using beforeEach/afterEach to patch console.error:

https://github.com/ValentinH/jest-fail-on-console (code) cc @ValentinH

https://github.com/testing-library/react-hooks-testing-library (code) cc @mpeyper

Own code used to hide React's "Can't perform a React state update on an unmounted component" warning, which looked more or less like this:
let originalConsoleError: typeof console.error

beforeEach(() => {
  originalConsoleError = console.error
  console.error = (...args) => {
    const reactUpdateOnUnmountedWarning = `Can't perform a React state update on an unmounted component`
    if (String(args[0]).includes(reactUpdateOnUnmountedWarning)) return
    originalConsoleError.call(console, ...args)
  }
})

afterEach(() => {
  console.error = originalConsoleError
})

I wonder what's the recommended approach to address scenarios like this.
The best approach I could come up with is to not unpatch console.error at all (not tested):
let shouldHideReactUpdateOnUnmountedWarning = false

beforeAll(() => {
  const originalConsoleError: typeof console.error
  console.error = (...args) => {
    const reactUpdateOnUnmountedWarning = `Can't perform a React state update on an unmounted component`
    if (
      shouldHideReactUpdateOnUnmountedWarning &&
      String(args[0]).includes(reactUpdateOnUnmountedWarning)
    ) {
      return
    }
    originalConsoleError.call(console, ...args)
  }
})

beforeEach(() => {
  shouldHideReactUpdateOnUnmountedWarning = true
})

afterEach(() => {
  shouldHideReactUpdateOnUnmountedWarning = false
})

This is still relevant. 😎

not stale


Create Introduction Component

Create the Introduction component. It will carry WYSIWYG markup and should follow the mockup.
https://www.figma.com/file/u4rMeypztxJhhY1RdaBPTN/RS-Video-Draft?node-id=84%3A62

added the headline portion to this component via the latest figma sketch

v1 of this has been deployed


ci: add large-size E2E CI job

this commit adds a new workflow to the Training repo
it will run a nightly cron job to test the current 'main' branch of Training against the current 'main' branch of the CLI (instructlab)

This will be good for testing things like https://github.com/instructlab/training/pull/268


Updates

Description
Please provide a 1 line description of your art
Logo of Aarogya Setu
Fixes #issue-number
Insert the image of the art below

Checklist:
To fill the checklists, put x inside the brackets. [x]

[x] My code follows the guidelines of this project
[x] I have tested my code and it works properly
[x] I have added just one folder that includes my Art files (jsx and css)
[x] I have not edited App.js file
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x] This is my original code and I have NOT copied the code from anywhere else.

Had to keep the background white so that it is properly displayed

Amazing job @Shridhar-dev

Thanks :blush:


Auto discovery failure

I configured this integration successfully, but I had to do a manual installation.
The heat pump (Alpha Innotec LWDV-91) is not discovered and in the logs I find these error messages:
2023-12-22 12:18:11.040 ERROR (MainThread) [custom_components.luxtronik2] Could not handle config_flow.async_step_dhcp DhcpServiceInfo(ip='<IP_ADDRESS>', hostname='', macaddress='0009822099a4')
Traceback (most recent call last):
File "/config/custom_components/luxtronik2/config_flow.py", line 256, in async_step_dhcp
broadcast_discover_ip, broadcast_discover_port = discover()[0]
~~~~~~~~~~^^^
IndexError: list index out of range
2023-12-22 12:18:12.023 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/discovery_flow.py", line 96, in _async_start
await gather_with_limited_concurrency(
File "/usr/src/homeassistant/homeassistant/util/async_.py", line 187, in gather_with_limited_concurrency
return await gather(
^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/util/async_.py", line 185, in sem_task
return await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 880, in async_init
flow, result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 908, in _async_init
result = await self._async_handle_step(flow, flow.init_step, data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 396, in _async_handle_step
if result.get("preview") is not None:
^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'get'
2023-12-22 12:18:15.715 ERROR (MainThread) [homeassistant.components.homeassistant_alerts] Timeout fetching homeassistant_alerts data

My home assistant installation has three network interfaces, one primary and two VLAN interfaces. The Heatpump can be reached via one of the VLAN interfaces.
Integration functions normally, but after each restart of HA the error message appears again.

Is the VLAN while startup available?
Perhaps the same problem as #216

Yes, VLAN was available at the moment of the error log (it's the IoT VLAN, if it is not there half of the integrations would not start)
I think this one is different from #216. I tried if this is related to the interface used for multicast traffic (in HA network settings), but even with the multicast interface set to the IoT VLAN the error appears.


some updates

@kaapstorm I can't remember this change. I'm thinking of closing this PR. Any objections?

I found this going through old PRs. I think this is a result of some rebasing. I'm closing it.


docs: fix readme code blocks formatting

The first lines were hidden. This also adds syntax highlighting

Thank you, this is great!


[MultiSelect]Can I limit the number of multiple selections?

There is a requirement in my project that only 2 businesses can be selected at most. Is there any parameter to realize this function?

hi @daddisapisero ,
This issue is resolved. Please install later version.
Use "maxSelect" props.


OLM refactor follow up

RELEASE_VERSION was not getting set in the packageserver deployment
env vars
Guest cluster manifests had the wrong prefix (user-data instead of
user-manifests)

It says it's available in its cluster operator, but I guess that doesn't mean everything is ok. Ideally we can validate using the e2e conformance tests.


Can't load scene directly from bundled .app on macOS

Godot version:
3.0 RC 2
OS/device including version:
macOS Sierra 10.12.6
Mono JIT compiler version <IP_ADDRESS>
Issue description:
When using RC 2 with mono on macOS, clicking the "play" button does not launch the game. When running the project through the terminal, an error is shown:

If I use Godot 3.0 RC 2 classic, it works flawlessly.
The project is nothing special: just the Godot icon. There are no C# scripts on any nodes.
Steps to reproduce:
Attempt to run the project
Minimal reproduction project:
MonoSandboxRc2.zip

@reduz This issue doesn't happen with mono builds only.


Scaffolding requires Individual User Accounts

It would help our Intro to MVC tutorial if we didn't need all the code from Individual User Accounts

TFS Bug#232592

This is intentional and we will remove that requirement in future releases.


Support serialization of maps as structs

Required to support #[serde(flatten) again
Implementation idea:

add a strategy to a struct type that says serialize to map / deserialize from map

Open question:

support schema tracing? add a general option, that converts maps to structs?

fixed on the arrow2 branch


Crypto account import are not persistent

I did a fresh install on a new iPhone 11 v 2.4.21 (441) (never had altme installed on it before)
imported 4 accounts
added tz ownership cards
closed the app
reopened it
all 4 tz ownership cards are gone
cannot add them again

Fixed in beta 2.4.28 IOS/Android


[Bug] App crashes after clicking command icon in overview popup and continues crashing whenever overview is toggled

Description
After installing KeyClu with the Notion extension, I began exploring its features. While using the Notion shortcuts overview (activated by double-tapping the ⌘ cmd key), I clic
ked the ⌘ command icon in the bottom bar. This caused the app to crash, and now it crashes every time I try to open the shortcuts overview in any app. Since I cannot access the shortcuts overview or find relevant settings to fix this issue, the app has become unusable. Diagnostic reports are attached below.
diagnosticreports.zip
Expected behavior
Not to crash, or at least enable reverting what I enabled somewhere in the settings.
App version
0.29 (23917)
macOS version
macOS Sequoia 15.1.1 (24B2091)
Installation method
Manual (dmg/zip)
Checklist before submitting a bug

[X] This issue hasn't been addressed in an existing GitHub issue or discussion.

Hey mkoslacz,
Thanks for reporting this issue and providing crash report! I'll look into it as soon as I can. In the meantime, you can avoid the crash by turning off macOS Keyboards Shortcuts integration in the Settings -> Integrations.


Merge master branch to prTesting1_201903070909 branch

OPS Build status updates of commit 8641aa4:
:clock10: Pending: waiting for processors (7 builds ahead of you)
:warning: OPS Build is busy, currently there are 7 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

OPS Build status updates of commit 8641aa4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

split/updateTestRef1.md
:bulb:Suggestion

Details

split/updateTestRef1.md

[Suggestion] Missing attribute: author. Add a valid GitHub ID.
[Suggestion] Missing attribute: ms.author. Add a valid Microsoft alias.
[Suggestion] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Suggestion] Missing attribute: ms.topic. Add a valid value to indicate the article type.
[Suggestion] Missing attribute: ms.date. A freshness date is required for this content set. Add a date in format MM/DD/YYYY.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


'@ID' tags are not properly validated for uniqueness

Describe the bug
Two routes with the same path may share an ID without an error being thrown. This is because the map holding
paths will be overwritten with the latest route see here
To Reproduce
Create two endpoints that have the same path. For example
// @ID duplicate-id
// @Router /api/foo/{id} [get]

// @ID duplicate-id
// @Router /api/foo/{id} [delete]

Expected behavior
No two routes should be able to share an ID.
Your swag version
e.g. 1.7.0
Your go version
go version go1.15.6 linux/amd64
Desktop (please complete the following information):

OS: [linux]
Browser: [chrome]
Version: [22]

This is an OSS project, please feel free to do a PR if you feel like it's really important to you.


Precompiled Kotlin DSL scripts fix the JVM target to 8

Expected Behavior
Precompiled Kotlin DSL scripts should allow configuring the JVM target, by setting it in the kotlin-dsl target instead of hardcoding it in the precompiled script templates (like here).
Current Behavior
Precompiled script templates hardcode the JVM target for all precompiled scripts to 8.
Context
Being able to optionally target JVM 11 is gradually becoming more relevant as more and more libraries switch their JVM target to 11.

Hi Cesar,
KotlinInitScript, KotlinSettingsScript and KotlinBuildScript are templates for the build scripts.
The templates for precompiled script plugins are in PrecompiledScriptTemplates.kt and they don't enforce any jvmTarget.
Here is a precompiled script plugin using Java 11 opened in IDEA:

The build configuration contains:
plugins {
    `kotlin-dsl`
}

kotlinDslPluginOptions {
    jvmTarget.set("11")
}

We were missing some test coverage for setting jvmTarget to something else than 8, added in https://github.com/gradle/gradle/pull/20907.
I'm going to close this issue as invalid. Please open another one with a reproducer if you encounter any issue using precompiled scripts with other jvmTarget than 8.

Ohhh that's excellent. Thanks, Paul!

I run into a tangentially related issue when referencing JVM11 utilities from my build.gradle.kts. Reported in #21041.


Training on own dataset

Hello,
When I am training using my own dataset created using tfrecords I get this error at the same step always:

tensorflow.python.framework.errors_impl.OutOfRangeError: PaddingFIFOQueue '_1_get_batch/batch/padding_fifo_queue' is closed and has insufficient elements (requested 4, current size 0)
[[node get_batch/batch (defined at ../data/io/read_tfrecord.py:98) ]]

Something wrong with your tfrecord. @nassarofficial

hello, can you release  convert_data_to_tfrecord_coco.py ?
thank you

https://github.com/DetectionTeamUCAS/Cascade_FPN_Tensorflow/blob/master/data/io/convert_data_to_tfrecord_coco.py
You need to make some modify because I'm not using the official json format. @reeceshearsmith

Thank you very much @yangxue0827

This repo has not been reproduced, still in debugging. @reeceshearsmith

Thanks for informing : )


[Python high-level SDK] Add some usage examples

I took the high-level lakeFS SDK out for a spin and had a lot of fun.  And I don't even like Python 🐍 .
Tested them on my interactive Python shell.
Fixes #7232.

@nicholasjng I would really welcome your review, of course!

Heh, too late.

Heh, too late.

@nicholasjng it's never too late 😄
We can continue making the modifications as necessary


An empty "allow_origins" or a wildcard does not work

Because of https://github.com/gin-contrib/cors/issues/37 we need to set manually AllowAllOrigins to true if the  AllowOrigins is empty or has a wildcard.

Fixed in #2


Support for openmc.CylindricalMesh

This currently doesn't support MeshFilter with CylindricalMesh

by replacing _find_coords_of_mesh by
def find_coords_of_mesh(mesh: openmc.CylindricalMesh):

    xs = mesh.r_grid
    ys = mesh.phi_grid
    zs = mesh.z_grid

    return xs, ys, zs

This could work, although it produces a cartesian mesh

I think a deep dive into the vtk package would be needed
cartesian mesh != CylindricalMesh

After a deep dive into the VTK pacakge, I made a PR to OpenMC directly (see https://github.com/openmc-dev/openmc/pull/2096)
This PR also works for RegularMesh and RectilinearMesh so we could potentially get rid of this package if this gets merged in

Great stuff Remi. These little packages are great places to develop ideas but ultimately it is more ideal if we can move these features in to the main code. This will be particularly nice as the core of this code came from Patrick who is an OpenMC developer so it is one big circle


Master -> Live

Docs Build status updates of commit aa176d3:
:warning: Validation status: warnings

File
Status
Preview URL
Details

mixed-reality-docs/interaction-fundamentals.md
:warning:Warning
View
Details

mixed-reality-docs/testing-your-app-on-hololens.md
:warning:Warning
View
Details

mixed-reality-docs/TOC.md
:white_check_mark:Succeeded

mixed-reality-docs/development.md
:white_check_mark:Succeeded
View

mixed-reality-docs/hands-and-tools.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mrtk-getting-started.md
:white_check_mark:Succeeded
View

mixed-reality-docs/interaction-fundamentals.md

Line 163: [Warning] Cannot find bookmark '#news-and-notes' in 'mixed-reality-docs/index.md'

mixed-reality-docs/testing-your-app-on-hololens.md

Line 53: [Warning] Cannot find bookmark '#news-and-notes' in 'mixed-reality-docs/index.md'

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


chore(deps): fix cev issues

Fixes #

Codecov Report

Merging #107 (a14abc1) into main (a78d0a8) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #107   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         2
  Lines          125       125
  Branches        21        21
=========================================
  Hits           125       125

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


Change default for is_file() and fix typo in docs

Two minor changes. Fixes #134 and #135.

Thanks @cwognum. I will merge and add the same logic to is_dir as well.


Tab tearout for Settings page loses current page

Windows Terminal version
1.23.2611.0
Windows build number
N/A
Other Software
No response
Steps to reproduce

Open the settings UI
Navigate to a page that isn't the first one (aka the default page we open to)
tearout the settings tab (click and drag the tab out of the window)

Expected Behavior
The settings UI should still be on the same page
Actual Behavior
We reset to the Startup page. Additionally, any changes we had are lost.

Discussed with the team. This is a real bug, but it's really not worth fixing.


crash when clicking on parameter name [in plotting window]

Everything is running smoothly, dual plotting is possible.
But when clicking on the parameter name, it causes a crash.
Only error notification is:

TypeError: native Qt signal is not callable

I actually tracked that one down recently :)
i'll merge a fix shortly (i hope)

should be fixed now. let me know if if re-appears.


feat(api): Add option to enable sync on import

SUMMARY
In order to bring the API more in line with the CLI, I have added the ability to specify sync_columns and sync_metrics when using the API.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS
Set sync_columns or sync_metrics to true. The API should behave like the CLI when those flags are set.
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[x] Introduces new feature or API
[ ] Removes existing feature or API

@eschutho looks like this might be ready to merge if it meets your standards :)

@reesercollins sorry, this slipped under my/our radar again 🤦
If you could rebase/resolve the conflicts, we'll merge the thing pronto.


Persian

Issue Type: Feature Request
Hello Everyone,
As  a persian i cannot type persian text in vscode.  to solve this problem i checked the new times and times. but i was not satisfied with the suggestions.
please help me. thanks.
Regards
J.K
VS Code version: Code 1.55.2 (3c4e3df9e89829dce27b7b5c24508306b151f30d, 2021-04-13T09:37:00.942Z)
OS version: Windows_NT ia32 10.0.15063

In Python I meant.


Feature/vassili/playlist page

Purpose
Create the playlist page on lti site
Proposal
Create the page, fetch playlists list and display the result.

features/Playlist with capital P


Respect error formatting in problems panel

The problems panel seems to be discarding some of the formatting that would normally exist. In the included screenshot you can see that the problems panel has removed some of the spacing in the panel itself, but the hover menu has the correct formatting.

this makes it nearly impossible to use the problems panel to debug when there are types that are heavily nested.

/duplicate
Very similar to https://github.com/microsoft/vscode/issues/54272

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


Loading state

What is the loading state while hooks are loading?

Currently the during loading the container shrinks to near zero height and then expands. This is unwanted content jumping we should fix when we implement loading.


[PVP] Many fixes and changes. All my pvp prs combined.

Sorry for the massive single pr. Removing the vpr code for kaeris to do vpr got all my branches confused and the best way I could do this was to merge all my branches into one, fix vpr conflict, and put in new pr. All the kaeris recommendations from other prs were ported over.
Untouched They seem to be working fine. WAR, MCH, SAM, PCT, WHM, SGE, SCH
DRK
Fixed the wrong buff code on blackest night, it was overwriting itself. Added was last ability used as good measure bc of server ticks.
Move the Shadowbringer health slider to where it should be in config screen.
PLD
Added Holy Sheltron to the burst combo in melee range/combat.
GNB
Added Heart of Corundum to burst combo with an hp slider to avoid wastage. Can it be used on other? sure, but realistically, GNBS aren't gonna be healing people with it.
Optimized the burst and slimmed down the code significantly. Fixed the 4th combo action.
Added slider for Blasting zone target health %
BRD
Fixed harmonic arrow hijacking the whole combo. Gave it a slider for choice of how many charges to use it at. Added a execute mode for under 12k health so anything above 2 charges should kill your target.
DNC
ported the dancer partner remind over from pve without the autorotation stuff. added EnAvant option to boost 1 2 combo damage with slider to save charges per user preference.
DRG
Fixed Broken 1234 combo adding drakebane. Added execute mode for chaotic spring. It bypasses guard so it is a good option to kill anything under 8k health.
MNK
Fixed logic of fire resonance to always use it with phantom rush (largest hit of 12k) unless 2 charges are available and then throw one of a flints or winds reply (2nd largest hits of 8k but aoe)
RPR
Added Harvest moon execute range at the bottom for enemies under 12k
NIN
Made Mudra Automatic mode an actual option to fix issue with discord report. Added a mudra pooling mode for bunshin burst window. Added the lb execute onto aoe mode as well.
VPR
I put it back to the original code so that it shouldnt conflict with Kaeris vpr
RDM
Added option to hold charges of corps and displacement if the player chooses.
Fixed displacement simply not working for me. Adjusted to more action readys instead of the getcooldown code that wasnt working for displacement
Tweaked so that the displacement, corps, and embolden buffs all line up with scorch for max damage
SMN
Removed unused fester slider from the config that would confuse the masses
Removed the Canweave from the dps options (necrotize and lb stuff) to streamline things
BLM
Fixed the blizzard side trying to use foul. Not longer a pvp spell. Replaced with xeno as it intends
Fixed missing slider for wreath of ice health threshold.
Added wreath of fire execute mode option with slider. While it goes through guard, it is a lot of dps lost when it can have 50% uptime.
Fixed flare star to only show on the fire button if in astral fire, or the blizzard button if in umbral ice. Allows you to LB and use freeze or flare to change elements and use the star you choose.
AST
Fixed the gravity options to work properly. It was ONLY working with double gravity.
Fixed macrocosmos to work without double gravity if not selected but still hold for double gravity if selected.
Removed pvpimmune tag from lady of crowns as it is an aoe heal.

@zbee This is good to go now. I have checked and tested if everything functions as intended.


fixing typo in instances_retrievable flag

It needs to be instances_retrievable
Ref: https://github.com/openservicebrokerapi/servicebroker/blob/master/spec.md#fetching-a-service-instance

Pull Request Test Coverage Report for Build 5309

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 89.216%

Totals

Change from base Build 5302:
0.01%

Covered Lines:
9570

Relevant Lines:
10356

💛  - Coveralls

Validation on k8s cluster: n-2 is succeeded.

Validation on k8s cluster: n-1 is succeeded.

Validation on k8s cluster: n is succeeded.

Validation on k8s cluster: n is succeeded.


Add STObject constructor to explicitly set inner object template

High Level Overview of Change
Add an STObject constructor overload that includes an additional bool argument to set the inner object template. Set the argument to true if the constructed object is an inner object and if the fixInnerObjTemplate amendment is enabled.
Context of Change
Currently, the inner object template is not set upon object creation. If the object contains an soeDEFAULT field, and this field is initially set to the default value, accessing the field results in tefEXCEPTION error. Conversely, if the top object's soeDEFAULT field, initially set to the default value, is accessed, it returns the default value since top objects have the template set during construction. This fix aims to make the inner object behavior consistent with the top object behavior. The inner object must be explicitly constructed, as described in the summary, for this fix to work.
Currently, two AMM fields, sfTradingFee and sfDiscountedFee, included in the inner objects sfVoteEntry and sfAuctionSlot respectively, are declared as soeDEFAULT fields. This fix employs the new STObject constructor when constructing inner objects that include these fields.
Type of Change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Refactor (non-breaking change that only restructures code)
[ ] Performance (increase or change in throughput and/or latency)
[x] Tests (you added tests for code that already exists, or your new feature included in this PR)
[ ] Documentation update
[ ] Chore (no impact to binary, e.g. .gitignore, formatting, dropping support for older tooling)
[ ] Release

Test Plan
AMM unit-test is extended with a test, which demonstrates the behavior before and after this fix.

Our current setup for amendments works well when modifying and add transactors. It works less well with bug fixes - especially bug fixes that effect lower level classes. We've run into this several times with STAmount and number classes, and now we're running into it with STObject. I dislike passing in a bool into the constructor like this patch does, although I understand why you did it.

After talking with some people, we would like to see a 2.0.2 for this fix that gets pushed ASAP. Waiting for 2.1.0 seems too long imho.

Looks good. One optional comment to consider.

There is another update. Please re-review. Thanks.

Why don't we just make these fields soeOPTIONAL? Whats the purpose of these being soeDEFAULT?
Also you stated If the object contains an soeDEFAULT field, and this field is initially set to the default value, accessing the field results in tefEXCEPTION error.
Isn't this exactly what default behavior is supposed to be? soeDEFAULT // optional, if present, must not have default value
Thanks

Why don't we just make these fields soeOPTIONAL? Whats the purpose of these being soeDEFAULT?
Also you stated If the object contains an soeDEFAULT field, and this field is initially set to the default value, accessing the field results in tefEXCEPTION error.
Isn't this exactly what default behavior is supposed to be? soeDEFAULT // optional, if present, must not have default value
Thanks

Changing the field's style is risky and it's a lot more code changes.
soeDEFAULT field saves space. If it has the default value then it should not be present. But if it is accessed then it should return the default value if it's not present.

Why don't we just make these fields soeOPTIONAL? Whats the purpose of these being soeDEFAULT?
Also you stated If the object contains an soeDEFAULT field, and this field is initially set to the default value, accessing the field results in tefEXCEPTION error.
Isn't this exactly what default behavior is supposed to be? soeDEFAULT // optional, if present, must not have default value
Thanks

Changing the field's style is risky and it's a lot more code changes.
soeDEFAULT field saves space. If it has the default value then it should not be present. But if it is accessed then it should return the default value if it's not present.

Ah I see thank you

@legleux reviewing for QA


Not found: type EnglishLexer

Hello, I downloaded Factorie onto my Ubuntu machine and got the prerequisites like Scala and Maven installed. I am running Factorie through IntelliJ.
Upon running Grid.scala, I get that type EnglishLexer cannot be found.

Can you compile and run on the command line?
On Wed, May 6, 2020 at 2:16 AM vkrishnamurthy11<EMAIL_ADDRESS>wrote:

Hello, I downloaded Factorie onto my Ubuntu machine and got the
prerequisites like Scala and Maven installed. I am running Factorie through
IntelliJ.
Upon running Grid.scala, I get that type EnglishLexer cannot be found.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/factorie/factorie/issues/390, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAY5TNZ4PECW7K3JBNM5IJTRQD6CBANCNFSM4M2FE2BQ
.

I ran it through the command line and it worked, thanks.
Btw I am trying to write a simple program where given a single die, I'd like to find say the probability of only even number showing up. Can you point me to some resources or examples that I can use?

I think what you would want to use for an example like this are the
Marginal and Summary classes, and then manually pick out and process the
values you wanted (i.e., finding the probability of each even number and
adding them up).
http://factorie.cs.umass.edu/usersguide/UsersGuide450Inference.html
On Thu, May 7, 2020 at 10:55 PM vkrishnamurthy11<EMAIL_ADDRESS>wrote:

I ran it through the command line and it worked, thanks.
Btw I am trying to write a simple program where given a single die, I'd
like to find say the probability of only even number showing up. Can you
point me to some resources or examples that I can use?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/factorie/factorie/issues/390#issuecomment-625601503,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHS44WWPK7YTI47RSCDPD3RQNYAVANCNFSM4M2FE2BQ
.


Division by constant floating point 0 should be permitted by the compiler or outlawed by the spec.

See https://play.golang.org/p/jxi2L81R1j
This program is rejected as invalid by the compiler, because of a division by constant 0. This, however, does not match the spec: the language "If the divisor is a constant, it must not be zero." appears in the section on integer operations only, rather than for floating points. One or the other is wrong, then.
In light of the fact that division by floating-point 0 is not well-defined as yielding an infinite value, it may be desirable to ban this behaviour and direct users to math.Inf instead. See, however, #10006.

/cc @griesemer

This is working as intended. This is not a "floating-point division" - it's a constant division of arbitrary precision numbers which is evaluated at compile-time. Division by zero is not permitted.
Note that https://play.golang.org/p/SF2MbYsxZ1 which is a float64 division by 0 is accepted and leads to a NaN.
Closing.

PS: See https://golang.org/ref/spec#Constant_expressions for the spec rule:
"The divisor of a constant division or remainder operation must not be zero". It has even an example that's basically this piece of code with different values.


Add "Example aliases" to README

Resolves #301

Added a section for Example aliases in the README.
Removed paths to non-English versions of README.md and retained only the English version.

@kyu08
I've fixed. please check it!


Docs: set push_preview=false

Docs build should still work even if push_preview=false.
push_preview should only affect PR previews. It should have no effect on pushes to master.

Codecov Report

Merging #491 (4648ad1) into dev (31c1c65) will decrease coverage by 0.33%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##              dev     #491      +/-   ##
==========================================
- Coverage   81.88%   81.55%   -0.34%
==========================================
  Files          39       39
  Lines        2932     2901      -31
==========================================
- Hits         2401     2366      -35
- Misses        531      535       +4

Impacted Files
Coverage Δ

src/sources.jl
78.37% <0.00%> (-5.84%)
:arrow_down:

src/composition/models/inspection.jl
95.23% <0.00%> (-4.77%)
:arrow_down:

src/data/datasets.jl
86.11% <0.00%> (-2.78%)
:arrow_down:

src/measures/continuous.jl
97.36% <0.00%> (-2.64%)
:arrow_down:

src/measures/finite.jl
92.97% <0.00%> (-1.94%)
:arrow_down:

src/composition/learning_networks/inspection.jl
81.81% <0.00%> (-0.80%)
:arrow_down:

src/composition/learning_networks/nodes.jl
67.66% <0.00%> (-0.48%)
:arrow_down:

src/hyperparam/one_dimensional_range_methods.jl
91.76% <0.00%> (-0.38%)
:arrow_down:

src/composition/learning_networks/machines.jl
92.03% <0.00%> (-0.21%)
:arrow_down:

src/univariate_finite/methods.jl
79.50% <0.00%> (-0.17%)
:arrow_down:

... and 5 more

Continue to review full report at Codecov.

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

Not convinced. Can you please add a detectable change to the documentation?

Done. I changed "light-weight" to "lightweight" at the end of the docs index page

@DilumAluthge ready to be checked (I merged onto master). I don't see a change on https://alan-turing-institute.github.io/MLJBase.jl/dev/ yet, but let me know if you do.

Looks good to me:

Ah. I was looking at the wrong "light-weight". My bad.
Many thanks.


Incorporate confirmation depth into the derivation pipeline

Closes #81

Codecov Report

Merging #93 (fe70e67) into integration (dba39dd) will decrease coverage by 0.76%.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           integration      #93      +/-   ##
===============================================
- Coverage        45.19%   44.44%   -0.76%
===============================================
  Files              178       30     -148
  Lines             7330     1881    -5449
  Branches          1161      380     -781
===============================================
- Hits              3313      836    -2477
+ Misses            3894     1045    -2849
+ Partials           123        0     -123

Flag
Coverage Δ

cannon-go-tests
?

chain-mon-tests
26.95% <ø> (ø)

common-ts-tests
?

contracts-bedrock-tests
?

contracts-ts-tests
100.00% <ø> (ø)

core-utils-tests
?

sdk-next-tests
41.41% <ø> (ø)

sdk-tests
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 148 files with indirect coverage changes

I'm not getting that error. Can you try the same command on integration and see if it fails there too? If so, I think docker compose build or make golang-docker will build the image that's missing. I have in the past been unable to download the OP stack go builder from the registry, I think it might be private or something

I'm not getting that error. Can you try the same command on integration and see if it fails there too? If so, I think docker compose build or make golang-docker will build the image that's missing. I have in the past been unable to download the OP stack go builder from the registry, I think it might be private or something

Still not able to pull it, but I'm seeing the same issue on integration so probably just a local issue for me. Looks like this image is stored on google cloud instead of the github container registry so could be related to that. Anyways, this shouldn't block this PR.


About Apple silicon remote debug Linux ARM64

I use Apple silicon env , and installed Linux arm64 vm in pd . I want to try to remote debug in my apple silicon env following
: https://github.com/OmniSharp/omnisharp-vscode/wiki/Remote-Debugging-On-Linux-Arm
but it show me that

This is due to two things:

We do not have an Apple M1 supported version of the extension so pipeTransport will not work. Even Support for Rosetta 2 it not yet supported yet.
We do not activate the extension on the remote machine if it is running ARM/ARM64. See https://github.com/OmniSharp/omnisharp-vscode/issues/2771

This is due to two things:

We do not have an Apple M1 supported version of the extension so pipeTransport will not work. Even Support for Rosetta 2 it not yet supported yet.
We do not activate the extension on the remote machine if it is running ARM/ARM64. See https://github.com/OmniSharp/omnisharp-vscode/issues/2771

I hope that it can release soon ............. coz Java / Python  / NodeJS / Go / Rust can debug and run in apple silicon , but .net .................. @WardenGnaw

I hope that it can release soon ............. coz Java / Python  / NodeJS / Go / Rust can debug and run in apple silicon , but .net .................. @WardenGnaw

@WardenGnaw  I update my macOS 11.2 , I can use debug .NET in VSCode, but I think this is Rosetta runtime , I hope OmniSharp team can support it asap ..... coz it is very important for .NET developer .


Add 'ResourceGovernance' note for other properties

The additional properties noted in the section beginning on line 69
are not in the ThreadPool property node, unlike the SchedulingBehavior
property. The only way to discover the correct property node is to
open up the msmdsrv.ini config file for SSAS.
Adding this note and XMLA snippet will make it easier for others to
find and update these settings.

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


set_webhook management command

This PR changes how the webhook and API URLs are treated, to allow local dev environment to use a local Telegram Bot API server:

WEBHOOK_URL becomes an environment variable. If it is not set, it defaults to the ListenMessages view on localhost.

API_BASE_URL is a new environment variable. It points to the local Telegram Bot API server if the script to use it has been created, otherwise it points to the cloud Telegram Bot API server.

The mpact.services.set_webhook() function moves to a management command, and the view is removed. Set the webhook URL with:
$ ./manage-dev set_webhook

For a production environment, this command should be run at the end of the initial deploy.

@hussain-mohammed

No longer relevant


ufomerge.py: Fix handling of missing font path

ufo2._path can be None, which makes Path(ufo2._path) fail.

Will merge once CI has finished.


[wip] Change all patchKey to replaceKey

This PR is a member of a group.

Coverage remained the same at 53.925% when pulling 247f655b41bed8b8a9064a86a3c5ac4b2a66f958 on TomHAnderson:hotfix/patchKey into 6d45064514260162e382a56555873a5a748d1611 on zfcampus:master.

This repository has been closed and moved to laminas-api-tools/api-tools-doctrine; a new issue has been opened at https://github.com/laminas-api-tools/api-tools-doctrine/issues/4.

This repository has been moved to laminas-api-tools/api-tools-doctrine. If you feel that this patch is still relevant, please re-open against that repository, and reference this issue. To re-open, we suggest the following workflow:

Squash all commits in your branch (git rebase -i origin/{branch})
Make a note of all changed files (`git diff --name-only origin/{branch}...HEAD
Run the laminas/laminas-migration tool on the code.
Clone laminas-api-tools/api-tools-doctrine to another directory.
Copy the files from the second bullet point to the clone of laminas-api-tools/api-tools-doctrine.
In your clone of laminas-api-tools/api-tools-doctrine, commit the files, push to your fork, and open the new PR.
We will be providing tooling via laminas/laminas-migration soon to help  automate the process.


Implement Reflect for more mesh data types

          If you feel like it I don't see anything preventing anyone from implementing `Reflect` on `PrimitiveTopology` and `MeshAttributeData`.

Originally posted by @nicopap in https://github.com/bevyengine/bevy/pull/9779#discussion_r1322842957

I attempted this after seeing a user on discord who would have liked to be able to serialize meshes, and it seemed at least somewhat involved.
impl_reflect_for_hashmap doesn't work for BTreeMap, so it seemingly needs a nearly identical impl (without the S type param, and with + Ord on K).
After that it seemed like MeshAttributeData might be another obstacle, or at least it seemed to blow up with errors when attempting to derive Reflect for it.

(I was the one wanting to serialize Meshs)
I'm willing to put in the work to implement a newtype for ser/de meshes, but as far as I can tell the only bevy change required would be to implement an .inner() method on MeshVertexAttributeId. I'm probably going to submit a PR for that, and then make a bevy_serde_mesh crate.


Uncatchable Exception Thrown when bad privateCert used

When the authenticate method is used with an incorrect value passed for privateCert the call to self.signRequest(samlMessage); throws the exception error:0906D06C:PEM routines:PEM_read_bio:no start line.
When this happens rather than triggering a 500 error response the server crashes. Here is a simple app which shows this
const express = require('express');
const app = express();
const passport = require('passport');
const SAMLStrategy = require('passport-saml').Strategy;

const options = {
    "path": "/login/callback",
    "entryPoint": "https://www.example.com",
    "callbackUrl": "https://example.com/login/callback",
    "protocol": "https://",
    "privateCert": "-----BEGIN CERTIFICATE-----\n"+
	"8mvhvrcCOiJ3mjgKNN1F31jOBJuZNmq0U7n9v+Z+3NfyU/0E9jkrnFvm5ks+p8kl\n" +
	"BjuBk9RAkazsU9l02XMS/VxOOIifxKC7R9bDtx0hjolYxgqxPIO5s4rmjj0rLzvo\n" +
	"vQTTTx/tB5e+hbdx922QSeTjP4DO4ms6cIexcH+ZEUOJ3wXiHToJW83SXLRtwPI9\n" +
	"JbWKeS9nWPnzcedbDNZkGtohW5vf32BHuvLsWcl6eFXRSkdX/7+rgpXmDRB7caQ+\n" +
	"2SXVY7ORily7LTKg1cFmuKHDzKTGFIp5/GU6dwIDAQABAoIBAArgFQ+Uk4UN4diY\n" +
	"gJWCAaQlTVmP0UEHZQt/NmJrc9ZVduuhOP0hH6gF53nREHz5UQb4nXB2Ksa3MtYD\n" +
	"Z1vhJcu/T7pvmib4q+Ij6oAmlyeL/xwVY3IUURMxX3tCdPItlk4PEFELKeqQOiIS\n" +
	"7B0DYxWfJbMle3c95w5ruYEr2A+fHCKVSlDpg7uPd9VQ6t7bGMZZvc9tDSC1qPXQ\n" +
	"Gd/WOMXxi+t/TpyVZ6tOcEekQzAMLmWElUUPx3TJ0ur0Zl2LZ7IvQEXXias4lUHV\n" +
	"fnH3akDCMmdhlJSVqUfplrh85zAOh6fLloZagphj/Kpgfw1TZ+njSDYqSLYE0NZ1\n" +
	"j+83feECgYEA2aNGgbc+t6QLrJJ63l9Mz541lVV3IUAxZ5ACqOnMkQVuLoa5IMwM\n" +
	"oENIo38ptfHQqjQ9x8/tEINFqOHnQuOJ/+1xP9f0Me+0clRDCqjGYqNYgmakKyD7\n" +
	"vey/q6kwHk679RVGiI1p+HdoA+CbEKWHJiRxE0RhAA3G3wGAq7kpJocCgYEAxp4/\n" +
	"tCft+eHVRivspfDN//axc2TR6qWP9E1ueGvbiXPXv0Puag0W9cER/df/s5jW4Rqg\n" +
	"CE8649HPUZ0FJT+YaeKgu2Sw9SMcGl4/uyHzg7KnXIeYyQZJPqQkKyXmIix8cw3+\n" +
	"HBGRtwX5nOy0DgFdaMiH0F08peNI9QHKKTBoWJECgYEAyymJ1ekzWMaAR1Zt8EvS\n" +
	"LjWoG4EuthFwjRZ4BSpLVk1Vb4VAKAeS+cAVfNpmG3xip6Ag0/ebe0CvtFk9QsmZ\n" +
	"txj2EP0M7div/9H8y2SF3OpS41fhhIlDtyXcPuivDHu/Jaf4sdwgwlrk9EmlN0Lu\n" +
	"CIMYMz4vtpclwGNss+EjMt0CgYEAqepD0Vm/iuCaVhfJsgSaFvnywSdlNfpBdtyv\n" +
	"PzH2dFa4IZZ55hwgoklznNgmlnyQh68BbVpqpO+fDtDnz//h4ePRYb84a96Hcj9j\n" +
	"AjJ/YxF5f/04xfEsw/wkPQ2FHYM1TDCSTWzyXcMs0gTl3H1qbfPvzF+XPMt+ZKwN\n" +
	"SMNy4SECgYB3ig6t+XVfNkw8oBOh0Gx37XKbmImXsA8ucDAX9KUbMIvD03XCEf34\n" +
	"jF3SNJh0SmHoT62vc+cJqPxMDP6E7Q1nZxsEyaAkKr2H4dSM4SlRm0VB+bS+jXsz\n" +
	"PCiRGSm8eupuxfix05LMMreo4mC7e3Ir4JhdCsXxAMZIvbNyXcvUMA==\n" +
	"-----END CERTIFICATE-----\n",
   };

const strategy = new SAMLStrategy(options, function(profile, done) {});
passport.use('saml', strategy);
app.get('/test', passport.authenticate('saml', { failureRedirect: '/', failureFlash: true }), function(req, res) {
	console.log('!!! done');
	res.redirect('/');
});

app.listen(3000);
console.log('listening on port: 3000');

It would be nice to handle this more gracefully. Let me know what you think. Thanks much.

I went ahead and made a pull request with a simple change that will catch the error and pass it back via the callback instead of throwing the exception. I also added a test with the commit which shows the issue. If this is something you can use then please feel free to pull it in. If there's anything I can do to make the commit better let me know. Thanks again.

@chriswininger Having issues with privateCert, mine looks pretty much like the one in your example above
const PRIVATE_CERT = `-----BEGIN CERTIFICATE-----
abcd
efgh
etcetc
-----END CERTIFICATE-----
`;

What is it about this format that makes it a bad private cert? It appears to have a start line, why is it throwing the PEM_read_bio:no start line error?

I just had the issue and it seemed that adding the BEGIN/END lines would solve it; however, since I was running a lot of tests, it could really have been an issue with the certificate itself.
It is important to accept this pull if it is working because this issue really crashes the server.

For future reference, if you are having trouble figuring out the correct private key format, you can use this little script to test:
  "use strict";
  var fs = require("fs")

  var SAML = require("passport-saml").SAML;

  var saml = new SAML({
      privateCert : fs.readFileSync("./tmp.pem")
  })

  var message = { SAMLResponse: "BOOM" };
  saml.signRequest(message)
console.log(message.Signature)

Using that, I determined that the private key must start with -----BEGIN PRIVATE KEY----- on it's own line. (And -----END PRIVATE KEY----- on it's own line at the end for good measure.)
It doesn't work to put BEGIN PRIVATE KEY on the same line as the rest of the cert, and didn't work to omit it and didn't work to use BEGIN CERTIFICATE instead.
The certificate itself can be on a single line, or presumably will also work with linebreaks.
This behavior is inconsistent with other parts of passport-saml which accept certs on a single line without the header/footer.  The need for the headers here is not currently documented-- I'll work on that.
It also be nice if passport-saml validated the cert formats as soon as they were loaded for faster feedback that something is wrong.

Resolving, since #231 was merged.

I'm seeing a similar issue when my cert has the lines
-----BEGIN CERTIFICATE-----
-----END CERTIFICATE-----
I get the following error:
Error: error:0906D06C:PEM routines:PEM_read_bio:no start line
when I replace CERTIFICATE with PRIVATE KEY to get the lines:
-----BEGIN PRIVATE KEY-----
-----END PRIVATE KEY-----
I get the error:
Error: error:0D0680A8:asn1 encoding routines:asn1_check_tlen:wrong tag
any ideas?

@ZoharLiran Are you using the most recent version of passport-saml?  Check your cert with other certificate checking tools to confirm it valid and in the right format. This does not appear to be a bug in passport-saml, so I'm marking this as closed.


(addRule) Filter for tags within tags

Thanks for the great work on this package.
I would like to apply a rule to certain tags, only if they are within others. For example, I would like to apply a rule to
 tags, but only within  tags.
Here's the rule I have now:
var TurndownService = require('turndown')
var turndownService = new TurndownService()
turndownService.addRule('ruleName', {
     filter: 'td',
     replacement: function (content) {
          return '' + content + '</tdr>'
     }
})
...
turndownService.turndown(content)

How would I apply this rule to
 tags within  tags?
I have tried the following, but it has not worked (the rule is not applied):
turndownService.addRule('newRuleName', {
     filter: 'td p',
     replacement: function (content) {
          return '' + content + '	'
     }
})

This will be easy as soon as we introduce CommonMark contexts, which is a planned major change.
If your intention is to match only the HTML context, then it's still quite easy even with the current version. A slightly modified version can be used to match also the rule (e.g. a HTML table might or might not form a GFM table), but it also requires some more changes to Turndown ATM.
The HTML-only context matching can be something like:
function inHtmlContext(node, selector) {
  let currentNode = node;
  // start at the closest element
  while (currentNode != null && currentNode.nodeType !== 1) {
    currentNode = currentNode.parentElement || currentNode.parentNode;
  }
  return (
    currentNode !== null
    && currentNode.nodeType === 1
    && currentNode.closest(selector) !== null
  );
}

// ...

turndownService.addRule('newRuleName', {
  filter: function(node) {
    return node.nodeName === 'P' && inHtmlContext(node, 'td');
  },
  replacement: function (content) {
    return '' + content + '	'
  }
})

Thanks for the info you provided. I will try it out.


Add an option to have the timepicker on the same page as the calendar

Is your feature request related to a problem? Please describe.
It's not really a problem, just that sometimes when entering a date and time, it's more visually obvious to have both pickers appear on the screen at the same time, so the user sees the date and time at once.  The component's current design is slick and works well when the flow setting is properly configured, but I'd love to have the option to have a unified date and time picker.
Describe the solution you'd like
Have a setting like 'unified-datetime-picker' which would be a boolean.  When set to true, the time picker would appear on the date picker, in place of the clock face icon.  In this mode, the component wouldn't switch between date and time because both are already on the screen.  The appearance of the time picker may need a slight modification , but all of the other functionality for both pickers would be the same as before.
Describe alternatives you've considered
I tried flatpickr, which has this type of interface.  But I prefer using vue-datepicker because it's a better component.
Thanks!

You can use the time-picker-inline prop for that: https://vue3datepicker.com/props/time-picker-configuration/#time-picker-inline

That's great, exactly what I was looking for!  Thank you!

That's great, exactly what I was looking for!  Thanks!
On Thu, Apr 11, 2024 at 4:34 AM Laurens @.***> wrote:

You can use the time-picker-inline prop for that:
https://vue3datepicker.com/props/time-picker-configuration/#time-picker-inline
—
Reply to this email directly, view it on GitHub
https://github.com/Vuepic/vue-datepicker/issues/824#issuecomment-2049198787,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJGHZRZ2SGH2VHA3TLTELP3Y4ZDLHAVCNFSM6AAAAABGBGCBCWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBZGE4TQNZYG4
.
You are receiving this because you authored the thread.Message ID:
@.***>


Rest client 1.2-m1

I am working on OpenTracing instrumentation for rest-client 1.2. To verify the integration I would like to run TCK but I need rest-client implementation based on 1.2-m1 https://github.com/eclipse/microprofile-rest-client/releases/tag/1.2-m1.
Is anybody working on the implementation? When it's going to be done?

@michalszynkiewicz has started working on an implementation, but we don't have a deadline yet

@pavolloffay most of the features are already implemented in this PR: https://github.com/smallrye/smallrye-rest-client/pull/44
One difficulty to work with it might be that it uses a snapshot version of MP Rest Client (because I'm also solving some TCK issues while working on it). I have passing the method in request context left to implement, when I do that I will create a proper PR.

thanks @michalszynkiewicz  I will try it out at the end of this week.


[SQL Migration] Update server name query

This PR updates the query that is used during SKU recommendation to fetch the server name of the current connection, since the file names of the performance data files that it's looking for are derived from the server name. This query is the correct one that is also used by the recommendation NuGet when the files are being written.
This was causing an issue where recommendations would fail in situations like this: https://stackoverflow.com/questions/26097229/servername-vs-serverpropertyservername

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
4 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.01%) to 42.36%

Files with Coverage Reduction
New Missed Lines
%

extensions/notebook/src/jupyter/serverInstance.ts
4
75.5%

Totals

Change from base Build<PHONE_NUMBER>:
-0.01%

Covered Lines:
29424

Relevant Lines:
64623

💛  - Coveralls


MF-662 - Change menu style

What does this do?
Change menu style:

update menu from bootstrap button group to bootstrap nav
highlight selected item

Which issue(s) does this PR fix/relate to?
Resolves #662

Codecov Report

Merging #678 into master will increase coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #678      +/-   ##
==========================================
+ Coverage   86.24%   86.29%   +0.05%
==========================================
  Files          62       62
  Lines        3722     3722
==========================================
+ Hits         3210     3212       +2
+ Misses        355      353       -2
  Partials      157      157

Impacted Files
Coverage Δ

things/service.go
94.15% <0%> (+1.29%)
: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 83cafeb...fbbd546. Read the comment docs.


No source files for linux amd64 on v6.12 release

@tanema you forgot to release the other source files in the latest v6.12 release, now my install script fails on circle ci :(
What needs to be added:
2.43 MBdarwin-amd64.zip
2.13 MBlinux-386.zip
2.3 MBlinux-amd64.zip
2.13 MBwindows-386.zip
2.31 MBwindows-amd64.zip

Because I get the error:
Downloading themekit from github.com//Shopify/themekit/releases/download/v0.6.12/linux-amd64.zip
Installing themekit to /home/ubuntu/.themekit
Traceback (most recent call last):
  File "<stdin>", line 137, in <module>
  File "<stdin>", line 78, in install
  File "<stdin>", line 99, in __unzip
  File "/usr/lib/python2.7/zipfile.py", line 770, in __init__
    self._RealGetContents()
  File "/usr/lib/python2.7/zipfile.py", line 811, in _RealGetContents
    raise BadZipfile, "File is not a zip file"
zipfile.BadZipfile: File is not a zip file

👋  Hey @jonathan-bird this time it wasn't an accident. I have been trying to move the deploy to single source on the CDN. It looks like you are using an old version of the install script so you might want to update with the current one that uses the CDN. If you are not using that script please point your ulrs to: ```
https://shopify-themekit.s3.amazonaws.com/{{ themekitversion }}/darwin-amd64/theme
https://shopify-themekit.s3.amazonaws.com/{{ themekitversion }}/windows-amd64/theme.exe
https://shopify-themekit.s3.amazonaws.com/{{ themekitversion }}/windows-386/theme.exe
https://shopify-themekit.s3.amazonaws.com/{{ themekitversion }}/linux-amd64/theme
https://shopify-themekit.s3.amazonaws.com/{{ themekitversion }}/linux-386/theme

Ohhhhh I see :) yes I'm using v6.1 which tried to find it. Can I use v6.12
then? Just worried about anything acting differently or breaking. Haven't
looked at the script in a while.
Should I expect anything?
Thanks!
On 25 May 2017 11:26 pm, "Tim Anema"<EMAIL_ADDRESS>wrote:

👋 Hey @jonathan-bird https://github.com/jonathan-bird this time it
wasn't an accident. I have been trying to move the deploy to single source
on the CDN. It looks like you are using an old version of the install
script so you might want to update with the current one that uses the CDN.
If you are not using that script please point your ulrs to: ```
https://shopify-themekit.s3.amazonaws.com/{{ themekitversion
}}/darwin-amd64/theme
https://shopify-themekit.s3.amazonaws.com/{{ themekitversion
}}/windows-amd64/theme.exe
https://shopify-themekit.s3.amazonaws.com/{{ themekitversion
}}/windows-386/theme.exe
https://shopify-themekit.s3.amazonaws.com/{{ themekitversion
}}/linux-amd64/theme
https://shopify-themekit.s3.amazonaws.com/{{ themekitversion
}}/linux-386/theme
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Shopify/themekit/issues/398#issuecomment-304009585,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABcKcadXkZKTH6AF9fMKOcSNaPDdJAMhks5r9YGFgaJpZM4Nl8Z4
.

What do you mean you are using 6.1? It seems like you are using the themekit install script which has always grabbed the latests themekit even when it was getting it from github. I am referring to this script https://github.com/Shopify/themekit/blob/master/scripts/install

Nope had been using 6.1 and tried other versions but all were trying to get
6.12.
Its midnight here so I'll try to find the logs tomorrow. But what should I
be using? 6.12 and it'll work?
On 25 May 2017 11:38 pm, "Tim Anema"<EMAIL_ADDRESS>wrote:

What do you mean you are using 6.1? It seems like you are using the
themekit install script which has always grabbed the latests themekit even
when it was getting it from github. I am referring to this script
https://github.com/Shopify/themekit/blob/master/scripts/install
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Shopify/themekit/issues/398#issuecomment-304012029,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABcKcXvDbgfePDBdRHg_F_FgiYMWwVskks5r9YRFgaJpZM4Nl8Z4
.

Again, what do you mean you are using 6.1?
Also yes, there are no significant changes between 6.1 and 6.12, it also seems like you have been testing again the most recent versions anyways with out realizing it.

As in I curl 6.1 not master in the url.
On 26 May 2017 12:25 am, "Tim Anema"<EMAIL_ADDRESS>wrote:

Again, what do you mean you are using 6.1?
Also yes, there are no significant changes between 6.1 and 6.12, it also
seems like you have been testing again the most recent versions anyways
with out realizing it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Shopify/themekit/issues/398#issuecomment-304023360,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABcKcTJqCHJbwq84S1EMRCW6fYTh5mB4ks5r9Y9tgaJpZM4Nl8Z4
.

Okay so that doesn't change the fact that the install script that you are curling looks for the most recent release, which is why it is looking for 6.12. You should be curling from master because no matter what, the install script will always look for the most recent release.

Yeah thats what I thought was happening. Will give it a go in the morning.
Thanks mate
On 26 May 2017 12:31 am, "Tim Anema"<EMAIL_ADDRESS>wrote:
Okay so that doesn't change the fact that the install script that you are
curling looks for the most recent release, which is why it is looking for
6.12. You should be curling from master because no matter what, the install
script will always look for the most recent release.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Shopify/themekit/issues/398#issuecomment-304024836,
or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABcKcS0rTPa8UKAe0KbXMtmJA5n4FODoks5r9ZDKgaJpZM4Nl8Z4
.

👍  Cheers, I am closing this issue since nothing is broken but if you need further support you can ask questions here.

The issue that I keep getting is as follows (permission error on /usr/local/bin/theme). Never used to happen on old versions
curl https://raw.githubusercontent.com/Shopify/themekit/master/scripts/install | python
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

100  1535  100  1535    0     0  24567      0 --:--:-- --:--:-- --:--:-- 45147
Fetching release data
Downloading version v0.6.12 of Shopify Themekit
Traceback (most recent call last):
  File "<stdin>", line 44, in <module>
  File "<stdin>", line 19, in install
  File "<stdin>", line 40, in __download
IOError: [Errno 13] Permission denied: '/usr/local/bin/theme'

curl https://raw.githubusercontent.com/Shopify/themekit/master/scripts/install | python returned exit code 1

Action failed: curl https://raw.githubusercontent.com/Shopify/themekit/master/scripts/install | python

It works if I set the ownership beforehand. But never used to have to do that.
sudo chown -R $(whoami) /usr/local/bin && sudo chmod -R 755 /usr/local/bin

Please refer to the documentation website on the appropriate curl command (I am out of office). This is because theme kit is now installed in /usr/local/bin. A more appropriate location for command line tools.

On May 25, 2017, at 8:39 PM, Jonathan Bird<EMAIL_ADDRESS>wrote:
It works if I set the ownership beforehand. But never used to have to do that.
sudo chown -R $(whoami) /usr/local/bin && sudo chmod -R 755 /usr/local/bin
―
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

Hey @jonathan-bird just checking in. Let me know when you have everything working. 👍

Seems to be working now :)


Telework QA Scripting

Automated testing for Telework

waiting for selenium security review & approval

@MikePSA is reviewing and fabbing up and estimate

This is with Igor for review.

I have re-requested a security review of this tool


Support different addresses for http/ws

Describe the feature
geth default is 8546 for ws and 8545 for HTTP.
atm we're using a single address for both.
TODO
Split this into two separate addresses:
https://github.com/paradigmxyz/reth/blob/f56bb5a022f182009622a33407820976dd4f185f/crates/rpc/rpc-builder/src/lib.rs#L418-L419
Additional context
No response

I would like to attempt this one


fix: node check in chrome browser

Summary
When used in chrome browser, the process.versions variable doesn't exist.

Thanks vm @pjurczynski ! I've merged it and released it as v3.0.2


About the consistency of using tokenizer.model instead of AutoTokenizer with use_fast=False

Hi here 🤗 After playing around a bit with mlx and some of the examples under mlx-examples I was wondering whether using the tokenizer.model i.e. the SentencePieceTokenizer model file, instead of loading the tokenizers via AutoTokenizer with use_fast=False is better, because AFAIK as some examples are relying on a single file only i.e. the tokenizer.model, some configuration details may be missing like e.g. special_tokens that may have been added on top of the default tokenizer. Maybe that's not really relevant for showcasing the examples and I guess it's better in terms of sharing MLX models to have the tokenizer.model within the same repository in the HuggingFace Hub, but was wondering whether there's any downside on this approach that may lead to conflicts with the generation process itself. Thanks in advance!

It would seem to be an issue for me, but I'll still consider this serendipity 😂
I was getting RuntimeError: Internal: src/sentencepiece_processor.cc(1103) [model_proto->ParseFromArray(serialized.data(), serialized.size())] for my Deepseek-Coder-33b model off of HF. Just looked up what the issue was related to and fortunately there was a GH issue thread detailing just that.
I guess this means I can just modify that piece of the puzzle in the Llama file and it'll work? Will report back!

Sigh, well, I give up, that was working to a good degree, just had some trouble first with the tokenizer file, kept trying to use HF remote repo data in lieu of the file path given. Then got that squared away, I believe by using assert from_pretrained=True. (Had use_fast=False in the actual loader of my tokenizer path).
But once that got squared away, had issues with the config.json afterwards. I think that's largely due to deviating from a typical Llama config.json(?)
https://huggingface.co/deepseek-ai/deepseek-coder-33b-instruct/blob/main/config.json
This is what my janky llama.py file ended up looking like. Of course, tried a ton of combinations but I don't know ML technical details, so it was futile. Had no idea which config values correlated.
llama copy.txt

I recommend using the hf_llm example it uses AutoTokenizer and should more cleanly manage tokenization in general. We are moving other examples towards using AutoTokenizer as well.


"Detected use of deprecated base_url property" log message

After start-up on 0.112 I saw this message in my logs:
Detected use of deprecated `base_url` property, use `homeassistant.helpers.network.get_url` method instead. Please report issue to the custom component author for o365 using this method at custom_components/o365/__init__.py, line 40: callback_url = f"{hass.config.api.base_url}{AUTH_CALLBACK_PATH}"

Reporting it as an issue as requested

Oh was going to do a PR for this but it looks like you already fixed this on master. Will leave it open for now since other users will likely see this message and go here to report the same issue. But yea looks like as soon as the next version comes out the problem is resolved 👍


feat: issue FLPATH-591 - Add assessment workflow type and display outputs

This PR provides the capabilities of the Orchestrator plugin to:

detect the type of workflow (infrastructure vs assessment) in SonataFlow and,
group workflows by type in the scaffolder templates.
It then enables a user to:
select and execute an assessment workflow and,
discover the associated infrastructure workflows aka workflow options.

@anludke @RichardW98 would you mind adding description?

@pkliczewski please review the description and advise.
cc @mareklibra

@anludke looks great, thanks


Remove firefox warning

Firefox does support worker modules by default, if the browser has been updated in the past 9 months.
https://caniuse.com/?search=module worker

Thanks!


Improvements

I think I worked around every big issue I could find.

Thank you @evandrocoan.

Hi @evandrocoan would it be OK for you to rebase your branch on top of this repo's master?

I think I did not understand correctly.
There are few ways to integrated my branch on your master:

You can merge this pull request squashing (all my commits would become a single).
You can merge this pull request without squashing (all my commits are kept).
You can rebase this pull request and no merge commit would be created and it would be like I was committing directly to your master.
You can cherry pick only the commits you would like, directly into your master
You can cherry pick only the commits you would like, into some other branch and either merge it, squash it or rebase it into your master.

For me, you can merge this any ways you would like.


Check: integration tests are busted?

This isn't meant to be merged, but to run the integration tests in a specific way to verify whether an error exists.

238516f652467ebb2738f7cb02052723d5d8a179 / https://github.com/scroll-tech/ceno/pull/692 seems to be the first bad commit that fails with:
$ RUST_BACKTRACE=1 cargo run --package ceno_zkvm --example riscv_opcodes -- --start 10 --end 11
    Finished `dev` profile [optimized + debuginfo] target(s) in 0.05s
     Running `target/debug/examples/riscv_opcodes --start 10 --end 11`
thread 'main' panicked at ff_ext/src/lib.rs:53:13:
assertion `left == right` failed
  left: 8
 right: 2
stack backtrace:
   0: rust_begin_unwind
             at /rustc/c94848c046d29f9a80c09aae758e27e418a289f2/library/std/src/panicking.rs:681:5
   1: core::panicking::panic_fmt
             at /rustc/c94848c046d29f9a80c09aae758e27e418a289f2/library/core/src/panicking.rs:75:14
   2: core::panicking::assert_failed_inner
   3: core::panicking::assert_failed
             at /rustc/c94848c046d29f9a80c09aae758e27e418a289f2/library/core/src/panicking.rs:364:5
   4: ff_ext::impl_goldilocks::<impl ff_ext::ExtensionField for goldilocks::structs::GoldilocksExt2>::from_bases
             at ./ff_ext/src/lib.rs:53:13
   5: <transcript::basic::BasicTranscript<E> as transcript::Transcript<E>>::read_challenge
             at ./transcript/src/basic.rs:35:17
   6: ceno_zkvm::scheme::prover::ZKVMProver<E,PCS>::create_proof
             at ./ceno_zkvm/src/scheme/prover.rs:125:13
   7: riscv_opcodes::main
             at ./ceno_zkvm/examples/riscv_opcodes.rs:304:30
   8: core::ops::function::FnOnce::call_once
             at /home/matthias/.rustup/toolchains/nightly-2024-12-06-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.


Input should be disabled if user has no balance for Sell

The slider is disabled but the user is able to input an amount to sell which then also causes the slider to move

Stop slider from moving


theming framework

sketching out themes
current version is here https://uclh-foundry.github.io/FlowEHR-Hitchhiking/
this is a screen shot of the new version

credits to https://www.quantumjitter.com for the approach

thanks

On 20 Feb 2023, at 07:20, Ahmed Al-Hindawi @.***> wrote:
@ahmed-alhindawi approved this pull request.
Looks great - the quantumjitter.com x-msg://3/quantumjitter.com website is very neat.
—
Reply to this email directly, view it on GitHub https://github.com/UCLH-Foundry/FlowEHR-Hitchhiking/pull/18#pullrequestreview-1305205677, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIHXTEQIKMMRURPHAAIYSLWYMLLVANCNFSM6AAAAAAVBGJD2U.
You are receiving this because you authored the thread.


[INLONG-5169][Sort] Fix race condition issue of HBaseSinkFunction metric collection

Prepare a Pull Request

Fixes #5169

Motivation

Fix race condition issue of HBaseSinkFunction metric collection

Modifications
Describe the modifications you've done.
Verifying this change
(Please pick either of the following options)

[x] This change is a trivial rework/code cleanup without any test coverage.

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a follow-up issue for adding the documentation

@yunqingmoswu @thexiay PTAL, thanks.

Maybe we can define a ConcurrentCounter

@yunqingmoswu @thexiay PTAL, thanks.

@yunqingmoswu @thexiay PTAL, thanks.

done

Hi guys, thanks for reviewing. First, I'm sorry that I didn't explain my points behind the PR.
As you can see, all the comments are focused on the scenario of flushing failure. I think we don't need care about the metrics after flushing failure. Because

If flushing fails, the job would falls into failover scenario.
Metric accuracy can not be guaranteed when failover happens. The consistency mode of HBaseSinkFunction is at-least-once. So some of produced records would probably be re-produced again. However the metric collection would not be reverted. All of these records would be counted.
Moreover, nobody knows how many records have been written into HBase Region Server when flushing fails. Flushing of BufferedMutator is not a transactional operation. If I remember correctly, HBase client spawns RPC calls to several Region Server concurrently. Any failure RPC call leads to a global failure. So when failure happens, we don't know how many RPC succeeded. It might be none, some or all records have been flushed successfully.

My points here are:

We have to guarantee the metric accuracy if no failure happens. That's what we do in this PR.
Metric is not accurate if flushing fails, no matter what we do. So we don't need to involve any synchronization of these counters. Just make it as cheaper as possible.
A counter records the number of flushing failure times is meaningful. But I'm a bit confused of the counter name "dirty", so I removed the these ambiguous counters. Maybe we could introduce another counter to record the failure times.

What do you guys think of this? @EMsnap @gong @yunqingmoswu

Hi guys, thanks for reviewing. First, I'm sorry that I didn't explain my points behind the PR.
As you can see, all the comments are focused on the scenario of flushing failure. I think we don't need care about the metrics after flushing failure. Because

If flushing fails, the job would falls into failover scenario.
Metric accuracy can not be guaranteed when failover happens. The consistency mode of HBaseSinkFunction is at-least-once. So some of produced records would probably be re-produced again. However the metric collection would not be reverted. All of these records would be counted.
Moreover, nobody knows how many records have been written into HBase Region Server when flushing fails. Flushing of BufferedMutator is not a transactional operation. If I remember correctly, HBase client spawns RPC calls to several Region Server concurrently. Any failure RPC call leads to a global failure. So when failure happens, we don't know how many RPC succeeded. It might be none, some or all records have been flushed successfully.

My points here are:

We have to guarantee the metric accuracy if no failure happens. That's what we do in this PR.
Metric is not accurate if flushing fails, no matter what we do. So we don't need to involve any synchronization of these counters. Just make it as cheaper as possible.
A counter records the number of flushing failure times is meaningful. But I'm a bit confused of the counter name "dirty", so I removed the these ambiguous counters. Maybe we could introduce another counter to record the failure times.

What do you guys think of this? @EMsnap @gong @yunqingmoswu

As far as I know, the underlying logic of refresh should generate hfile first and then load, then refresh will only have this batch of data either all visible or all lost. If I understand correctly, then after refreshing the statistics, the data obtained will be more accurate, not only for dirty data, but also for normal sync data.

@ifndef-SleePy hello, here define of dirty data is write fail, and we need data records and data size.

Hi guys, thanks for reviewing. First, I'm sorry that I didn't explain my points behind the PR.
As you can see, all the comments are focused on the scenario of flushing failure. I think we don't need care about the metrics after flushing failure. Because

If flushing fails, the job would falls into failover scenario.
Metric accuracy can not be guaranteed when failover happens. The consistency mode of HBaseSinkFunction is at-least-once. So some of produced records would probably be re-produced again. However the metric collection would not be reverted. All of these records would be counted.
Moreover, nobody knows how many records have been written into HBase Region Server when flushing fails. Flushing of BufferedMutator is not a transactional operation. If I remember correctly, HBase client spawns RPC calls to several Region Server concurrently. Any failure RPC call leads to a global failure. So when failure happens, we don't know how many RPC succeeded. It might be none, some or all records have been flushed successfully.

My points here are:

We have to guarantee the metric accuracy if no failure happens. That's what we do in this PR.
Metric is not accurate if flushing fails, no matter what we do. So we don't need to involve any synchronization of these counters. Just make it as cheaper as possible.
A counter records the number of flushing failure times is meaningful. But I'm a bit confused of the counter name "dirty", so I removed the these ambiguous counters. Maybe we could introduce another counter to record the failure times.

What do you guys think of this? @EMsnap @gong @yunqingmoswu

As far as I know, the underlying logic of refresh should generate hfile first and then load, then refresh will only have this batch of data either all visible or all lost. If I understand correctly, then after refreshing the statistics, the data obtained will be more accurate, not only for dirty data, but also for normal sync data.

The HFile way you described is called "bulk loading" [1]. That's not the way worked here. BufferedMutator would not trigger bulk loading, there is another API for bulk loading. It would go through WAL and MemStore to be ingested into Region Server.
Bulk loading also could not guarantee "this batch of data either all visible or all lost", because there might be several HFile involved in the batch operation.
HBase could guarantee consistency in a row, but not cross rows, please check the ACID docs [2], "APIs that mutate several rows will not be atomic across the multiple rows.".

[1] https://hbase.apache.org/book.html#arch.bulk.load
[2] https://hbase.apache.org/acid-semantics.html

Hi guys, thanks for reviewing. First, I'm sorry that I didn't explain my points behind the PR.
As you can see, all the comments are focused on the scenario of flushing failure. I think we don't need care about the metrics after flushing failure. Because

If flushing fails, the job would falls into failover scenario.
Metric accuracy can not be guaranteed when failover happens. The consistency mode of HBaseSinkFunction is at-least-once. So some of produced records would probably be re-produced again. However the metric collection would not be reverted. All of these records would be counted.
Moreover, nobody knows how many records have been written into HBase Region Server when flushing fails. Flushing of BufferedMutator is not a transactional operation. If I remember correctly, HBase client spawns RPC calls to several Region Server concurrently. Any failure RPC call leads to a global failure. So when failure happens, we don't know how many RPC succeeded. It might be none, some or all records have been flushed successfully.

My points here are:

We have to guarantee the metric accuracy if no failure happens. That's what we do in this PR.
Metric is not accurate if flushing fails, no matter what we do. So we don't need to involve any synchronization of these counters. Just make it as cheaper as possible.
A counter records the number of flushing failure times is meaningful. But I'm a bit confused of the counter name "dirty", so I removed the these ambiguous counters. Maybe we could introduce another counter to record the failure times.

What do you guys think of this? @EMsnap @gong @yunqingmoswu

As far as I know, the underlying logic of refresh should generate hfile first and then load, then refresh will only have this batch of data either all visible or all lost. If I understand correctly, then after refreshing the statistics, the data obtained will be more accurate, not only for dirty data, but also for normal sync data.

The HFile way you described is called "bulk loading" [1]. That's not the way worked here. BufferedMutator would not trigger bulk loading, there is another API for bulk loading. It would go through WAL and MemStore to be ingested into Region Server.
Bulk loading also could not guarantee "this batch of data either all visible or all lost", because there might be several HFile involved in the batch operation.
HBase could guarantee consistency in a row, but not cross rows, please check the ACID docs [2], "APIs that mutate several rows will not be atomic across the multiple rows.".

[1] https://hbase.apache.org/book.html#arch.bulk.load [2] https://hbase.apache.org/acid-semantics.html

Thanks for clarifying.

After an offline communication with @yunqingmoswu , we reached an agreement that just keep the origin implementation with thread-safe counter. Because it's bases on production requirement, not technical.

We have to keep the meaningless "dirty" prefix counter till someday the production manager realizes that it's meaningless.
Summing the counter after flushing is better than before flushing although neither of them could guarantee accuracy. Because we don't want to meet the scenario that user asks a question why there exists successful counter in metric system however there is no data in HBase.

please git pull uptream master , git rebase , resolve conflic@ifndef-Sleepy

I've re-created the PR after resolving conflicts.