load schema ui async; use skeleton loading indicator

This is a ui followup to #9741

schemas now load async along with the tables
the AppLoader is removed in favor of individual TableLoader
instead of Loading... text, we use a more modern Skeleton indicator that things are loading

Hopefully this makes the whole thing feel a bit more interactive, and modern, and provides some value to people.
https://user-images.githubusercontent.com/4760722/201197459-2e52db73-661b-4794-88ca-6843e05f719e.mov

@joshigaurava are you able to review this?

I just merged upstream/master to resolve merge conflicts.
I do think this needs one more PR on top of this to throttle this page. This sends 3 requests in parallel for every table (get table size, ideal state, and external view). This likely overwhelms the browser for a bit, and it makes it so even if you click into a table while it's loading, it still has to wait for all of those requests to finish. We could probably load 10 or so tables at a time and use cancellation tokens when you navigate away from the page.
I'm not really a fan of adding another button to load more data. That feels like it's degrading the user experience when we could probably just request data more slowly.

Codecov Report

Merging #9781 (01b889d) into master (47c8f18) will increase coverage by 8.17%.
The diff coverage is 86.45%.

@@             Coverage Diff              @@
##             master    #9781      +/-   ##
============================================
+ Coverage     60.58%   68.75%   +8.17%
+ Complexity     5281     4999     -282
============================================
  Files          1949     1963      +14
  Lines        104632   105028     +396
  Branches      15847    15895      +48
============================================
+ Hits          63389    72214    +8825
+ Misses        36540    27762    -8778
- Partials       4703     5052     +349

Flag
Coverage Δ

integration2
24.39% <0.00%> (-0.05%)
:arrow_down:

unittests1
67.89% <86.45%> (+0.07%)
:arrow_up:

unittests2
15.77% <86.45%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...apache/pinot/common/function/FunctionRegistry.java
86.84% <ø> (ø)

...not/query/planner/logical/RelToStageConverter.java
81.48% <ø> (+1.85%)
:arrow_up:

...che/pinot/query/planner/logical/RexExpression.java
78.66% <ø> (+2.66%)
:arrow_up:

...ache/pinot/query/planner/logical/StagePlanner.java
100.00% <ø> (ø)

...e/pinot/query/runtime/operator/FilterOperator.java
76.00% <ø> (+16.00%)
:arrow_up:

...ery/runtime/operator/operands/FunctionOperand.java
100.00% <ø> (ø)

...query/runtime/operator/MailboxReceiveOperator.java
79.36% <50.00%> (-0.97%)
:arrow_down:

...query/runtime/operator/operands/FilterOperand.java
83.90% <50.00%> (+16.05%)
:arrow_up:

...ot/query/runtime/executor/RoundRobinScheduler.java
87.50% <87.50%> (ø)

...uery/runtime/executor/OpChainSchedulerService.java
95.12% <95.12%> (ø)

... and 286 more

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


Java Demo Issue

when running make rhinojs fails due to a missing cp command
cp rhino/buildGradle/libs/rhino*.jar rhino.jar
usage: cp [-R [-H | -L | -P]] [-fi | -n] [-apvXc] source_file target_file
       cp [-R [-H | -L | -P]] [-fi | -n] [-apvXc] source_file ... target_directory
make: *** [rhino.jar] Error 64

Issue was resolved by manually copying one of the jars
cp rhino/buildGradle/libs/rhino-1.7.13-SNAPSHOT.jar rhino.jar

Running the test locally, I see three jar files generated in the build process.
It probably would suffice to change that line (https://github.com/SheetJS/sheetjs/blob/master/demos/altjs/Makefile#L57) to
cp rhino/buildGradle/libs/rhino-1*.jar rhino.jar


fix: ignore files that are not found

This is needed when files are explicitly passed to
gts. Just ignore them.
This addresses https://github.com/google/ts-style/issues/86

Codecov Report

Merging #87 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master     #87      +/-   ##
=========================================
+ Coverage    99.6%   99.6%   +<.01%
=========================================
  Files           8       8
  Lines         254     256       +2
  Branches       10      11       +1
=========================================
+ Hits          253     255       +2
  Misses          1       1

Impacted Files
Coverage Δ

src/lint.ts
100% <100%> (ø)
: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 11bf7de...01a79bb. Read the comment docs.

Added a test case.

Can someone merge this? I don't seem authorized for that.


Data loss when exiting Atom with unsaved files

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
When exiting Atom with one or more unsaved files, there is no confirmation to exit without saving, and the content of any unsaved files is completely lost.
Steps to Reproduce

Open Atom
Start a new file
Add some content to the file
Exit Atom (e.g, by clicking the "X" icon in the window, or by using File --> Quit)
Re-open Atom
File content is gone!

Expected behavior:
Atom should either automatically save files that have not been saved when closed (e.g, like Sublime Text does by default), or confirm with the user that they would like to exit without saving changes.
Actual behavior:
There is no confirmation to exit, nor is there any automatic saving. This means the content of any unsaved files is lost!
Reproduces how often:
100%
Versions
Atom    : 1.12.7
Electron: 1.3.13
Chrome  : 52.0.2743.82
Node    : 6.5.0
OS: Linux Mint 18 "Sarah", Linux 4.7.5-040705-generic #201609240533 SMP Sat Sep 24 09:35:42 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Thanks for reaching out! This is a duplicate of https://github.com/atom/atom/issues/10474, when an Atom window is opened that has no project folders, the current stable version of Atom (v1.12.9) can close without a confirmation when there are unsaved changes. This has been fixed to present a confirmation dialog in v1.13-beta, see https://github.com/atom/atom/pull/12922 for details. In the situation where there is at least one project folder, the unsaved information is stored as part of the project state.
Thanks again for reporting the problem.


Loading a model returns either an untrained model or broken model

When trying to save a trained model and reload it in a separate python file using
model.save(filepath, save_format='tf') then model = tf.keras.models.load_model(filepath)
I see that the model type has changed, before saving I had a
<tensorflow_decision_forests.keras.GradientBoostedTreesModel object at ... >
after loading I have a
<keras.src.saving.legacy.saved_model.load.GradientBoostedTreesModel object at... >
This model evaluated correctly but if I call model.make_inspector() on the loaded model I have this error
AttributeError: 'GradientBoostedTreesModel' object has no attribute 'make_inspector' This command runs normally for the model that is trained and saved.
My alternative approach was to just save the model weights with model.save_weights(filepath) then load the model weights with model.load_weights(filepath) followed by model.compile(metrics=["binary_crossentropy"])
However, when evaluated this model gives 0s and the following error when I call model.make_inspector()

Traceback (most recent call last):
  File "/home/cb719/Documents/L1Trigger/Tracker/TrackQuality/TrackQuality_package/test.py", line 43, in <module>
    NoDegredation.model.make_inspector()
  File "/home/cb719/miniconda3/envs/tq/lib/python3.11/site-packages/tensorflow_decision_forests/keras/core_inference.py", line 411, in make_inspector
    path = self.yggdrasil_model_path_tensor().numpy().decode("utf-8")
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/cb719/miniconda3/envs/tq/lib/python3.11/site-packages/tensorflow/python/util/traceback_utils.py", line 153, in error_handler
    raise e.with_traceback(filtered_tb) from None
  File "/tmp/__autograph_generated_filegdj2nxzc.py", line 39, in tf__yggdrasil_model_path_tensor
    ag__.if_stmt(ag__.ld(multitask_model_index) >= ag__.converted_call(ag__.ld(len), (ag__.ld(self)._models,), None, fscope), if_body, else_body, get_state, set_state, (), 0)
                                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: in user code:

    File "/home/cb719/miniconda3/envs/tq/lib/python3.11/site-packages/tensorflow_decision_forests/keras/core_inference.py", line 436, in yggdrasil_model_path_tensor  *
        if multitask_model_index >= len(self._models):

    TypeError: object of type 'NoneType' has no len()

I see from #169 that pickling a model is not supported though if it were maybe that would also fix my issues.
Any advice on best practices for saving and loading models would be welcome, I would like to avoid having to retrain a model every time I want to inspect it.
Tensorflow decision forests version: 1.6.0
Python version:  Python 3.11.6 | packaged by conda-forge | (main, Oct  3 2023, 10:40:35) [GCC 12.3.0] on linux

Hi,
this is a known issue, but there is a workaround for most cases.
If your model does not use keras-specifics (e.g. it's not using neural networks preprocessing or model composition), you can create the inspector from the saved model on disk:
# Let's save the model first:
path_to_model = "/tmp/mymodel"
model.save(path_to_model)
# Now create an inspector from the raw YDF model inside our model
insp = tfdf.inspector.make_inspector(os.path.join(path_to_model, "assets"))


UX: unset name results in unhelpful error message

Functions that set a derivation name should provide some manner of checking, the following error is not particularly helpful:
error: The path name '.drv' is invalid: it is illegal to start the name with a period. Path names are alphanumeric and can include the symbols +-._?= and must not begin with a period. Note: If '.drv' is a source file and you cannot rename it on disk, builtins.path { nam.

repro: nix-shell -v --show-trace -E '(import <nixpkgs> {}).writeShellScriptBin "" "asd"'

nowadays no name/pname fails with
error:
       … while calling the 'derivationStrict' builtin

         at <nix/derivation-internal.nix>:9:12:

            8|
            9|   strict = derivationStrict drvAttrs;
             |            ^
           10|

       … in the attrset passed as argument to builtins.derivationStrict

         at «none»:0: (source not available)

       error: attribute 'name' missing


pass allow_ssl_requests_only to storage module

what

Create a flag to require the underlying s3 bucket to only support access via tls

why

AWS Foundational Security Best Practices

/test all

/test all


Can we use TSX other than jsx?

Can we use TSX other than jsx? for creating components?

Hello @arisawali2014 .
Yes, you can. MingleJS doesn't interfere with that. TSX config should be at Vite level.
I actually don't use TSX, so I installed a typical Laravel app with Vite + React in TSX, using the default installer.
This is what it looks it's needed, find below, screenshot and contents:

package.json

...

        "build": "tsc && vite build"
(....)
"dependencies" : {
(....)
        "@types/node": "^18.13.0",
        "@types/react": "^18.0.28",
        "@types/react-dom": "^18.0.10",
        "@vitejs/plugin-react": "^4.2.0",
        "laravel-vite-plugin": "^1.0",
        "react": "^18.2.0",
        "react-dom": "^18.2.0",
        "typescript": "^5.0.2",
        "vite": "^5.0"
(...9
...

ts-config.json

{
    "compilerOptions": {
        "allowJs": true,
        "module": "ESNext",
        "moduleResolution": "bundler",
        "jsx": "react-jsx",
        "strict": true,
        "isolatedModules": true,
        "target": "ESNext",
        "esModuleInterop": true,
        "forceConsistentCasingInFileNames": true,
        "noEmit": true,
        "paths": {
            "@/*": ["./resources/js/*"],
            "ziggy-js": ["./vendor/tightenco/ziggy"]
        }
    },
    "include": ["resources/js/**/*.ts", "resources/js/**/*.tsx", "resources/js/**/*.d.ts"]
}

Hey thanks finally we can use it by tsx or jsx. but one more thing that i need to concern is. how do you use a parent child component across livewire and js/tsx?

https://ui.aceternity.com/components/background-gradient-animation
so i want to use this component. but i don't know how to implement it using minglejs


java sdk changes for bulk import

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

Can you re-run the recordings against WCUS and check those in instead? I believe that's the test region used by our tests in CI, so it may fail otherwise.

Done. Thanks


Composable interfaces

Search Terms
composition interfaces
Suggestion
Right now we can extend an interface with another interface. This syntax is similar to the class inheritance syntax where you extend classes with other classes.
export interface Animal {
  shout: () => void;
}

export interface Human extends Animal {
 think: () => void;
}

What would be awesome is the ability to use composition to describe interfaces.
This would allow us to explain the relationships between interfaces in terms of behaviours rather than inheritance trees. This is model that languages like Go employ
Use Cases
MPJ gives a much better explanation of the use cases than I can
https://www.youtube.com/watch?v=wfMtDGfHWpA
Examples
export interface Shouter {
  shout: () => void
}

export interface Thinker {
  think: () => void
}

export interface Animal {
  ...Shouter
}

export type Human = {
  ...Shouter
  ...Thinker
}

Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
[?] This feature would agree with the rest of TypeScript's Design Goals.

How is that any different than the first example?  It should have some sort of appreciable benefit to warrant additional syntax in my opinion.  Interfaces are allowed by be extended from multiple other interfaces as well, plus other advanced type operators allow all sorts of other strange ways of combining types.

I apologize, I have updated my post to include the template and a more comprehensive example

You can do that already without adding new syntax. The only caveat is that you have to use types instead of interfaces:
export interface Shouter {
  shout: () => void
}

export interface Thinker {
  think: () => void
}

export type Animal = Shouter;
export type Human = Shouter & Thinker;
export type SpecialHuman = Shouter & Thinker & {
    poop: () => void;
};

TIL I am an Omit<SpecialHuman, "think">.

Being serious now: it's not clear what differences you have in mind. Perhaps its the notion that extending a type implies perfect subtype compatibility in the presence of conflicts.
If the aversion is to the compatibility checks (which I think are valuable), then do intersection types as above model what you have in mind?

I don't understand the example in OPs original post, because here it is using current TypeScript.

@alshdavid hasn't actually verified whether they have something else in mind, so let's not pile up here. If the existing features solve their problem, then we can close the issue.

The existing features solve their problem

The existing features do solve the problem. Union types do facilitate this technically.
I've been thinking a lot about what I am trying to solve with this and I think I am directing my attention at the wrong language feature.
I'll close this but just to continue the discussion I'd love to get some thoughts from TypeScript contributors.
Using factory functions and leveraging the type system is challenging in TypeScript. Are factory functions something that is generally discouraged with TS?

I worked with factory functions and composition in TypeScript for quite a while.  There have been some improvements in the language since that time, but really the challenge was more that ECMAScript really hasn't tackled traits and composition as part of the language specification.  It was part of the original Harmony specification, which is where the class syntax came from, but traits were too much for TC39 to swallow in one go, so they put all that on hold, getting the MVP through.  There has been off and on again talking about more syntactical support, but I don't believe currently there is really anyone championing it.
The vast majority of the TypeScript compiler is factory functions, so they are certainly supported.  We eventually gave up on factory functions when the TypeScript team relaxed some constraints in the compiler and made traits/mixins realistic, and ever since then, it has just been easier to embrace the class constructor.  Using a mixin class would look something like this:
type Constructor<T> = new (...args: any[]) => T;

class Animal {
  shout() {};
}

interface ThinkerMixin {
  think(): void;
}

function ThinkerMixin<T extends Constructor<Animal>>(Base: T): T & Constructor<ThinkerMixin> {
  return class Thinker extends Base {
    think() {}
  };
}

const Thinker = ThinkerMixin(Animal);

const myThinker = new Thinker();

myThinker.shout();
myThinker.think();

For the most part the types just flow through, the only thing you have to really deal with is that you have to provide an interface for what each mixin function would mixin, but once you have done that, the types just flow through.

Thanks for the insight. Do you have any thoughts around the implementation of object declaration in the form of Structs - such as in Go (Golang)?
type Person = {
    name: string
    walk: (this: Person, steps: number) => void
}

function walk(this: Person, steps: number) {
    console.log(this.name, 'walked', steps, 'steps')
}

function newPerson (name: string): Person {
    return {
        name,
        walk
    }
}

const person = newPerson('marvin')
person.walk(8)

Which would be expressed like this in Go
type Person struct {
	Name string
}

func (p *Person) Walk(steps int) {
	fmt.Println(p.name + " walked " + steps + "steps")
}

func newPerson(name string) *Person {
	return Person{
		Name: name,
	}
}

const person = newPerson("marvin")
person.Walk(8)

Differences are that the receiver is defined behind the function name with an arbitrary, rather than being a this as a first parameter. The struct itself is a type, rather than being a factory function that accompanies a type.
Thoughts?

This behaviour, of having to maintain a seperate interface, is finally what led us away from factory functions and just embrace class.  It really isn't TypeScript as much as JavaScript/ECMAScript is a prototypical language, of which class is arguably bad/confusing syntactic sugar for a constructor function which instantiates a prototype.
The only "trick" to make it more self sustaining would be something like this, but this could be really awkward:
const PersonPrototype = {
  name: "" as string,
  walk
};

type Person = typeof PersonPrototype;

function walk(this: Person, steps: number) {
  console.log(this.name, 'walked', steps, 'steps');
}

function createPerson(name: string): Person {
  const person = Object.create(PersonPrototype) as Person;
  Object.assign(person, { name });
  return person;
}

const person = createPerson('marvin');
person.walk(8);


Deletes storage on component deletion

What type of PR is this?
This PR deletes storage belonging to a component on component deletion
/kind bug
What does does this PR do / why we need it:
Fixes storage deletion on odo delete
Which issue(s) this PR fixes:
Fixes #2529
How to test changes / Special notes to the reviewer:

create a component
add a storage to it
delete the component
push again and check if we face any issues.

/refresh

/lgtm


How to get the string without backslash?

Hi, I'm not sure if it's swift problem or the pod. When I do
XML.description

it was returning escape character "". I tried to do replacingOccurrences(of: "", with: "") but no luck. I looked SOF can't find answers either.

Hi, I'm guessing you got this resolved, but this would be because of the content in the XML itself. SWXMLHash will return any string characters found and won't do any special parsing on anything that isn't XML characters. Everything else would be considered text.


systemd-boot: New /boot data format

The systemd-boot-builder.py script stores information about the profile, generation, and specialisation in the file name of loader entry .conf files. This has led to some issues where these names are improperly generated or parsed, e.g. the recent revert of boot counting: #334526.
I suggest a new format for these entry files. There should be a JSON file of a format something like this:
{
  "$profile": {
    "$generation": {
      "entry.conf": "$path_to_entry.conf",
      "files": [
        "$path_to_kernel"
        "$path_to_initrd"
        ...
      ]
    }
  }
}

This will make it easier to identify the locations of entry files as well as kernels, initrds, etc. to garbage collect.
When boot counting is reintroduced, the entry file name will refer to the name if it did not have any boot count included.
The entry name becomes arbitrary, giving us slightly better control over sorting.
This JSON file could have an ever-increasing number in its name, so that updates can be atomic without breaking the ability to GC the old one. When updating, make the new JSON file with the higher number, add the new files to the ESP, GC the old files from the ESP, and finally remove the old JSON file with the lower number. This way all the files that could need GC'ing will always have their corresponding JSON file present.
This is just a rough idea. And migration is going to be the tricky part. @alois31 recommended taking inspiration from when lanzaboote had to do something similar:

The migration: https://github.com/nix-community/lanzaboote/pull/204
Rewriting thin UKI stubs: https://github.com/nix-community/lanzaboote/pull/302

/cc @JulienMalka @Mic92 @r-vdp @NixOS/systemd

Don't we already have the bootspec which fulfils a similar function?

It sounds to me we should (finally) rewrite systemd-boot-builder to properly use bootspec instead.  I think there is some prior work for this in the lanzaboote repo if memory serves me well

systemd-boot-builder does use bootspec. I think the difference here is that essentially the bootspec is stateless whereas if I understand correctly this additionnal data would be stateful,

@Atemu, @arianvp Yes, the idea here is not to encode the same information as bootspec. It's instead to manage the stateful aspects of where and how we store boot entries in the ESP.


Exposing state-store.js

Would you consider exposing the StateStore class in a seperate npm module?
https://github.com/atom/atom/blob/f6352cb47bb579e0848d1d3aa73a573cd3585d98/src/state-store.js
I think it'd be really useful for other projects in general, as it essentially provides a non-blocking async alternative to localStorage. I've looked around and can't seem to find anything that simplifies the IndexedDB interface to a key-value store like what's been done here!

@rageandqq
https://www.npmjs.com/package/focalstorage is the close/best that I found from a cursory search.
It's more-or-less the localStorage API but powered by IndexedDB.

As Atom more-or-less re-implements this.. does it make sense to just use this guys package instead of the home-rolled code in atom?


MoRA support

Copied from the official implementation at https://github.com/kongds/MoRA by @kongds
Paper: https://arxiv.org/abs/2405.12130

I just tried training a model using this code. Admittedly a bit of patchwork needed to get it to work and I may have fatfingered something somewhere.
The resulting adapter was, however, broken.
Here is an example of it merged with failspy's l3-8b abliterated v3.0:
./main --temp 0.5 -t 11 -ngl 25 -c 2048 -n 512 -m ./mora-output-q8_0.gguf -p "<|begin_of_text|><|start_header_id|>user<|end_header_id|>

What are some fun facts about pigs?<|eot_id|><|start_header_id|>assistant<|end_header_id|>

"
Log start
main: build = 3083 (adc9ff38)
main: built with cc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0 for x86_64-linux-gnu
main: seed  =<PHONE_NUMBER>
[...]
▅ <|begin_of_text|><|start_header_id|>user<|end_header_id|>

What are some fun facts about pigs?<|eot_id|><|start_header_id|>assistant<|end_header_id|>

What are some fun▅▅▅ [end of text]

In an existing Silly Tavern chat, when doing a regeneration, it outputted "Thelisten" and then stopped.
I initially did a training run with constant lr 1e-4, but eval loss did not drop as I wanted so I dropped to 6e-5 and it got a bit better. Are there other gotchas with doing MoRA training compared to LoRA that could have caused this?

I just tried training a model using this code. Admittedly a bit of patchwork needed to get it to work and I may have fatfingered something somewhere.
The resulting adapter was, however, broken.
Here is an example of it merged with failspy's l3-8b abliterated v3.0:
$ ./main --temp 0.5 -t 11 -ngl 25 -c 2048 -n 512 -m ./mora-output-q8_0.gguf -p "<|begin_of_text|><|start_header_id|>user<|end_header_id|>

What are some fun facts about pigs?<|eot_id|><|start_header_id|>assistant<|end_header_id|>

"
Log start
main: build = 3083 (adc9ff38)
main: built with cc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0 for x86_64-linux-gnu
main: seed  =<PHONE_NUMBER>
[...]
▅ <|begin_of_text|><|start_header_id|>user<|end_header_id|>

What are some fun facts about pigs?<|eot_id|><|start_header_id|>assistant<|end_header_id|>

What are some fun▅▅▅ [end of text]

No matter what I do, the output ends up repeating my prompt and ending at some point a few tokens in.
In an existing Silly Tavern chat, when doing a regeneration, it outputted "Thelisten" and then stopped.
I initially did a training run with constant lr 1e-4, but eval loss did not drop as I wanted so I dropped to 6e-5 and it got a bit better. Are there other gotchas with doing MoRA training compared to LoRA that could have caused this?
Here's another example where I forgo the llama 3 template entirely:
$ ./main --temp 2.5 -t 11 -ngl 25 -c 2048 -n 512 -m ./mora-output-q8_0.gguf -p "What are some fun facts about pigs?
[...]
▅ What are some fun facts about pigs?

 activityapeuntoape лет lowprocess▅anaprocess overse H activity activity

Hello, thanks for your interesting to our works. But this code has some bugs in implementation like this line.
                x_m, x_n = x[..., :mm], x[..., nn_:]

which should be
                x_m, x_n = x[..., :mm], x[..., mm:]

Could you try the original version?

Hello, thanks for your interesting to our work. But this code has some bugs in implementation like this line.
                x_m, x_n = x[..., :mm], x[..., nn_:]

which should be
                x_m, x_n = x[..., :mm], x[..., mm:]

Could you try the original version?

This line does not affect me, as I did not change the mora_type from its default (1). The above code only applies to mora_type=2 or 3. Correct me if I'm wrong. (I did see this and put in a breakpoint to see if it would reach the code in question but it did not.)

Hello, thanks for your interesting to our work. But this code has some bugs in implementation like this line.
                x_m, x_n = x[..., :mm], x[..., nn_:]

which should be
                x_m, x_n = x[..., :mm], x[..., mm:]

Could you try the original version?

This line does not affect me, as I did not change the mora_type from its default (1). The above code only applies to mora_type=2 or 3. Correct me if I'm wrong. (I did see this and put in a breakpoint to see if it would reach the code in question but it did not.)

Yes, it is for mora_type=2 or 3. Could you provide the settings of MoRA?

I think my comments above can be disregarded for the purposes of this PR. The dataset I used was most likely not suitable for MoRA training. I intend to play with it more but haven't had time yet.
It would be a pity if this dragged out indefinitely.


Support building DbtDag without setting paths in ProjectConfig

Previously, users were unable to run a DbtDag or DbtTask group where the following was used:

RenderMode.DBT_LS
ExecutionConfig(dbt_project_path)
RenderConfig(dbt_project_path)

This scenario can be helpful when using ExecutionMode.KUBERNETES or other similar ones and was found out during: https://github.com/astronomer/astronomer-cosmos/pull/1297

There are two types of checks failing in this PR:

Related to the existing latency when building (3.8, 2.6) dependencies, that is addressed in #1297
Issue related to a dbt conflict with the protobuf version:

  File "/home/runner/work/astronomer-cosmos/astronomer-cosmos/venv/lib/python3.11/site-packages/dbt_common/events/base_types.py", line 139, in msg_from_base_event
    "msg": event.message(),
           ^^^^^^^^^^^^^^^
  File "/home/runner/work/astronomer-cosmos/astronomer-cosmos/venv/lib/python3.11/site-packages/dbt/events/types.py", line 2059, in message
    return f"Resource report: {self.to_json()}"
                               ^^^^^^^^^^^^^^
  File "/home/runner/work/astronomer-cosmos/astronomer-cosmos/venv/lib/python3.11/site-packages/dbt_common/events/base_types.py", line 98, in to_json
    return MessageToJson(
           ^^^^^^^^^^^^^^
TypeError: MessageToJson() got an unexpected keyword argument 'including_default_value_fields'

https://github.com/dbt-labs/dbt-core/issues/9759
The current PR causes neither issue.
I rebased PR  #1297 using this branch and confirmed this second issue is also solved in that PR.


Task512: Twitter Emotion Classification

Given a Twitter post, classify the post's emotion to six classes ('sadness', 'joy', 'love', 'anger', 'fear', 'surprise')
Emotion classes are balanced:
love        572
fear        572
anger       572
joy         572
surprise    572
sadness     572

The task looks good to me, the definition might be a bit redundant, you may change it to something like:
"Definition": "In this task, you are given Twitter posts. Your task is to label the post's emotion (as expressed by the user) as sadness, joy, love, anger, fear, or surprise.",

The task looks good to me, the definition might be a bit redundant, you may change it to something like:
"Definition": "In this task, you are given Twitter posts. Your task is to label the post's emotion (as expressed by the user) as sadness, joy, love, anger, fear, or surprise.",

Done, thanks!

Looks great! Thanks!


Add a task to the pipeline to index all scraped fulltexts

Description
This PR aims to add a step to the pipeline to index all pdf fulltexts, parsed from policy documents, into an elasticsearch database.
To this purpose:

Add the import_fulltext_s3 script, usable out of airflow
Add a task in airflow using this script
Add the task to the policy dag

Also:

Fix a minor import path issue (.pdf_parser.pdf_parse -> .pdf_parse)
Fix the return of the epmc index method (Removes a /2, as the instruction and data are one element of the list, not two)
Add the OPENRESEARCH_S3_PREFIX variable again to docker compose, as it was needed by the index epmc task

Type of change
Please delete options that are not relevant.

[x] :sparkles: New feature

How Has This Been Tested?
make test
make docker-test
Local runs using Docker, docker-compose (@10Gb RAM and 2 VCPU)

Card created in trello, merging this


Visual/UI positioning bug with Plugin & Theme Repo

Theme: Soft X
Discord build: Stable
OS: Windows 10
Summary: When opening the Plugin Repo and Theme Repo, it is visually off center or off screen. This appears to happen if you move to the repos from any source (BD top banner, settings etc). When in the bugged state, you can still click outside and exit, or click on a different settings menu button (such as Themes, Plugins, Updates, Game Overlay, etc)
Note: Confirmed via the BD Data Visualization Plugin Status Tracker that both repos are working
Steps to Repro:

Open Plugin Repo / Theme Repo
Observe alignment

Theme Repo:

Plugin Repo:

This doesn't seem to be an issue anymore on betterdiscord


Handle DateTime serializing (Fixes #378)

Add handling for parsing date and time objects when serialising a Map<K,V> to a JSON String.

Thanks for your pull request. Is this your first contribution to a Snowplow open source project? Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
:memo: Please visit https://docs.snowplowanalytics.com/docs/contributing/contributor-license-agreement/ to learn more and sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

All done and signed :)
On Wed, Feb 7, 2024 at 9:41 AM Snowplow CLA bot @.***>
wrote:

Thanks for your pull request. Is this your first contribution to a
Snowplow open source project? Before we can look at your pull request,
you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit
https://docs.snowplowanalytics.com/docs/contributing/contributor-license-agreement/
to learn more and sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll
verify. Thanks.
—
Reply to this email directly, view it on GitHub
https://github.com/snowplow/snowplow-java-tracker/pull/379#issuecomment-1931651880,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZM4AMPV7BR5XWCHPMXLYDYSND55AVCNFSM6AAAAABC5PQRPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZRGY2TCOBYGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thanks a lot for the contribution @stephen-murby! We will review and release this in the next version of the tracker.


iron:router v1 support eta?

Just curious if you are still working on this project and if so when you think 0.5 will land?

Yes, I'd need support for iron router 1 as well :)

See #19


Where would I get the flow parameter to feed into dense_image_warp?

Not sure how to utilize Dense warp flow operation.
I know there is a Dual_TVL1 function in cv, but is there something similar in tensorflow that I can utilize?
Thank you @WindQAQ

Hi, the short answer is no. There is no function that could generate optical flow between two frames like DUAL_TVL1 at least in addons. But I think you could generate flows with other packages (e.g. opencv) and feed them into dense_image_warp. That will also work fine. It's also welcome to contribute such functionality to addons! Thank you for asking.

Maybe my lack of familiarity with optical flow. Then what would be the input to the flow parameter of the dense_warp_flow function? Or is it output from cv.Dual_TVL1, cv.calcOpticalFlowPyrLK, calcOpticalFlowFarneback. if so which of these is best to use? also I would just be throwing this into a py_function.
Also found this, side note:
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/examples/android/jni/object_tracking/optical_flow.cc

Hmm, I'm not familiar with optical flow either... But the flow argument for dense_image_warp is a vector field indicating the direction that each pixel should follow. I should have some time to make an example for this after the importing issue is fixed... Maybe that could help you and the community understand how to use it.

Close this because we already had https://github.com/tensorflow/addons/blob/master/examples/image_ops.ipynb.

@WindQAQ I haven't look at a way to implement optical flow yet in tensorflow. However, the opencv method you mentioned uses cpu causing a some delay in time. I noticed there is a GPU implementation lurking, however that conflicts with tensorflow. Would definitely be a useful operation to have given its usage in video processing for activities.


Remove tags, make channel explicit part of a version, and add unstable attribute to channel

Version tags should be fully replaced with the already existing channel implementation to unify version metadata handling and make data accessing as well as assumptions about certain builds more explicit/obvious.
Version tags currently hold a version's channel, duplicated data about platforms, and whether it's unstable.
To replace them, we need to do the following:

The channel of a version should be stored in the version directly
Channels receive the extra attribute unstable (possibly more like invite-only in the future, set through a checkbox on channel creation/editing)
Platform versions can be accessed over the version and parsed as version ranges

I think we should just get rid of unstable and authors can make a channel for that right?

Fixed in https://github.com/HangarMC/Hangar/commit/f503d64a62dcb72a8018063238af5b2d44d23f6b, https://github.com/HangarMC/Hangar/commit/f58c1f301134a28648825eee74af4dcbb3de1a02


Cosmatic Drip ~ INTERMISSION 1

About the PR
An intermission from the typical departmental drip updates. PR Adds two new jumpsuits in the form of the Casual Detective and Blue Formal suit, with matching jackets, and a red and blue bowtie.
Why / Balance
Drip, need I say more?
Technical details
RSI and YAML sprites, nothing out of the ordinary
Media

Requirements

[x] I have read and I am following the Pull Request Guidelines. I understand that not doing so may get my pr closed at maintainer’s discretion
[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

Added: New casual detective fatigues and matching Forensics Jacket, arriving, on the scene.
Added: A blue formal suit and jacket, waistcoat can be folded away if desired.
Added: Red and Blue bowties are now available in a threadvend near you.
Added: Security now have their own departmental bandana and a new greatcoat.

Greatcoat and bandana still needs loadouts / secdrobe

there we go :)


Load the PayPal button also on document.readyState === 'interactive' along with 'complete'

Description
The function window.payPalCheckoutReady is only executed once the PayPal script has ascertained that document.readyState === 'completed'

According to the spec for document.readyState the ‘complete` status is only ever set when all sub-resources have completed loading. So it’s completely possible for an image, or unrelated JavaScript file to be still loading, but the page to be otherwise completely usable.
In some context, when loading other resources from CDN that may be blocked in certain parts of the world, the request can be timing out / taking a long time to respond. This will delay document.readyState === ‘completed’ which has the side-effect of making PayPal unusable.
Proposed solution
Check for document.readyState === ‘complete’ || ‘interactive’

I'm totally ok if you want to pr this in to help with legacy integrations -- but right now we're not recommending that merchants use window.paypalCheckoutReady for any new integrations. Instead, if they just call paypal.Button.render(), the button will wait until the document (and container element) is ready before it renders.

Thanks Daniel. I see the document state is checked inside the isDocumentReady function. If this is updated to return true also when the state is interactive, will this affect also new integrations? What do you think of accepting as a ready state also interactive as well as complete?

Given that this function is only used for old v3 integrations, I'm leaning in the direction of letting it lie for now. Don't want to accidentally break any old integrations with any race conditions, and paypal.Button.render() should be much snappier for merchants who want to update.


RBAC section missing content

At https://docs.microsoft.com/en-us/azure/security/fundamentals/identity-management-overview#rbac, it states "The following lists four fundamental built-in roles. The first three apply to all resource types." but then there is no list of four items.

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

ID: 4c24e0e2-d91c-e902-1fc3-8a5443f96740
Version Independent ID: a51cb910-d3fe-4106-ab88-090272cc26c1
Content: Azure security features that help with identity management
Content Source: articles/security/fundamentals/identity-management-overview.md
Service: security
Sub-service: security-fundamentals
GitHub Login: @TerryLanfear
Microsoft Alias: terrylan

@Mirend
Thanks for your feedback! We will investigate and update as appropriate.

Thanks! I made a pull request to add the missing roles: https://github.com/MicrosoftDocs/azure-docs-pr/pull/111208
They're also listed in this article. https://docs.microsoft.com/en-us/azure/role-based-access-control/overview
CC: @TerryLanfear

@MarileeTurscak-MSFT - Thanks for addressing this issue! Instead of adding the missing roles, I think it would be better to delete the two sentences creating the confusion: "The following lists four fundamental built-in roles. The first three apply to all resource types." Under "Learn more" we link to the article that lists the roles.


Captive Portal: "Allowed MAC-Address" ignored

Hi.
There's a problem with our Captive Portal and the Whitelist for the MAC-addresses.
Since one the last update the whitelisted MAC-addresses are ignored.
The same problem was reported here last year.
Another problem:
The list -> Service: Captive Portal: Sessions is empty now but I found this error-message in the Logfiles:
tail /var/log/configd/latest.log
Script action failed with Command '/usr/local/opnsense/scripts/OPNsense/CaptivePortal/listClients.py /zoneid '0' /output_type 'json'' returned non-zero exit status 1. at Traceback (most recent call last):    File "/usr/local/opnsense/service/modules/actions/script_output.py", line 44, in execute subprocess.check_call(script_command, env=self.config_environment, shell=True,    File "/usr/local/lib/python3.9/subprocess.py", line 373, in check_call      raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '/usr/local/opnsense/scripts/OPNsense/CaptivePortal/listClients.py /zoneid '0' /output_type 'json'' returned non-zero exit status 1.
(often repeated)
Can anybody confirm this?
Versions: 	 OPNsense 24.1.6-amd64 FreeBSD 13.2-RELEASE-p11 OpenSSL 3.0.13

temporary solution until it is fixed:
https://forum.opnsense.org/index.php?topic=19012.0


Consider using page header+footer for slides

Having some text that cannot be manually split over multiple pages like, e.g., a bibliography (not yet working with typst-slides but hopefully soon TM https://github.com/typst/typst/issues/785).
I experimented a bit, and this seems to work:
#style(styles => {
    let header = block(
        width: 100%,
        inset: (x:.5em, y:.7em),
        stroke: (bottom: 1mm + red),
        grid(columns: (1fr, 1fr),
            image("logo.svg", width: 2cm),
            align(right)[Header]
        )

    )
    let footer = block(
        width: 100%,
        inset: (x:.5em, y:.7em),
        stroke: (top: 1mm + red),
        align(right)[Footer]
    )
    page(width: 5cm, height: 5cm, margin: (x: 3%,
      top: measure(header, styles).height + .5em,
      bottom: measure(footer, styles).height + .5em),
      header: header, header-ascent: .5em,
      footer:footer, footer-descent: .5em,
      lorem(50))
})

Currently, stuff like that breaks the layouting:

though this would require a theme redesign as mentioned in https://github.com/andreasKroepelin/typst-slides/issues/41#issuecomment-1565306723

I actually used header and footer in the beginning but then felt that theme design is much simpler if every piece of layout is just handled by the theme author. But you are right that this fails for content that doesn't fit on one slide... As you already remarked, this is strongly tied to rethinking how theming should work. I'll have some long travels soon, hopefully I'll find some time!


The requested file (go1.13.7.linux-amd64.tar.gz) is unknown to the buildpack!

Getting the error shown in title when trying to deploy my golang REST API. I'm doing this through github, so I have my heroku linked to my github account. It's using my private repo.
I am using the community manage dep https://github.com/golang/dep to package my app. Here is my current Gopkg.toml setup:
[metadata.heroku]
  root-package = "NIGHTLYAPI"
  go-version = "go1.13.7"
  install = [ "./..." ]

[[constraint]]
  name = "github.com/go-sql-driver/mysql"
  version = "1.5.0"

[[constraint]]
  name = "github.com/gorilla/mux"
  version = "1.7.3"

[prune]
  go-tests = true
  unused-packages = true

And here is the full log when trying to deploy my branch:
-----> Go app detected
-----> Fetching jq... done
-----> Fetching stdlib.sh.v8... done
-----> Fetching tq... done
-----> New Go Version, clearing old cache
-----> Installing go1.13.7
 !!
 !!    The requested file (go1.13.7.linux-amd64.tar.gz) is unknown to the buildpack!
 !!
 !!    The buildpack tracks and validates the SHA256 sums of the files
 !!    it uses. Because the buildpack doesn't know about the file
 !!    it likely won't be able to obtain a copy and validate the SHA.
 !!
 !!    To find out more info about this error please visit:
 !!        https://devcenter.heroku.com/articles/unknown-go-buildack-files
 !!
 !     Push rejected, failed to compile Go app.
 !     Push failed

Unfortunately, the link it provides is a WIP so there is nothing for me to see.

I guess it doesn't work with the version i published? I changed my file to say go-version = "go1.12.0" and it worked.


Unassembled | failed to read current commit information with git rev-parse --is-inside-work-tree

Help me to figure out Docker
root@AndrijZyn:/home/andrijzyn/docker_test/getting-started-todo-app# docker compose watch
[+] Running 36/3
 ✔ proxy Pulled                                                           43.4s
 ✔ mysql Pulled                                                           54.2s
 ✔ phpmyadmin Pulled                                                      51.2s
[+] Building 76.4s (13/18)                                                       docker:default
 => [client internal] load build definition from Dockerfile                                0.2s
 => => transferring dockerfile: 3.30kB                                                     0.0s
 => [backend internal] load build definition from Dockerfile                               0.1s
 => => transferring dockerfile: 3.30kB                                                     0.0s
 => [backend internal] load metadata for docker.io/library/node:20                         1.8s
 => [backend internal] load .dockerignore                                                  0.1s
 => => transferring context: 52B                                                           0.0s
 => [client internal] load .dockerignore                                                   0.1s
 => => transferring context: 52B                                                           0.0s
 => [client base 1/2] FROM docker.io/library/node:20@sha256:1ae9ba874435551280e95c8a8e74  55.1s
 => => resolve docker.io/library/node:20@sha256:1ae9ba874435551280e95c8a8e74adf8a48d72b56  0.1s
 => => sha256:383ffd6aa27c8e1306abaa608746f2b3d5e152c791c126bc4b54b37a045 2.49kB / 2.49kB  0.0s
 => => sha256:ca4e5d6727252f0dbc207fbf283cb95e278bf562bda42d35ce6c9195 49.55MB / 49.55MB  22.7s
 => => sha256:10d643a5fa823cd013a108b2076f4d2edf1b2a921f863b533e83ea5e 64.14MB / 64.14MB  28.0s
 => => sha256:1ae9ba874435551280e95c8a8e74adf8a48d72b564bf9dfe4718231f214 6.41kB / 6.41kB  0.0s
 => => sha256:1a8e51cfa7a515f1fe4439430880590c19d07eb19af434edc8a68951b2c 6.60kB / 6.60kB  0.0s
 => => sha256:30b93c12a9c9326732b35d9e3ebe57148abe33f8fa6e25ab76867410b 24.05MB / 24.05MB  4.0s
 => => sha256:d6dc1019d7935fe82827434da11bf96cf14e24979f8155e73b7942 211.24MB / 211.24MB  35.6s
 => => extracting sha256:ca4e5d6727252f0dbc207fbf283cb95e278bf562bda42d35ce6c919583a110a0  4.5s
 => => sha256:ea8e6f2ca326ab8466ac3b0fb5c871248c2defd8b21329ec0eb28cf59d 3.32kB / 3.32kB  22.9s
 => => sha256:19951d6e9461aa228a4a0bf32a03da467d67bc48ad4983f8134c44b5 48.08MB / 48.08MB  34.8s
 => => extracting sha256:30b93c12a9c9326732b35d9e3ebe57148abe33f8fa6e25ab76867410b0ccf876  1.2s
 => => sha256:247e8d31d16f1031563959c6af448df7280c978b968966db4b8b2b4e6d 1.25MB / 1.25MB  28.8s
 => => sha256:282ebe8f0e4864f0231f3b647e3417c38d85b9646a1a35820649c218a56619 447B / 447B  29.0s
 => => extracting sha256:10d643a5fa823cd013a108b2076f4d2edf1b2a921f863b533e83ea5ed8d09bd4  5.6s
 => => extracting sha256:d6dc1019d7935fe82827434da11bf96cf14e24979f8155e73b794286f10b7f0  13.5s
 => => extracting sha256:ea8e6f2ca326ab8466ac3b0fb5c871248c2defd8b21329ec0eb28cf59dc8efe2  0.0s
 => => extracting sha256:19951d6e9461aa228a4a0bf32a03da467d67bc48ad4983f8134c44b557bcbbd4  4.4s
 => => extracting sha256:247e8d31d16f1031563959c6af448df7280c978b968966db4b8b2b4e6d231152  0.1s
 => => extracting sha256:282ebe8f0e4864f0231f3b647e3417c38d85b9646a1a35820649c218a5661937  0.0s
 => [backend internal] load build context                                                  0.1s
 => => transferring context: 172.33kB                                                      0.0s
 => [client internal] load build context                                                   0.2s
 => => transferring context: 132.01kB                                                      0.0s
 => [client base 2/2] WORKDIR /usr/local/app                                               1.1s
 => [backend backend-dev 1/4] COPY backend/package.json backend/yarn.lock ./               0.2s
 => [client client-base 1/5] COPY client/package.json client/yarn.lock ./                  0.2s
 => CANCELED [client client-base 2/5] RUN --mount=type=cache,id=yarn,target=/usr/local/s  17.9s
 => ERROR [backend backend-dev 2/4] RUN --mount=type=cache,id=yarn,target=/usr/local/sha  17.5s
------
 > [backend backend-dev 2/4] RUN --mount=type=cache,id=yarn,target=/usr/local/share/.cache/yarn     yarn install --frozen-lockfile:
1.577 yarn install v1.22.22
1.615 warning package.json: No license field
1.790 warning<EMAIL_ADDRESS>No license field
1.796 [1/4] Resolving packages...
2.725 [2/4] Fetching packages...
13.44 error https://registry.yarnpkg.com/caniuse-lite/-/caniuse-lite-1.0.30001583.tgz: Extracting tar content of undefined failed, the file appears to be corrupt: "ENOENT: no such file or directory, chmod '/usr/local/share/.cache/yarn/v6/npm-caniuse-lite-1.0.30001583-abb2970cc370801dc7e27bf290509dc132cfa390-integrity/node_modules/caniuse-lite/data/features/tabindex-attr.js'"
13.44 info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
------
WARN[0054] current commit information was not captured by the build  error="failed to read current commit information with git rev-parse --is-inside-work-tree"
WARN[0054] current commit information was not captured by the build  error="failed to read current commit information with git rev-parse --is-inside-work-tree"
failed to solve: process "/bin/sh -c yarn install --frozen-lockfile" did not complete successfully: exit code: 1

The beginner's guide has outdated information, so for those who will be on the same path and with the same problem, those who are interested in what the difference is, then
docker compose up --watch automatically restarts services when changes are detected, whereas docker compose watch simply monitors changes without automatically restarting. This command is new in Docker Compose V2


Add Architecture field to Seccomp configuration in Linux runtime

By default, Seccomp filters will only permit syscalls to be made using the
native architecture of the kernel. This is fine for most use cases, but breaks
others (such as running 32-bit code in a container on a host with a 64-bit
kernel). This PR adds a field to specify additional architectures which may
make syscalls in a container secured by Seccomp.
As with other the other aspects of Seccomp, Libseccomp's seccomp.h is used to provide string constants which can be used to represent these additional architectures.

Ping @crosbymichael

@crosbymichael Added the relevant constants into the runtime config. I think they're valuable to have in the Go version of the spec, probably less so in the markdown description - considering converting that to a table so I can show descriptions

LGTM

LGTM


Organize Imports not working on insiders build

VSCode Version:
Version: 1.41.0-insider (user setup)
Commit: 27cd33d891eb23e370b672e751be9fe8b3748ac1
Date: 2019-11-08T19:12:35.358Z
Electron: 6.1.4
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Windows_NT x64 10.0.18363

Steps to Reproduce:

open a typescript project folder (angular for me)
select the Organize Imports command from command panel with opening a ts file
an error message called actual command NOT FOUND pop up from the right bottom corner
try to set the typescript.tsdk from project local installation version(3.5.3) to vscode builtin version(3.7.2) and both not working
switch to the stable version of vscode and the issue does not occured
I'm not sure whether it's related to typescript or not

Does this issue occur when all extensions are disabled?: Yes/No
Yes

sorry for my poor English if it's confusing you

this issue seems gone in today's insiders build 👍
Version: 1.41.0-insider (user setup)
Commit: 213bdddb72ff7a6c8eed071420de8ddac4293cb1
Date: 2019-11-11T05:40:31.150Z
Electron: 6.1.4
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Windows_NT x64 10.0.18363


Applications/Network needs -lutil

Performed ./clean_world.sh, ./build_world.sh and building of Applications/Network failed on Debian.  (See below)
Suggest adding
    ADDITIONAL_LDFLAGS = -lutil

to Network/GNUmakefile to pick up forkpty.
Making all for app Network...
 Creating Network.app/....
 Compiling file AppController.m ...
 Compiling file MiniView.m ...
AppController.m:323:30: warning: incompatible pointer types initializing 'DKPort<NMAccessPoint> *' with an expression of type 'DKProxy *' [-Wincompatible-pointer-types]
      DKPort<NMAccessPoint> *ap = device.ActiveAccessPoint;
                             ^    ~~~~~~~~~~~~~~~~~~~~~~~~
AppController.m:383:10: warning: unused variable 'viewFrame' [-Wunused-variable]
  NSRect viewFrame;
         ^
AppController.m:430:29: warning: incompatible pointer types sending 'DKProxy<NMActiveConnection> *' to parameter of type 'DKProxy<NMConnectionSettings> *' [-Wincompatible-pointer-types]
        updateForConnection:device.ActiveConnection];
                            ^~~~~~~~~~~~~~~~~~~~~~~
./EthernetController.h:21:62: note: passing argument to parameter 'conn' here
- (void)updateForConnection:(DKProxy<NMConnectionSettings> *)conn;
                                                             ^
AppController.m:448:29: warning: incompatible pointer types sending 'DKProxy<NMActiveConnection> *' to parameter of type 'DKProxy<NMConnectionSettings> *' [-Wincompatible-pointer-types]
        updateForConnection:device.ActiveConnection];
                            ^~~~~~~~~~~~~~~~~~~~~~~
./EthernetController.h:21:62: note: passing argument to parameter 'conn' here
- (void)updateForConnection:(DKProxy<NMConnectionSettings> *)conn;
                                                             ^
AppController.m:581:30: warning: incompatible pointer types initializing 'DKPort<NMAccessPoint> *' with an expression of type 'DKProxy *' [-Wincompatible-pointer-types]
      DKPort<NMAccessPoint> *ap = dev.ActiveAccessPoint;`<
                             ^    ~~~~~~~~~~~~~~~~~~~~~
5 warnings generated.
 Compiling file ConnectionManager.m ...
 Compiling file NMSetup.m ...
 Compiling file WifiController.m ...
NMSetup.m:29:9: warning: instance method '-clearBuffer:' not found (return type defaults to 'id') [-Wobjc-method-access]
  [self clearBuffer:self];
        ^~~~~~~~~~~
./NMSetup.h:10:12: note: receiver is instance of class declared here
@interface NMTerminalView : TerminalView
           ^
1 warning generated.
 Compiling file EthernetController.m ...
 Compiling file Network_main.m ...
 Linking app Network ...
/Library/Libraries/libTerminalKit.so: error: undefined reference to 'forkpty'
clang: error: linker command failed with exit code 1 (use -v to see invocation)
gmake[3]: *** [/Developer/Makefiles/Instance/application.make:131: Network.app/./Network] Error 1
gmake[2]: *** [/Developer/Makefiles/Instance/application.make:145: internal-app-run-compile-submake] Error 2
gmake[1]: *** [/Developer/Makefiles/Master/rules.make:297: Network.all.app.variables] Error 2
make: *** [/Developer/Makefiles/Master/application.make:38: internal-all] Error 2

Should be OK now.
Thanks!


[Dev UI] Endless Loading Spinner in Genkit UI

Describe the bug
I've created a sample genkit codebase with the help of firebase cli (firebase init).
However I can't do anything in the Genkit UI if I start it by genkit start because I end in an endless loading spinner:
The text I see is Waiting to connect to Genkit runtime....
To Reproduce
Steps to reproduce the behavior:

Create sample genkit codebase with firebase cli (firebase init)
Go to the folder which has been created
Start genkit with genkit start
Go to Genkit UI (e.g. http://localhost:4000)

Expected behavior
Genkit UI and flows can be tested.
Screenshots

Desktop (please complete the following information):

Device: Macbook Pro 16" M2 Pro
OS: macOS
Browser: Google Chrome
Genkit v0.9

Additional context
/

I have the same problem, may I ask if you have solved it


update flag parse in webhook

What type of this PR

Bug fixes

update flag parse in webhook
Which issue(s) this PR fixes:
Fixes #1345

已回合release-1.9


Examples of relations in the docs are wrong for TS

Hi, I've been setting up a new Feathers app with ObjectionJS and Typescript recently and found out that if I set up relations according to the examples outlined in the docs here (on the feathers-objection lib), it works initially - but once you start doing something less basic it falls apart.
I think I have a correct way to set it up so if interested, I'll do a PR.
Unfortunately it's going to need a PR in the feathers generator as well but it's not a big change so I'm keen on doing that as well if approved here.
The main issue is that the docs here suggest doing the following for setting up relations:

class User extends Model {
  static get tableName() {
    return 'user';
  }
  ...
}

module.exports = function(app): typeof User {
  if (app) {
    const db = app.get('knex');

    db.schema
      .hasTable('user')
      .then(exists => {
        if (!exists) {
          db.schema
            .createTable('user', table => {
              table.increments('id');
            })
        }
      })
  }

  return User;
};

The problem is that in TS with the default export you can't return type "User" but have to return "typeof User" since it's not an instance but a class definition you're returning.
So I propose to also export the model class itself and drop the if (app) check, so you'll use the default exported function only when creating the Feathers service, but use the model export whenever you need to reference it e.g. when setting up relations.

It would be better if you can open a PR, because I'm not sure that I fully
understand what you're looking for.
I'm not sure if you need to change the lib code or to add another example
of service & model initialization that works better with TypeScript.
בתאריך יום ו׳, 19 בנוב׳ 2021, 14:51, מאת Jiří Richter <
@.***>:

Hi, I've been setting up a new Feathers app with ObjectionJS and
Typescript recently and found out that if I set up relations according to
the examples outlined in the docs here (on the feathers-objection lib), it
works initially - but once you start doing something less basic it falls
apart.
I think I have a correct way to set it up so if interested, I'll do a PR.
Unfortunately it's going to need a PR in the feathers generator as well
but it's not a big change so I'm keen on doing that as well if approved
here.
The main issue is that the docs here suggest doing the following for
setting up relations:
class User extends Model {
static get tableName() {
return 'user';
}
...
}
module.exports = function(app): typeof User {
if (app) {
const db = app.get('knex');
db.schema
  .hasTable('user')
  .then(exists => {
    if (!exists) {
      db.schema
        .createTable('user', table => {
          table.increments('id');
        })
    }
  })

}
return User;
};
The problem is that in TS with the default export you can't return type
"User" but have to return "typeof User" since it's not an instance but a
class definition you're returning.
So I propose to also export the model class itself and drop the if (app)
check, so you'll use the default exported function only when creating the
Feathers service, but use the model export whenever you need to reference
it e.g. when setting up relations.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/feathersjs-ecosystem/feathers-objection/issues/162,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABB5E3IQTD7MRMRFB7E7THTUMZB5BANCNFSM5IMCHZOA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

It's just for docs here. I'll do the PR at the start of the next week.


How to start the system without "clients"

I would like to write my own executor that listen on the messages on /actions_hub and takes care of the execution on the robot.  Is that possible?  Is /actions_hub the complete API for this?
The thing I cannot find is how to start the system without some "clients". It seems that the executor is starting something that tries to run the actions.  At least if I start following the first tutorials.  So how do I start it so I can use my own client executor written in Python?

I was confused. I now see that the simple example launch file was not the one in bringup so things are working.  So there is no issue with starting the system.
But what I seem to be missing is some unique identifier in the ActionExecution message. How are you supposed to run two action in parallell on the same robot and the same action but maybe different arguments.  Do I have to make some string of the action and arguments so get a unique identifier?
Also what is the field "node_id" in ActionExecution message? What is the meaning?

Hi @tompe17

I would like to write my own executor that listen on the messages on /actions_hub and takes care of the execution on the robot. Is that possible? Is /actions_hub the complete API for this?

This is the topic that implements the execution auction protocol. You should check all the topics/services/actions that the executor currently has.
I would like to write my own executor that listen on the messages on /actions_hub and takes care of the execution on the robot. Is that possible? Is /actions_hub the complete API for this?

The thing I cannot find is how to start the system without some "clients". It seems that the executor is starting something that tries to run the actions. At least if I start following the first tutorials. So how do I start it so I can use my own client executor written in Python?

I do not understand this very well. Please, clarify.

But what I seem to be missing is some unique identifier in the ActionExecution message. How are you supposed to run two action in parallell on the same robot and the same action but maybe different arguments. Do I have to make some string of the action and arguments so get a unique identifier?

For executing the same action in the same robot you should have two different action executors running in the robot, with different node name

Also what is the field "node_id" in ActionExecution message? What is the meaning?

It is the node name
Francisco


hpx: 1.1.0 -> 1.2.0

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/hpx/versions.
meta.description for hpx is: '"C++ standard library for concurrency and parallelism"'.
Release on GitHub
Compare changes on GitHub

Checks done (click to expand)

built on NixOS
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/1d_stencil_1 passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/1d_stencil_2 passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/1d_stencil_3 passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/1d_stencil_4 passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/1d_stencil_4_checkpoint passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/1d_stencil_4_parallel passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/1d_stencil_5 passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/1d_stencil_6 passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/1d_stencil_7 passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/1d_stencil_8 passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/accumulator_client passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/template_accumulator_client passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/template_function_accumulator_client passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/async_io_simple passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/async_io_action passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/async_io_external passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/async_io_low_level passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/os_thread_num passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/hpx_thread_phase passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/cancelable_action_client passed the binary check.
Warning: no invocation of /nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/heartbeat had a zero exit code or showed the expected version
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/heartbeat_console passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/jacobi passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/jacobi_hpx passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/jacobi_nonuniform_hpx passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/nqueen_client passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/access_counter_set passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/simplest_performance_counter passed the binary check.
Warning: no invocation of /nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/sine_client had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/emitter had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/worker had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/collector had a zero exit code or showed the expected version
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/1d_wave_equation passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/allow_unknown_options passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/command_line_handling passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/component_ctors passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/component_in_executable passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/component_inheritance passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/component_with_executor passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/composable_guard passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/customize_async passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/data_actions passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/enumerate_threads passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/error_handling passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/event_synchronization passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/factorial passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/fibonacci passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/fibonacci_await passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/fibonacci_dataflow passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/fibonacci_one passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/fibonacci_futures passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/fibonacci_futures_distributed passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/fibonacci_local passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/file_serialization passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/fractals passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/fractals_struct passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/hello_world passed the binary check.
Warning: no invocation of /nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/init_globally had a zero exit code or showed the expected version
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/interest_calculator passed the binary check.
Warning: no invocation of /nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/interval_timer had a zero exit code or showed the expected version
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/latch_local passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/latch_remote passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/local_channel passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/partitioned_vector_spmd_foreach passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/pingpong passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/pipeline1 passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/print_to_console passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/potpourri passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/receive_buffer passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/safe_object passed the binary check.
Warning: no invocation of /nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/shared_mutex had a zero exit code or showed the expected version
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/sierpinski passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/simple_future_continuation passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/simplest_hello_world_1 passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/simplest_hello_world_2 passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/timed_futures passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/timed_wake passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/use_main_thread passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/vector_counting_dotproduct passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/vector_zip_dotproduct passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/wait_composition passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/zerocopy_rdma passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/fractals_executor passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/sort_by_key_demo passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/random_mem_access_client passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/oversubscribing_resource_partitioner passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/simple_resource_partitioner passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/simplest_resource_partitioner_1 passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/simplest_resource_partitioner_2 passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/async_customization passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/guided_pool_test passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/spell_check_simple passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/spell_check_file passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/thread_aware_timer passed the binary check.
Warning: no invocation of /nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/throttle_client had a zero exit code or showed the expected version
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/spin passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/simple_central_tuplespace_client passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/transpose_serial passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/transpose_serial_block passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/transpose_smp passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/transpose_smp_block passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/transpose_block passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/transpose_block_numa passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/transpose_serial_vector passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/hpx_runtime passed the binary check.
/nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/hpxrun.py passed the binary check.
Warning: no invocation of /nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/hpx_environment.py had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/hpx_invoke.py had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/hpx_optsweep.py had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/hpx_run_test.py had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin/hpxcxx had a zero exit code or showed the expected version
97 of 111 passed binary check by having a zero exit code.
0 of 111 passed binary check by having the new version present in output.
found 1.2.0 with grep in /nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0
directory tree listing: https://gist.github.com/0973b58320504d75995f00a0cd93985e
du listing: https://gist.github.com/db0ad4be9982a8bd2d26896ea61bc3cd

Rebuild report (click to expand)

1 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
0 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
0 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
hpx

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A hpx https://github.com/r-ryantm/nixpkgs/archive/6f3d64d86a6792c381220eeea02636339fec54f1.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0
ls -la /nix/store/r7iswii632hv0w02xkapgfnf0lllrlwj-hpx-1.2.0/bin

cc @bobakker for testing.

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: hpx
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Timed out, unknown build status on x86_64-linux (full log)
Attempted: hpx
Partial log (click to expand)
[ 57%] Linking CXX executable ../../bin/wait_composition
[ 57%] Built target wait_composition_exe
Scanning dependencies of target vector_zip_dotproduct_exe
[ 57%] Building CXX object examples/quickstart/CMakeFiles/vector_zip_dotproduct_exe.dir/vector_zip_dotproduct.cpp.o
[ 57%] Linking CXX executable ../../bin/zerocopy_rdma
[ 57%] Built target zerocopy_rdma_exe
Scanning dependencies of target timed_wake_exe
[ 57%] Building CXX object examples/quickstart/CMakeFiles/timed_wake_exe.dir/timed_wake.cpp.o
building of '/nix/store/cvlam8db1r4qz1dgii3mq0pxbafsqxpw-hpx-1.2.0.drv' timed out after 1800 seconds
error: build of '/nix/store/cvlam8db1r4qz1dgii3mq0pxbafsqxpw-hpx-1.2.0.drv' failed

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: hpx
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

(I'm building it locally to check)


Pull request for courses.html and caspertest

Pull request for courses.html and caspertest

A little constructive criticism for your next pull request:

What's the overall purpose of this pull request?  It's nice to give pull requests a clear title and a description that states the changes that were made and the intenion(s) behind them.
It looks like there are code style changes, visual changes, test improvements (or fixes?), and tests added (maybe missing tests or tests for something different?)

Number 1 can actually be dealt with on this pull request if you want to go back and review your own changes and do a recap in the description field above.
FYI you can make bulleted lists on Github by making bullet line start with a -  like this:
Changes:
- Made columns on page Y wrap to 2 columns instead of 4 on small screens
- Did something else

That will look like this:
Changes:

Made columns on page Y wrap to 2 columns instead of 4 on small screens
Did something else

Alright will check this more often. Thought had to create a separate branch just to fix this problem since it's not part of the new issues ... or at least I thought so. I guess you can ignore this pull request.


Add recent podcast interview to learn by watching section

Description
Add recent podcast interview to learn by watching section,
Motivation and Context
Update this user docs section with the most recent relevant videos/interviews.
How Has This Been Tested?
Local in my environment
Screenshots (if appropriate):

Types of changes

[ NA] Bug fix (non-breaking change which fixes an issue)
[ NA] New feature (non-breaking change which adds functionality)
[ NA] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ x] My code follows the code style of this project.
[ NA] My change requires a change to the documentation.
[ x] I have updated the documentation accordingly.
[ x] I have read the CONTRIBUTING document.
[ NA] I have added tests to cover my changes.
[ x] All new and existing tests passed.

Moved here:
https://github.com/matter-labs/zksync-docs/pull/179


how to let zgen enable the following line in zpreztorc?

https://github.com/sorin-ionescu/prezto/blob/master/runcoms/zpreztorc
line 22
# zstyle ':prezto:load' zfunction 'zargs' 'zmv'
I tried to uncomment the line in my
~/.zgen/sorin-ionescu/prezto-master/runcoms/zpreztorc
and did zgen reset.
But I still can't use zmv. Thank!

You can't modify plugins directly inside ~/.zgen directory. You have to do it somewhere else.


Why does transaction return a function rather than just running the function directly?

Is there some cost to creating a transaction function that makes it worth saving the function returned by transaction to be called multiple times?
I.e. I currently have code like db.transactions(someFn)();. Is that bad for some reason?

For future questions: there is a "Discussions" tab right next to the "Pull Requests" tab.
This makes transactions re-usable because the function also accept arguments. In contrast to re-using prepared statements this is not really a matter of performance. It allow you to encapsulate complex operations with multiple statements in a single function that you can then export from some module.

Is that bad for some reason?

Short answer: not really, because everything is cached.. So calling db.transaction again is pretty cheap.

Hey! Long time no see.


⚠ ClamAV has degraded performance

In e5fec81, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 484 ms

Resolved: ClamAV performance has improved in e0c9eb6.


Azure App Service Extension not showing up in Activity Bar

Type: Bug
I have installed and enabled the Azure App Service extension but for some reason it is not showing up in activity toolbar,  please help
Extension version: 0.25.1
VS Code version: Code 1.83.1 (f1b07bd25dfad64b0167beb15359ae573aecd2cc, 2023-10-10T23:48:05.904Z)
OS version: Windows_NT x64 10.0.19044
Modes:

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i7-11850H @ 2.50GHz (16 x 2496)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
31.73GB (20.89GB free)

Process Argv
--folder-uri file:///c%3A/Users/237160/ACSMaximusSoftphoneApp --crash-reporter-id c52ff71d-b95b-45b8-a100-088894fabea9

Screen Reader
no

VM
0%

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
py29gd2263cf:30856253
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
282f8724:30602487
f6dab269:30613381
a9j8j154:30646983
showlangstatbar:30737416
962ge761:30841074
03d35959:30757346
pythonfmttext:30731395
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
pythonnosmt12:30797651
pythonidxpt:30805730
pythonnoceb:30805159
copilotsettingc:30859502
synctok:30821570
dsvsc013:30795093
dsvsc014:30804076
diffeditorv2:30821572
pythonmhint1:30842940
dsvsc015:30845448
pythonregdiag:30859691
pyreplss2:30858576

What do you mean by the activity toolbar?  Could you please share a screenshot showing what you're seeing on your end?

Hi Matthew,
The issue has been resolved, for some reason the Azure icon was missing (not showing up) on the left hand toolbar in VS Code after installing the extension.  I was able to enable it using ‘Ctrl + Shift + A’.  Thanks.
@.***
From: Matthew Fisher @.>
Sent: Wednesday, October 18, 2023 5:48 PM
To: microsoft/vscode-azureappservice @.>
Cc: Thomas, Tharang @.>; Author @.>
Subject: [EXTERNAL] Re: [microsoft/vscode-azureappservice] Azure App Service Extension not showing up in Activity Bar (Issue #2583)
What do you mean by the activity toolbar? Could you please share a screenshot showing what you're seeing on your end?
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/vscode-azureappservice/issues/2583#issuecomment-1769519906, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A36BP6OFIR6PI4WZY6OBWG3YABMCJAVCNFSM6AAAAAA6EPVFSSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRZGUYTSOJQGY.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>CONFIDENTIALITY NOTICE: This e-mail, including attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information or otherwise be protected by law. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender and destroy all copies and the original message.


[BUG] Table filter banner grows vertically when activated and filters already selected

Describe the bug

After clicking the "Add new filter"  button:

Steps to Reproduce
Steps to reproduce the behavior:

Navigate to parts
Click on "Add new filter"   button above the parts table

Expected behavior
It should expand horizontally rather than vertically?
Version Information
Tested on demo version.

looks like a css issue?


Image width

hi sir i am having troublw with image width. its taking full size of page. i am also trying to give coustom size but its not working

images inside jconfirm are set to 100%, you might want to set it to a custom size and set !important to it.
width: 100px !important


Allow extraction of all MSAL logs from Azure Identity library

Context:
When customers encounter bugs in MSAL, the MSAL team needs detailed logs to diagnose the issue. The Azure Identity library doesn't have a provision to extract all these logs. In particular, we need verbose logs with PII information. For context, MSAL exposes 2 knobs for logging:

The log verbosity, which is very closely related to Azure SDK’s verbosity, i.e. Verbose, Info, Warning, Error.
A PII flag, false by default. Note: For a cheat sheet of what gets logged, see https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/wiki/PII.

The request is to allow app developers using the Azure Identity library to collect Verbose + PII logs from MSAL, on request, which are sometimes needed for supportability. The Azure Identity library exposes some knobs already, but there's no alignment over PII.

Moving this to the backlog because MSAL for Go doesn't log anything.

EnableSupportLogging is the name we're landing on, for when Go eventually does add this support.


Onwership patterns in the compiler

One of the technical debts of the Rust compiler is that its code does not take full advantage of Rust's ownership rules. This is partially through hacking over time but mostly due to being bootstrapped so early in Rust's development (it used @mut pointers way back when). There are a couple of ways they do ownership (Rc<T>, P<T>) with varying degrees of unsafety. The truth is simple: the Rust compiler is not written in "safe Rust". Obviously, this is very difficult (why create protosnirk if everything can be expressed in safe Rust) but I think it's possible to do better, most of the time. Obviously, hackiness eventually needs to be introduced as the language requires (not everything can be a perfect set of passes) but here are the basics:
String interning

In a patch or two, add string interning. Do it without lazy_static.
name fields either become Rc<String> or StringId
Issue with Rc<String> is reference count updates, having an index and asking for updates makes the cost more explicit
rustc has a gensym on its string pool, this might be worth exploring
StringPool should be passed around a lot but its mutability rules should be simple
Rust takes thread-local storage into account - it's probably not worth trying to sync pooling between threads

Tokens

Token's text becomes interned.

Tokenizing

Tokenizer's next() takes an &mut StringPool

AST

At this point, the AST depends on its StringPool
The parser can totally handle initializing the ScopeIndex of the AST without an extra pass, this could even be fixed in typeck
ScopeIndex should probably use a SmallVec or fixed-size type - it also needs a better name like ScopedId Done in typeck branch
We could also give each AST node a unique index

In the next stages of compiling, we need to run checks in passes. Each check should add some extra set of data to the program.
Many compilers do this through lowering passes, and produce new semantic trees or graphs of their represented program.
However, I think we can take a relational approach: do things in more passes but have easier lifetime analysis. Produce multiple
mappings instead of lowering data down.
Item collection
We need a first pass to correlate function names together so they can be called before being declared.

Visit all items, add them to a symbol table (specified in name check)

Name check
The first pass (currently parse::verify::smybol_checker) creates a mapping ScopeIndex -> Symbol that simply verifies that
each item and variable declared actually exists. This can happen before an "imports" pass.

Ensure that variables are all declared and not duplicated
Symbol: should have a unique identifier (SymId), a ScopedId of where declared, and possibly metadata about its declaration: is the variable mutable, etc.
The name checker should borrow the string pool and be consumed into the SymbolMap.

Mutation checks are built into this right now (by changing Cell<bool> fields in Symbol). Moving it into its own check might simplify things but would
result in more code and another pass. This has been changed in the typeck branch.
Type check
Type inference in the typeck branch uses the same ScopedIds as variable identification. Types are resolved in a graph to unique nodes which are mapped to concrete types.
Compile
Compiling is the fun part where each of these tables is looked up from each other

Generate LLVM type from each type/cache these in a TypeId -> LLVMType
Make sure predefined functions are declared
Take in the ScopeIndex -> Symbol, SymId -> TypeId and use them to compile the module, building up a ScopeId -> LLVMValueRef
Compiler should also take in the StringPool to produce nice names

Errors

The errors will probably contain string ids
The error handlers will need to use the StringPool

I've updated this old issue given my progress in the typeck branch, but I think I may have to close this and reopen smaller/more organized items. String interning may be an important feature to add later when performance improvements are needed.

Another solution is to bootstrap as late as possible.
Is there some solution to bootstrapping (other than being a good means of dogfooding the language) that I'm unaware of?
Go didn't bootstrap until 1.4 IIRC.

I had assumed the compiler would be more efficient with string interning (ASTs can have a lot of repeated identifiers), but looking around at other compilers I don't see a lot of string interning. It'll certainly never compare to time and space requirements of running LLVM.
Most of the things in this issue that are actually useful comments are things I'm doing in the typeck branch, and everything else is too long-term and vague to bother about. I may feel the need to rewrite the AST implementation in the future (possibly when user-defined structures and generics are taking shape), and I think a lowering pass will be required for lifetime handling and optimizations, but those aren't worth creating GitHub issues over right now.
I'm not concerned about bootstrapping - it can wait. It certainly couldn't happen anytime soon.


Enable monitoring for single model.

When I tried tutorial, the following error occured.
$ print_monitor_cv.py cifar_grbm_smd.pkl
Traceback (most recent call last):
  File "XXXXXXX/pylearn2/pylearn2/scripts/print_monitor_cv.py", line 84, in <module>
    main(**vars(args))
  File "XXXXXXX/pylearn2/pylearn2/scripts/print_monitor_cv.py", line 38, in main
    for model in list(this_models):
TypeError: 'GaussianBinaryRBM' object is not iterable

The print_monitor_cv.py seems not to support single layer model, so I patched it.
It would be nice if you could adopt this patch.

oh... Test is failed. I will check later.

sorry, I should use print_monitor.py not print_monitor_cv.py :bow:


[WIP] remove vmwware events

removes the events  ManageIQ/System/Event/EmsEvent/VC.class
Interestingly ManageIQ/System/Event/EmsEvent/VMWARE-VCLOUD.class had none in settings.yml
@lfu I suspect that there are more Vmware Events in settings.yml that dont have an automate connection. Do you have an idea how to pinpoint them? I could only guess by the similarity of their name.

@durandom Usually the VMware events are in CamelCase.

@durandom Usually the VMware events are in CamelCase.

Should I extract all those? @agrare is there somewhere a doc, to at least check if they are from vmware? I could also try by tracing back to the originating commit, but that would be really tedious

@agrare is there somewhere a doc, to at least check if they are from vmware

We have the SDK, if it is a VMware event it will be in here https://github.com/ManageIQ/manageiq-gems-pending/blob/master/lib/gems/pending/VMwareWebService/wsdl41/vim-types.xsd
I'm not familiar with what those events are used by/for so short of checking one-by-one if they are in the vcsdk wsdl I don't know how you'd identify VMware ones.

also removed all events that are in VMwareWebService/wsdl41/vim-types.xsd

@durandom a lot of these look VMware specific still, ReconnectHost_Task, ReconfigVM_Task, etc...
You've taken mostly Events but some Tasks as well, is the goal to just get all of the events then the Tasks later?

@durandom What is the status of this PR?  Also, I don't understand why you are removing events from the timeline but justifying with that they are not handled by automate?  I could see removing events that are no longer in vSphere for the versions we support, but that's not what's happening here form what I can tell.

@Fryguy indeed progress has gone stale :(

I don't understand why you are removing events from the timeline but justifying with that they are not handled by automate?

I'm not removing them, but moving them to vmware provider. See https://github.com/ManageIQ/manageiq-providers-vmware/pull/34 which I havent linked (my bad)

ohhhh my mistake...I misread.

@agrare is this something we still want to work on?


Fix mul overload

@avik-pal it looks like this is hitting some scalar index stuff?

Yeah we need to change aos to anytracedarray

Okay @avik-pal tesfs pass so I’m going to merge


Side effects when switching POE port power on GS308EP

There are some unwanted side effects caused by enabling/disabling the POE Port Power using this integration:
Initial settings:
| Port Priority         | Low             |
| Power Limit Type      | User            |
| Power Limit (W)       | 30.0            |
| Detection Type        | IEEE 802        |
| Longer Detection Time | Disable         |

Settings after switching off and on again:
| Port Priority         | Low             |
| Power Limit Type      | None            |
| Power Limit (W)       | 16.2            |
| Detection Type        |                 |
| Longer Detection Time | Get Value Fault |

The switch probably expects a full set of data in the posted form and overwrites the missing attributes with default/empty values. A way to solve this is to fetch the form first, copy the current settings and only change the port power value before posting back the entire form.

I can confirm this happens with the GS308EPP as well. Happy to support testing


EndOf File Error

Hi,
one question: After a certain time, the MessageWriter quits with 'end of file'. It seems, that a wrap around is not implemented. Is that correct?

That's correct and by design since the idea with mappedbus is to store all messages. So you'll have to make the file large enough for your use. However, an improvement could be that the writers continue to another file when the first one is full.

Any update on the feature request?