 import from /public

Is your feature request related to a problem?
Is there a good way to import SVG from public folder and render as svg element?
Describe the solution you'd like
Don't want to use and wrap a react library with qwik-react.
Don't want to have to create an exported function like the Qwik starter project  example.
Need to be able to access the actual svg.class directly to add things like tailwind classes so cant use img.src or object, etc.
Describe alternatives you've considered
img.src
object
vite plugins but most use React stuff which I don't want due to additional bloat/wrappers
Additional context
No response

In React you can do this
import React from 'react';
import {ReactComponent as Icons} from './icons.svg';

const App = () => {
  return (
    <div className="App">
      <Icons>
        <use href="#users"></use>
      </Icons>
    </div>
  );
}
export default App;

But I can't figure out how to make it work in Qwik.

A bit late to the party, but how about using ?jsx postfix on import path?
For example:
import Icon from "/public/icons/icon.svg?jsx";

Then use the imported svg directly as a component in code:
<Icon />

and apply classes directly to this component:
<Icon class="color-red-700" />

Responsive Image feature solved this specific issue.


(ruby) Wrong number of arguments passed for Timers

Currently, the wrong number of arguments are passed to the Timer lambdas from the Timer gem in librb/engine.rb. The Timer gem passes self as a second argument.

Fixed in #342 342

Hi, thanks for posting the pull request. I have merged the change and published a new version (2.0.28).


collectors: Change operation from Start to Collect

collectors: Change operation from Start to Collect
Start is not an appropriate operation name for the gadgets that generate a snapshot because they are not actually being started but just executed. In fact, after the Start operation they do not go in Started but Completed so they do not even need to be stopped.
For these reasons, the operation name was changed from Start to Collect.
https://github.com/kinvolk/inspektor-gadget/pull/357 unblocked this implementation and made it quite straightforward.
How to use
Nothing changes from the user's point of view.
Testing done

I tested the socket-collector with the local-gadget.
I re-run the socket and process collector guides to ensure they were still working correctly.

I think the changes to local-gadget are fine.


Updated submodules/lacework-control-tower-cfn.

Updated submodules/lacework-control-tower-cfn. Removed extraneous test parameters from lacework-control-tower-cfn cfn-abi-control-tower-integration.template.yaml.

/do-e2e-tests

@jefferyfry tests fail due to Issues with below resources from ControlTower submodule:

LaceworkAuthFunction
LaceworkSetupFunction
LaceworkAccountFunction

All 3 failed due to S3 permission or incorrect reference to the key.
Resource handler returned message: "Error occurred while GetObject. S3 Error Code: NoSuchKey. S3 Error Message: The specified key does not exist. (

@kkvinjam Added missing lambda zip files for ControlTower submodule.


Specular on export is always 0.5

When I export a model, specular value is always 0.5, no matter what is set in the material setting. This results always a bit shiny material. Same result with Babylon.js sandbox and when the model is imported back to Blender.
Windows 10, Blender 2.83.3

Hello,
glTF 2.0 use Metallic / Roughness PBR values, so there is no specular data directly in glTF file.
Can you please share a .blend file and corresponding .glb or .gltf file, as requested in issue template?
Thanks

The gltf2 specification does not define PBR specular (1 channel). It could be an extension, but it's not required to be implemented.

Thanks, I think I get it now. I'm coming from "traditional" materials, so PBR is a bit new to me. So I need to set roughness to 1, if I want to get completely matte material.

Seems we answer the question. Can this ticket be closed?

This is kind of relevant: While "specular" doesn't exist in gltf metallic workflow, in BabylonJS PBR material's metalic workflow there are a couple of values that directly affect the specular effect. They are "F0 Factor" and "indexOfRefraction". But changing the ior in blender's principled shader has no effect in the exported gltf ior. Maybe connecting these would help?

Hello,
See #1646
This is currently in development


Using a fully featured vue component as the preview template

Description:
For the purposes of keeping code DRY I'd like to use the html from a existing component as the preview template.
Right now, at least according to the documentation I was able to find we are supposed to give the previewTemplate prop a function that returns HTML.
I think it would be nicer if it were possible to use a component that was for instance imported from a .vue file.
Steps To Reproduce:
I've tried to import the component and attach it to the data property of the parent that contains the vue2-dropzone component.
Passing the data property itself or something akin to
<dropzone :previewTemplate="previewTemplate.render">

does not work, as the render function has not been created when the dropzone component is loaded.
It probably shouldn't, but maybe there is a way?

Gday @NikiSchlifke
That would be awesome, there's been some related requests (eg here ). I definitely love to do this but I haven't found a way yet. I gather it is complicated downstream but how dropzone.js itself handles the html string that is parsed, when I was digging I found reference to someone from the angular community wanting to do something similar.
Anyway I haven't given up hope yet, Im currently working on an overhaul of this component so Im trying to work it into that.

Hi folks,
Version 3 is now released. Check out the new docs for more info.

@rowanwins you got any progress on this? I tried to have a look at it, but didn't get any angle. I'm not that keen in vue yet, but you got any tips where we can start to solve this issue?

Unfortunately not @pscheit - it's a tricky one that I think is dependent on some changes upstream in dropzone itself.

@rowanwins @pscheit I have found a way to use components as previewTemplates.
The basic gist of it is to delay the initial VueDropzone component creation until you have the raw preview template html.
So this is what I did.
By default, I prevent the vue-dropzone from being loaded:
<vue-dropzone v-if="!loading"...
...
data: () => ({
  loading: true,
  previewHtml: null,

I load my options prop through computed properties but it should work if you load them through data:
computed: {
  options() {
    return {
      url: `${process.env.VUE_APP_API_BASE_URL}/upload`,
      previewTemplate: this.previewHtml,
    };
  },
},

Then I import Vue and my preview template component:
import Vue from 'vue';
import vue2Dropzone from 'vue2-dropzone';
import PreviewTemplate from './upload-media/PreviewTemplate.vue';

The preview component is a simple
Finally, I mount an instance of the component in my created hook and then pull out its outerHTML, load it into my previewHtml data attribute and end the loading:
created() {
  const ComponentClass = Vue.extend(PreviewTemplate);
  const instance = new ComponentClass();
  instance.$mount();
  this.previewHtml = instance.$el.outerHTML;

  this.loading = false;
}

Now when Dropzone starts initialising, I already have a compiled previewTemplate HTML in my options prop and it works like a charm.
If you want, I can make it into a PR.

@rowanwins @vrajroham
If this is still relevant I've made a way to get "proper" reactive templating for dropzone
https://github.com/AlexanderYW/vue-dropzone
And by "proper" i still need to figure out a way to deal with HUGE images without loosing performance (Will look into scaling the images before converting them to base64), but long story short I made it work with slots where it does not loose the @click bindings when being rendered
Feel free to give a hand if you have idea's regarding the performance issues

Hi AlexanderYW

@rowanwins @vrajroham
If this is still relevant I've made a way to get "proper" reactive templating for dropzone
https://github.com/AlexanderYW/vue-dropzone
And by "proper" i still need to figure out a way to deal with HUGE images without loosing performance (Will look into scaling the images before converting them to base64), but long story short I made it work with slots where it does not loose the @click bindings when being rendered
Feel free to give a hand if you have idea's regarding the performance issues

This is awesome, actually is exactly what is working on but got stuck as I kept loosing the @click binding inside slot,
Can u pls plz create a demo ASAP on codesandbox or codepen.
Thanks

@rowanwins @vrajroham
If this is still relevant I've made a way to get "proper" reactive templating for dropzone
https://github.com/AlexanderYW/vue-dropzone
And by "proper" i still need to figure out a way to deal with HUGE images without loosing performance (Will look into scaling the images before converting them to base64), but long story short I made it work with slots where it does not loose the @click bindings when being rendered
Feel free to give a hand if you have idea's regarding the performance issues

Unfortunately this does not work, at first your changed library refused to work at all, I fixed it, but it turned out that it does not support an external container for the template


Add GeneralConf.xml to make number of executors configurable

Now we have FetcherConf.xml, HeuristicConf.xml and JobTypeConf.xml.
I suggest to add a GeneralConf.xml to config things out of these scope, e.g. the number of executors.

@stiga-huang , thanks for submitting this patch.
+1, except for the minor comments.

@akshayrai , thanks for your review :smile:

@akshayrai , to make things clear, I split wait interval into fetch interval and retry interval.
Keys for them are drelephant.analysis.fetch.interval and drelephant.analysis.retry.interval

Looks quite useful. Nice work @stiga-huang! Also appreciate @akshayrai revisions. +1

PS @stiga-huang maybe you should squash your commits.

+1, thanks @stiga-huang


Empty response message after running insert/update query

What is the expected behavior in this case?

What is the expected behavior in this case?

should be just showing the table with the insert/update statement, that Empty response label should not be there. Not exactly sure what could be happening there.

Issue here is that code
        queryRes instanceof Array &&
        (queryRes[0]?.result ?? []) instanceof Array &&
        queryRes.filter((r: any) => (r.result ?? []).length > 0).length === 0 && (
          Empty response
        )}

So actually as the INSERT does not return any results, it is displaying that label.

Issue here is that code
        queryRes instanceof Array &&
        (queryRes[0]?.result ?? []) instanceof Array &&
        queryRes.filter((r: any) => (r.result ?? []).length > 0).length === 0 && (
          Empty response
        )}

So actually as the INSERT does not return any results, it is displaying that label.

But the table with the statement executed is not the queryRes?


ParallelRunStep for R scripts

Is your feature request related to a problem? Please describe.
Currently, we're able to deploy Python ML models with distributed batch scoring using the ParallelRunStep, and then we can call that deployed pipeline from Data Factory.  Some of the data scientists that I work with model in R.  ParallelRunStep can only run Python scripts and not R scripts.  Due to this, we're looking at other deployment alternatives, but it would be great if we could use Python to build a pipeline but have the scoring code be R.
Describe the solution you'd like
Currently, we build ML pipelines in ML Studio using the Python SDK and the ParallelRunStep.  We still want to use the Python SDK to build our pipelines, but it would be great if there was a way to run an R script from the ParallelRunStep instead of only Python scripts.
Describe alternatives you've considered
Azure Batch.  Azure Databricks + SparkR.  Azure Databricks + Sparklyr.
Additional context
For e.g., it would be great if the entry_script in ParallelRunConfig could be an R script if we wanted.  Then the R batch scoring script would follow the same format as a Python scoring script (init function, run function, etc.).  In addition, it would be great if we could specify the version of R as well.
env.r_version = '3.4.3'

parallel_run_config = ParallelRunConfig(
    environment=env,
    entry_script="batch_scoring.R",
    source_directory=".",
    output_action="append_row",
    mini_batch_size="20",
    error_threshold=1,
    compute_target=compute_target,
    process_count_per_node=2,
    node_count=1
)

Thanks for the feedback, we’ll investigate asap.

Thanks for the feedback.
Unfortunately, you cannot directly use an R script as entry script with ParallelRunStep. But you can write a Python wrapper to call the R script with a subprocess or use rpy2.
//sample entry_script to call R script with subprocess
def run(mini_batch):
"""Call echo.R/r-path for each item in mini_batch."""
result = []
for fil in mini_batch:
proc = subprocess.run(
["Rscript", r_path, fil],
shell=False,
check=False,
capture_output=True,
universal_newlines=True,
)
result.append(proc.stdout)
return result

@tracychms

"Unfortunately, you cannot directly use an R script as entry script with ParallelRunStep." - Correct this is why I reported a 'Feature Request'.
"But you can write a Python wrapper to call the R script with a subprocess or use rpy2." - I thought of that already, but how would I make sure the correct version of R is running in the container where scoring takes place?

If you use the subprocess approach and specify the version when building the image, it should work. rpy2 doesn't work.
def r_env():
"""Return environment for R.
DEFAULT_CPU_IMAGE = "mcr.microsoft.com/azureml/intelmpi2018.3-ubuntu16.04"
DEFAULT_GPU_IMAGE = "mcr.microsoft.com/azureml/intelmpi2018.3-cuda10.0-cudnn7-ubuntu16.04"
"""
env = Environment("parallel_run_step")
env.python.user_managed_dependencies = True
env.docker.base_image = None  # Set base image to None, because the image is defined by dockerfile.
env.docker.base_dockerfile = f"""

FROM {DEFAULT_CPU_IMAGE}

Hmmm.  I could try this.  If we're able to circle back around to entertaining this option again, I will try this out.

It's been a few weeks since a solution was provided so we'll close this issue for now. Should you have additional questions, please reopen this issue.


Reactive data to option

My data for the list comes from the backend and initially the options are an empty array and when the response comes from the backend the Multiple Selector component was not updating the list, I added this code and now the data has become reactive
useEffect(() => {
      setOptions(transToGroupOption(arrayOptions, groupBy));
    }, [arrayOptions, groupBy]);

Did you use onSearch props ?
I've done this here.
I think this part fit you needs.
Async Search with Debounce
there's a similar code currently.
    useEffect(() => {
      const exec = async () => {
        if (!debouncedSearchTerm || !onSearch) return;
        setIsLoading(true);
        const res = await onSearch?.(debouncedSearchTerm);
        setOptions(transToGroupOption(res, groupBy));   // <----- here
        setIsLoading(false);
      };

      void exec();
    }, [debouncedSearchTerm]);

I've add a prop triggerSearchOnFocus which might fit most use cases and refactored the onSearch executed condition.
Here is the usage.

Hi. I don't understand what a search has to do with my problem. Here code:
          <FormField
            control={form.control}
            name="optionList"
            render={({ field }) => {
              return (
                <FormItem>
                  <FormLabel>Option</FormLabel>
                  <FormControl>
                    <MultipleSelector
                      value={field.value}
                      onChange={field.onChange}
                      options={optionList}
                      placeholder="Select option to category"
                      emptyIndicator={

                          no results found.

                      }
                    />
                  </FormControl>
                  <FormMessage />
                </FormItem>
              );
            }}
          />

This is where I pass on the list of options options={optionList}
The problem is that this list is initially empty, and after some time, when the request to the server is executed, this list gets the required data - this happens asynchronously
But the MultipleSelector component does not respond to props changes options
const [options, setOptions] = React.useState<GroupOption>(
  transToGroupOption(arrayOptions, groupBy),
);

Since it moves it to the state during initialization and works with the stateit already
Therefore, when you change the props, you need to update the stack with new data.
useEffect(() => {
      setOptions(transToGroupOption(arrayOptions, groupBy));
    }, [arrayOptions, groupBy]);

You have to put your request in onSearch prop and return a GroupOtion[] value.
Just return the api res in onSearch prop and the component will trigger setOption.
<MultipleSelector
        // start here-----------------
        onSearch={async (value) => {
          const res = await mockSearch(value); // Your API.
          return res;  // return a value which  type is `GroupOtions`.
        }}
        // end here-----------------
        placeholder="trying to search 'a' to get more options..."
        loadingIndicator={
loading...
}
        emptyIndicator={
no results found.
}
      />

I still can't understand what search has to do with it - I'm not searching for anything. My request to api is executed through server action in zustand, then it is passed to child component in props where MultipleSelector is located. The initiating state for the options is an empty array, when the request is executed, the zustand storage will be mutated, and the necessary options will appear there for me to select from.

I got it. You are right for the useEffect.
I didn't do this useEffect because I was afraid of the performance issue of multiple re-renders.
I will add a JSON.stringify to avoid the same value re-render.
    useEffect(() => {
      /** If `onSearch` is provided, do not trigger renew options. */
      if (!arrayOptions || onSearch) {
        return;
      }
      const newOption = transToGroupOption(arrayOptions || [], groupBy);
      if (JSON.stringify(newOption) !== JSON.stringify(options)) {
        setOptions(newOption);
      }
    }, [arrayDefaultOptions, arrayOptions, groupBy, onSearch, options]);

here is the usage


Clipboard History appears on application start

Since the recent auto-update to B64 3915, the Clipboard History window now appears every time the application is started. There doesn't appear to be a setting in Preferences to stop this happening, and an Internet search says it's a bug - but I can't find a bugreport here.
So I'm creating one.

Do you have your clipboard docked to the side of a window, or is it
'floating' on the screen?
When you quit Quicksilver, is the clipboard open or closed?
Also, could you let me know which version of the Clipboard module you are
using (See the Plugins preference pane). You should be on v1.1.1
Thanks
On 8 February 2012 10:17, piersb <
<EMAIL_ADDRESS>
wrote:

Since the recent auto-update to B64 3915, the Clipboard History window now
appears every time the application is started. There doesn't appear to be a
setting in Preferences to stop this happening, and an Internet search says
it's a bug - but I can't find a bugreport here.
So I'm creating one.

Reply to this email directly or view it on GitHub:
https://github.com/quicksilver/Quicksilver/issues/691

It appears in the middle of the screen when the app starts, then closes. It's closed when I quit Quicksilver, and the plugin is v 1.1.1.

Hi again.
The Clipboard module was recently fixed to avoid this behaviour, so it is strange you are still seeing it. May I suggest you browse to this directory in Finder and delete the 'clipboard module'
~/Library/Application Support/Quicksilver/PlugIns
Once you've done that, try re-downloading the plugin.
Do you have the problem if you restart Quicksilver by pressing ⌘⌃Q or only when Quicksilver is first launched (e.g. when you log in)?

This happens with the Shelf too. It has nothing to do with B64. It’s been happening to me for at least 6 years.

The Clipboard module was recently fixed to avoid this behaviour, so it is strange you are still seeing it.

I thought that was for people that did want to see it on launch but only if it was docked. If you’re wondering why I didn’t bring it up, the recent changes didn’t bring up any new problems and never promised to fix my old ones. :-)
I also haven’t been able to find enough of a pattern to make a good report. I’ve seen it on a fresh launch and with a relaunch. Sometimes the panels go away after a second, sometimes I have to move the mouse over them, then mouse out of them and they’ll go away, and sometimes I have to click the close button (which doesn’t close them) then mouse out before they’ll go away.
I’ve mentioned this before, but I’m convinced (in my case anyway) that these panels think they’re docked to a screen edge even though they aren’t. That would explain

Why I can’t dock them to an edge
Why they tend to only go away when I mouse out of them

I haven’t ben able to figure out where the state for these panels is stored between launches, or I would try trashing the settings.

I thought that was for people that did want to see it on launch but
only if it was docked.

Recent (last 6 months) changes to the clipboard module have:

Stopped the panel appearing when other applications quit (the randomly
appearing bug)
Fixed what you have just mentioned above (which I broke whilst fixing 1)

I did not know anything about the panel appearing on launch.

I havent ben able to figure out where the state for these panels is
stored between launches, or I would try trashing the settings.

There's a BOOL in Quicksilver's prefs that specify whether the panel should
open or not on launch. Called QSPasteBoardHistoryIsVisible. Try setting
that to NO.
I'm not sure what the QSPasteBoardController BOOL does, but I have it set
to YES so maybe you should try that if it isn't?
QSGeneralShelfIsVisible also exists for the shelf.
On 8 February 2012 18:13, Rob McBroom <
<EMAIL_ADDRESS>
wrote:

This happens with the Shelf too. It has nothing to do with B64. Its been
happening to me for at least 6 years.

The Clipboard module was recently fixed to avoid this behaviour, so it
is strange you are still seeing it.

I thought that was for people that did want to see it on launch but only
if it was docked. If youre wondering why I didnt bring it up, the recent
changes didnt bring up any new problems and never promised to fix my old
ones. :-)
I also havent been able to find enough of a pattern to make a good
report. Ive seen it on a fresh launch and with a relaunch. Sometimes the
panels go away after a second, sometimes I have to move the mouse over
them, then mouse out of them and theyll go away, and sometimes I have to
click the close button (which doesnt close them) then mouse out before
theyll go away.
Ive mentioned this before, but Im convinced (in my case anyway) that
these panels think theyre docked to a screen edge even though they arent.
That would explain

Why I cant dock them to an edge
Why they tend to only go away when I mouse out of them

I havent ben able to figure out where the state for these panels is
stored between launches, or I would try trashing the settings.

Reply to this email directly or view it on GitHub:
https://github.com/quicksilver/Quicksilver/issues/691#issuecomment-3872599

the hidden value is controlled by the setting in QSDockingWindow.m
I guess the hidden BOOL isn't properly being set for you for some reason.
On 9 February 2012 15:53, Rob McBroom <
<EMAIL_ADDRESS>
wrote:

More info The problem seems to be with line 61, which reads
BOOL visible = ![(QSDockingWindow *)[[self sharedInstance] window]
hidden];
The result seems to alternate between YES and NO every time Quicksilver
quits. That is, quitting seems to toggle the setting. So every other launch
is where I see the window reappear.

Reply to this email directly or view it on GitHub:
https://github.com/quicksilver/Quicksilver/issues/691#issuecomment-3889712

I'm experiencing the same problem, should I assume the next version contains the fix?

should I assume the next version contains the fix?

No, but we’re working on it.


Mark gates when using a curve track on the OVERVIEW screen

would be useful to see when they are occurring

I don't think there is enough space on that page to add gates for curve tracks. The display has 64 pixels in height, leaving 8 for each track. Remove 1 for the spacing, you have 7 pixels for the curve. Adding gate information would remove 2 pixels (1 for the gates, 1 for the space) leaving 5 pixels for the curve visualization. So I don't think adding gate information there is that useful. Think of it from another perspective, there could also be a request to visualize retriggers, slides and whatnot. That's not really the point of the overview page anymore. So I think I'll close this one.


embassy-net 3.0 doesn't compile on esp32 due to async_fn_in_trait  and impl_trait_projections

I'm trying to upgrade a working esp32s3 project to embassy-net 3.0 (forced due to some dependency requirements) and face the errors below.
I added the suggested features to my crate, but it doesn't make any difference.
Seems like the rust compiler doesn't support these attributes (though it doesn't throw any error).
I tried it also on a new no_std project, just added
embassy-net = { version = "0.3.0", features = ["tcp", "udp", "dhcpv4", "medium-ethernet"]} and those errors appeared.
Am I doing something wrong or isn't esp32 working any longer with new embassy-net?
error[E0706]: functions in traits cannot be declared `async`
   --> /Users/user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/embassy-net-0.3.0/src/tcp.rs:545:9
    |
545 |         async fn read(&mut self, buf: &mut [u8]) -> Result<usize, Self::Error> {
    |         -----^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |         |
    |         `async` because of this
    |
    = note: `async` trait functions are not currently supported
    = note: consider using the `async-trait` crate: https://crates.io/crates/async-trait
    = note: see issue #91611 <https://github.com/rust-lang/rust/issues/91611> for more information
    = help: add `#![feature(async_fn_in_trait)]` to the crate attributes to enable

and
error[E0658]: `async fn` return type cannot contain a projection or `Self` that references lifetimes from a parent scope
   --> /Users/user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/embassy-net-0.3.0/src/tcp.rs:557:50
    |
557 |         async fn write(&mut self, buf: &[u8]) -> Result<usize, Self::Error> {
    |                                                  ^^^^^^^^^^^^^^----^^^^^^^^
    |                                                                |
    |                                                                help: consider spelling out the type instead: `embedded_io_impls::<impl embedded_io_async::Write for tcp::TcpSocket<'d>>`
    |
    = note: see issue #103532 <https://github.com/rust-lang/rust/issues/103532> for more information
    = help: add `#![feature(impl_trait_projections)]` to the crate attributes to enable

You need to update your compiler to latest stable (1.75) or newer.

I think with esp I have to use their version of the compiler, at least as far as I know - https://github.com/esp-rs/rust.
Is there a way to upgrade something there? Isn't it a single package of the compiler?
Also, isn't upgrading compiler just instead of adding the attributes manually? (unrelated to the esp problem)

check out esp's documentation I believe running espup update should be enough to update.

check out esp's documentation I believe running espup update should be enough to update.

Thanks, it worked.


Allow customizing timestamp format in Avro messages

Currently Avro messages assume that the timestamp field is always a Long value, unlike the JsonStringMessageDecoder which let's users choose the timestamp format.

Can one of the admins verify this patch?

Hey @jdhok,
thank you for your Pull Request.
It looks like you haven't signed our Contributor License Agreement, yet.

The purpose of a CLA is to ensure that the guardian of a project's outputs has the necessary ownership or grants of rights over all contributions to allow them to distribute under the chosen licence.
Wikipedia

You can read and sign our full Contributor License Agreement here.
Once you've signed reply with [clabot:check] to prove it.
Appreciation of efforts,
clabot

Camus is also deprecated from CP 3.0.0 on and we won't be making further changes.


Show CRNs and total seats in courses/section view

CRNs and total seat counts should be shown where sections are shown. Without showing the CRN, one must make a schedule to see any CRNs and cannot see what CRN corresponds to what section.
Additionally:
Should CRNs be shown on the schedule blocks?

total seats added in 3288b82


Adjust price after activity

Scintilla has the habit of putting a "max prize" on activities, meaning that the price of an activity can be lowered after the activity when costs end up less than predicted. For the EEMCS firstyears activity this has also been settled as the financial construction, so it has to be possible for the board to adjust the price down. This is also useful for merchandise for example, since this can become cheaper a piece when more are ordered. It should not be possible to adjust upwards.

This is quite tricky I believe, since creating an activity also makes a monetary transaction. So far we have steered clear of changing anything signup related when people have already signed up.
Not saying it’s impossible, do handle with care!


Add Avail Wallet

This closes #705
This is planned to be merged next week (ideally Monday)

@FrederikBolding the logging statements have been removed, can be confirmed on npm: https://www.npmjs.com/package/@avail-project/avail-snap?activeTab=code
Ready for re-review


CreateVectorizedFunction using only template parameters

Hello all,
This PR implements the CreateVectorizedFunction using only template parameters, it's a complement to the UDF C++ API.
It's very similar to the first CreateFunction implemented by the PR #712, the main difference is in the second argument that instead of receiving a generic function pointer (i.e., TR (*udf_func)(Args…)), it receives a vectorized function pointer of the type scalar_function_t:
typedef std::function<void(DataChunk &, ExpressionState &, Vector &)> scalar_function_t;
1. template<typename TR, typename... Args> void CreateVectorizedFunction(string name, scalar_function_t udf_func)

template parameters:

TR is the return type of the UDF function;
Args are the arguments up to 3 for the UDF function.

name: is the name to register the UDF function;
udf_func: is a vectorized UDF function.

This function automatically discovers from the template typenames the corresponding SQLTypes:

bool → SQLType::BOOLEAN;
int8_t →SQLType::TINYINT;
int16_t →SQLType::SMALLINT
int32_t →SQLType::INTEGER
int64_t  →SQLType::BIGINT
float →SQLType::FLOAT
double →SQLType::DOUBLE
string_t →SQLType::VARCHAR

An example of use would be:
static void udf_unary_function(DataChunk &input, ExpressionState &state, Vector &result) {
	assert(input.column_count() == 1);
	assert(input.data[0].type == TypeId::INTEGER);

	result.vector_type = VectorType::FLAT_VECTOR;
	auto result_data = FlatVector::GetData<int>(result);
	auto ldata = FlatVector::GetData<int>(input.data[0]);

	FlatVector::SetNullmask(result, FlatVector::Nullmask(input.data[0]));
	for (idx_t i = 0; i < input.size(); i++) {
		result_data[i] = ldata[i];
	}
}

connection.CreateVectorizedFunction<int, int>("udf_unary_int_function", &udf_unary_function);

P.S. It's missing a CreateVectorizedFunction to disambiguate some SQL types (some primitive types, e.g., int32_t, are mapped to the same SQLType: INTEGER, TIME and DATE).  Such function will be implemented soon in the same style of the second CreateFunction present in the PR #712, with some extra SQLType arguments.

I think this PR is ready, just the R package tests didn't pass due to the error: "Can't find DAV_PASSWORD in env".

Indeed, this is ready to merge! Thanks for the PR again :)


Small 0.10 updates

Removed the TODO from storage_engine.md and added a short note (taken from the blog post) about changes to clustering in 0.10 to 09_vs_010.

Had a few comments, otherwise this looks good. +1

Thanks, @gunnaraasen. I reworded it - agreed on the confusing wording.

+1


Cross site scripting is possible

Cannot be done in the comment box, only sending the post request manually.

should be fixed now


build: update to a tagged version of the Go zstd module

Oops. I deleted the branch too soon, sorry. I've restored it.


Dashrews/ROX-12271 check postgres for replica space

Description
Before creating clones to be used in upgrades and restores, we need to ensure that Postgres has enough space for the clone.  This PR does that calculation to ensure we have space.  There is one caveat to that.
We do not yet know how to best get the available size of a Postgres installation because it could be local, managed, etc.  We would have to use provider mechanisms to get that information for a managed instance.  For a local instance it varies and may be difficult to do in a secure fashion.  So for now, we are doing the calculations based on the assumption we have 100GB of Postgres storage.  ROX-12059 will address that.
The other trick to this is backup/restores.  The backup generated by pg_dump does not contain database size information.  Additionally the size of the dump file is likely significantly smaller than the database itself.  So I had to write a new file postgres.size that gets written to the backup bundle first to ensure that it is processed first.  The restore process reads that file to determine if there is enough space or not to perform the backup.  The DB size is the only thing written to that file.
Checklist

[ ] Investigated and inspected CI test results
~- [ ] Unit test and regression tests added~
~- [ ] Evaluated and added CHANGELOG entry if required~
~- [ ] Determined and documented upgrade steps~
~- [ ] Documented user facing changes (create PR based on [openshift/openshift-docs]~(https://github.com/openshift/openshift-docs) and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
Manual testing to specifically drive cases like an invalid size in the backup bundle.  Modified the size constant to be incredibly small and ran upgrades and restores manully to make sure not enough space was reported as expected.

/test style-checks


Investigate Vite build issues

When running vite build, there are some issues:

[x] Does TypeScript actually get properly handled by Vite Build?

DONE: Added tsc --noEmit before running vite build

[x] Semantic UI components spit out sourcemap errors

Can the problem be handled or alternatively can the errors be suppressed?

[x] Vite also complains about large chunks after minification

Is this important?

Added tsc --noEmit before running vite build.


Make the current location for script blocks executing in background/thread jobs default to the caller's in all scenarios

Update: This proposal has been approved - the remaining work is summarized in this comment.

Ideally, we'd have a consistent experience across all background-/thread-job related features, meaning that all of the following should exhibit the same behavior with respect to the current location that the script block being passed sees (by default:

(a) Start-Job
(b) Start-ThreadJob
(c) postpositional &  to start a job (implicit Start-Job)
(d) ForEach-Object -Parallel

The most sensible location to use is the caller's current location, which (c) already uses and (d) will, once #10672 is merged.
The proposal is to make (a) and (b) behave like (c) and (d) for overall consistency and use of a sensible default:
(b) (Start-ThreadJob) was meant to be modeled after Start-Job's example, but currently isn't: it uses the - virtually unpredictable from a user's perspective - process-wide working directory; given that, it shouldn't be too late to change it - see https://github.com/PaulHigin/PSThreadJob/issues/46
(a) (Start-Job) regrettably has always defaulted to $HOME (the filesystem provider's home location).
The question now is:
Can we consider Start-Job's default-to-$HOME behavior a bug / something worth fixing as a  Bucket 3: Unlikely Grey Area change?
I'm certainly personally in favor of that, but I haven't looked into how likely it is that existing Start-Job code relies on $HOME to be the default directory.
@iSazonov's take (from his comment at https://github.com/PowerShell/PowerShell/issues/10537#issuecomment-536199173):

I suggest to consider Start-Job case as bug.
If my work folder is c:\work and I run a job which switched to $home that is c:\users\isazonov - the last place is the worst place where user would like to see a resulting file. We could guess that user would use relative path to Documents folder. But most likely when faced with this inconsistency, the user will use the exact path to the working directory (c:\work), especially since the job is perceived as some kind of background process.

/cc @SteveL-MSFT Need PowerShell Committee conclusion.

@PowerShell/powershell-committee discussed this, we agree that each of these should standardize on using the current working directory as the working directory.  Start-Job is already inconsistent with itself in that Linux/macOS starts in user's home directory, but on Windows it starts in user's Documents folder.  We agree to accept a breaking change to always start in the filesystem current working directory where the cmdlet/operator is used for all of the scenarios.

@mklement0 Please update the issue description with current status - what is left to fix after last commits?

@iSazonov the background operator & already uses current working directory, foreach-object -parallel was fixed recently, start-threadjob has https://github.com/PaulHigin/PSThreadJob/issues/46 opened and @PaulHigin can make that fix and we can include that version in PS7.  I believe just Start-Job needs a fix.

@SteveL-MSFT Yes. The issue has PowerShell Committee conclusion and I'd want to see all (problems and solutions) in the OP for clear history because it is a breaking change.

I've updated the OP with a note at the top that points to the approval comment and to Steve's follow-up comment summarizing the remaining work needed.

I'd consider ForEach-Object -Parallel to be special in the sense that it's not a breaking change, since it's only a preview feature. This was the case I hit where my code was using old-school ForEach-Object and moving to the parallel version broke because executables were not found by the script. In this sense, not applying the caller's cwd is the breaking part.

@MathiasMagnus
This has already been fixed for ForEach-Object -Parallel (#10672)

@MathiasMagnus: Also note that it will be fixed for Start-Job and Start-ThreadJob as well (despite being technically breaking changes).


im.history error - channel_not_found

I am trying to get history of im. When I run
slack.im.history(channel='<channel_id>')

I get an error "channel_not_found".
My question is what should I put as channel?
Channel name or id? Due to lack of documentation, I am not being able to have this running right.

Hi @kthouz. Sorry for the late reply, I've been busy with so many other things. It's the channel ID, see official documentation https://api.slack.com/methods/im.history.


Breaking changes 0.4.23 -> 0.5.0?

Hi, are there any breaking changes that prevent me from forcing my sub-dependencies to use 0.5.0 instead of 0.4.23?

Yes, there is #603 which might break dependencies (see the tests changed in the same commit) but was required to address CVE-2023-0842. Hence I released it as 0.5.0 and not 0.4.24 (which I would have preferred).
If your dependencies are affected mostly depends how they use the returned object.

Seeing breaking changes, with "[Object: null prototype]" being added at each level of Object/nested Object.  Others are experiencing as well.  E.g., https://github.com/mattdesl/parse-bmfont-xml/pull/5.  I'm using the same workaround:
JSON.parse(JSON.stringify(result).  Not sure if there is a better solution, either in this lib, or in using code?

Probably either by comparing it with a value that doesn't have prototypes or using a comparison function that ignores prototypes.


Synthetic / Deepfake remove previous result when processing new image

Remove the previous result when a new image is processing

Done for both functions


learning gatsby/graphql to handle restful route and React state

I told to professor today. He suggest use to use gatsby and graphql instead of redux. We can take at look at it and discuss about it next week. No need for deep inside now, just take it look at it.

1.I spend some time to learn gatsby/graphql. Graphql is a new way to write rest api, but because we don't have a complicate database. I think it is not really worth to use it.
2. if you want to use gatsby, u must know graphql.
3.Both of them is not like to use a new css library, it takes time to learn. I still not quiet understand how gatsby works now. It is totally new. The biggest advantage is that gatsby make your website super fast.


Proposal: Refactor bundled --outFile result

The solution suggested in #6382 doesn't work as expected. It creates false define() statements in the JavaScript file:

I believe the TypeScript compiler doesn't react correctly in regard to bundled files.
IMHO, import { module1.Identifier2, module2.Identifier1 module3.Identifier1 } from "./moduleFile" should be the only valid syntax here.
That syntax should result in loading the bundle file and import all the required modules (which I suppose should become namespaces in the generated, i.e. referenced, bundled, JavaScript file) and identifiers from there.

Converting module syntax to namespace syntax in the bundle file feels reasonable to me, because the file gets loaded completely anyway. It doesn't make sense to retain the costly module syntax and infrastructure in a bundle file.

What does "Refactor bundled --outFile result" mean? can you provide more details.

Yes, sure. Lets have a look at the small example project taken from SetTrend/TS18 ...
This is the current output generated by TSC using --outFile --module amd --target ES5 (I enhanced the output here with an external reference to jQuery):
var __extends = (this && this.__extends) || function (d, b) {
    for (var p in b) if (b.hasOwnProperty(p)) d[p] = b[p];
    function __() { this.constructor = d; }
    d.prototype = b === null ? Object.create(b) : (__.prototype = b.prototype, new __());
};
define("_Base", ["require", "exports"], function (require, exports) {
    "use strict";
    var _Base = (function () {
        function _Base(element) {
            this.element = element;
            this._var = 1;
        }
        return _Base;
    }());
    Object.defineProperty(exports, "__esModule", { value: true });
    exports.default = _Base;
});
define("Derived", ["require", "exports", "_Base"], function (require, exports, _Base_1) {
    "use strict";
    var Derived = (function (_super) {
        __extends(Derived, _super);
        function Derived(element) {
            _super.call(this, element);
        }
        return Derived;
    }(_Base_1.default));
    Object.defineProperty(exports, "__esModule", { value: true });
    exports.default = Derived;
});
define("Manager", ["require", "exports", "jquery"], function (require, exports, $) {
    "use strict";
    var Manager = (function () {
        function Manager(provider) {
            this._provider = provider;
            $("body").addClass("loaded");
        }
        return Manager;
    }());
    Object.defineProperty(exports, "__esModule", { value: true });
    exports.default = Manager;
});

//# sourceMappingURL=all.js.map

In this simple example we find three defines. For each of these defines we need to create a configuration entry in the loader's configuration file or none of the defines will be found.
As the all.js file is loaded and interpreted in one large piece anyway, it is of no advantage to have each of the sub modules declare their own define.
I suggest to merge them all into one single standard define and export each of the sub-modules as namespaces, i.e. properties of the default output:
"use strict";

define(["require", "exports", "jquery"]
      ,  function (require, exports, $)
        {  exports.default =
          {  _Base:  function (element)    // no closures => no enclosurement
                    {
                      this.element = element;
                      this._var = 1;
                    }

          ,  Derived: function (__super)
                      {
                        return __extends(function(element) { __super.call(this, element); }
                                        , __super
                                        );
                      }(this._Base)

          ,  Manager: function (provider)    // no closures => no enclosurement
                      {
                        this._provider = provider;

                        $("body").addClass("loaded");
                      }
          }
        });

var __extends = (this && this.__extends)
                || function (d, b)
                    {
                      for (var p in b) if (b.hasOwnProperty(p)) d[p] = b[p];
                      function __() { this.constructor = d; }

                      d.prototype = b === null
                        ? Object.create(b)
                        : (__.prototype = b.prototype, new __());

                      return d;
                    };

//# sourceMappingURL=all.js.map

While the current `import` statements result in the following JavaScript:
```javascript
define(["require", "exports", "Derived", "Manager"], function (require, exports, Derived_1, Manager_1) {
    "use strict";
    var d = new Derived_1.default(null);
    var m = new Manager_1.default(d);
});
//# sourceMappingURL=main.js.map
The suggested import to look like this: `import myLib from "./tests/Scripts/all.js"` and rather generate something similar to this:
```javascript
"use strict";

define(["require", "exports", "all"]
      , function (require, exports, all)
        {
          var d = new all.default.Derived(null);
          var m = new all.default.Manager(d);
        });

//# sourceMappingURL=main.js.map

looks like a duplicate of https://github.com/Microsoft/TypeScript/issues/4434

No, not at all. As you can see from #4434, the suggestion there still suggests to create a number of define() statements - or System.register().

Please re-open.

not really. see my comment in https://github.com/Microsoft/TypeScript/issues/4434#issuecomment-135591590.

Ah, OK. I was only looking at the conclusion at the end of the thread. Fully agree.


DeepRec support cuda 10

System information

OS Platform and Distribution (e.g., Linux Ubuntu 20.04): Ubuntu 16.04
DeepRec version or commit id: main
Python version: python3.7
Bazel version (if compiling from source): 0.26.1
GCC/Compiler version (if compiling from source): gcc version 7.5.0
CUDA/cuDNN version: cuda 10.2  cudnn 7.6

Describe the problem
Under an environment of CUDA version 10.2 and cuDNN version 7.6, when compiling DeepRec, an error stating "No such file or directory" occurs, providing the specific details as follows:
/root/.cache/bazel/_bazel_root/e5dd34e735e9b22c055e30807c86bf9e/execroot/org_tensorflow/bazel-out/host/bin/tensorflow/core/_objs/embedding_gpu/gpu_hash_table.cu.pic.d (No such file or directory)
In file included from tensorflow/core/framework/embedding/gpu_hash_table.cu.cc:25:0:
external/cuCollections/include/cuco/dynamic_map.cuh:21:23: fatal error: cub/cub.cuh: No such file or directory

Provide the exact sequence of commands / steps that you executed before running into the problem

install cuda and cudnn

wget https://developer.download.nvidia.com/compute/cuda/10.2/Prod/local_installers/cuda_10.2.89_440.33.01_linux.run
sudo sh cuda_10.2.89_440.33.01_linux.run

https://developer.nvidia.com/rdp/cudnn-archive
tar -xzvf cudnn-xxx.tar.gz
sudo cp cuda/include/* /usr/local/cuda/include
sudo cp cuda/lib/libcudnn* /usr/local/cuda/lib64
sudo chmod a+r /usr/local/cuda/include/cudnn.h /usr/local/cuda/lib64/libcudnn*

bazel build DeepRec

bazel build -c opt --config=opt //tensorflow:libtensorflow_cc.so

Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem.

Good catch, currently DeepRec CICD is built on CUDA11, we haven't catch up the compatibility issue in CUDA 10.
Anyway, we suggest you upgrade to CUDA11 or CUDA12 (which also supported in DeepRec), which perform better performance.


Update UI Building Blocks on GettingStarted for parity

Overview
Updating UI Building Blocks links & table section on GettingStarted doc to match the home readme page for consistency & parity:
https://microsoft.github.io/MixedRealityToolkit-Unity/README.html
Changes

Fixes: #4916

Verification
View preview page and click links

/azp run mrtk_docs

/azp run mrtk_docs


zoxide script crashes at z<space><char>

I'm working on this zoxide script to get it working with engine-q. I believe shells doesn't exist yet but I can still source the file and when I try to do z<space<char> it crashes like this.
〉z thread 'main' panicked at 'internal error: span missing in file contents cache', crates/nu-protocol/src/engine/engine_state.rs:380:9
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

here's the script.
# Code generated by zoxide. DO NOT EDIT.

# =============================================================================
#
# Utility functions for zoxide.
#

# Default prompt for Nushell.
def __zoxide_prompt [] {
    # if gstat plugin is installed could do `gstat | get branch`
    let git = $'(do -i {git rev-parse --abbrev-ref HEAD} | decode utf-8 | str trim -r -c (char nl))'
    let git = (if ($git | str length) == 0 { '' } else {
        build-string (char lp) (ansi cb) $git (ansi reset) (char rp)
    })
    build-string (ansi gb) ($nu.cwd) (ansi reset) $git '> '
}

# =============================================================================
#
# Hook configuration for zoxide.
#

## Darren's shells HACK
def shells [] {
    [[active name path]; [$true filesystem $nu.cwd]]
}
## end HACK

# Hook to add new entries to the database.
def __zoxide_hook [] {
    shells | where active == $true && name == filesystem | get path | each {
        zoxide add -- $it
    }
}

# Initialize hook.
let-env PROMPT_COMMAND = (
    # let prompt = (if (env | where name == PROMPT_COMMAND | length) == 0 {
    let prompt = (if ("PROMPT_COMMAND" not-in (env).name)  {
        "__zoxide_prompt"
    } else {
        $nu.env.PROMPT_COMMAND
    });

    if ($prompt | str contains '__zoxide_hook') { $prompt } else { $'__zoxide_hook;($prompt)' }
)

# =============================================================================
#
# When using zoxide with --no-aliases, alias these internal functions as
# desired.
#

# Jump to a directory using only keywords.
def __zoxide_z [...rest:string] {
    if (shells | where active == $true | get name).0 != filesystem {
        if ($rest | length) > 1 {
            $'zoxide: can only jump directories on filesystem(char nl)'
        } else {
            cd $rest
        }
    } else {
        let arg0 = ($rest | append '~' | first 1);
        if ($rest | length) <= 1 && ($arg0 == '-' || ($arg0 | path expand | path exists)) {
            cd $arg0
        } else {
            cd $'(zoxide query --exclude ($nu.cwd) -- $rest | decode utf-8 | str trim -r -c (char nl))'
        }
    }
}

# Jump to a directory using interactive search.
def __zoxide_zi  [...rest:string] {
    if (shells | where active == $true | get name).0 != filesystem {
        $'zoxide: can only jump directories on filesystem(char nl)'
    } else {
        cd $'(zoxide query -i -- $rest | decode utf-8 | str trim -r c (char nl))'
    }
}

# =============================================================================
#
# Convenient aliases for zoxide. Disable these using --no-aliases.
#

alias z = __zoxide_z
alias zi = __zoxide_zi

# =============================================================================
#
# To initialize zoxide, add this to your configuration (find it by running
# `config path` in Nushell):
#
#   startup = ['zoxide init nushell --hook prompt | save ~/.zoxide.nu', 'source ~/.zoxide.nu']
#
# Note: zoxide only supports Nushell v0.37.0 and above.

updated script 12/28

I've started to narrow this down. the custom command __zoxide_z <string> works great. however, if I call the alias z <string> the first character of <string> causes this panic.
z thread 'main' panicked at 'internal error: span missing in file contents cache', crates/nu-protocol/src/engine/engine_state.rs:380:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

backtrace
z thread 'main' panicked at 'internal error: span missing in file contents cache', crates/nu-protocol/src/engine/engine_state.rs:380:9
stack backtrace:
   0: rust_begin_unwind
             at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/std/src/panicking.rs:517:5
   1: core::panicking::panic_fmt
             at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/core/src/panicking.rs:100:14
   2: core::panicking::panic
             at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/core/src/panicking.rs:50:5
   3: nu_protocol::engine::engine_state::EngineState::get_span_contents
             at ./engine-q/crates/nu-protocol/src/engine/engine_state.rs:380:9
   4: nu_protocol::engine::engine_state::StateWorkingSet::get_span_contents
             at ./engine-q/crates/nu-protocol/src/engine/engine_state.rs:833:20
   5: nu_parser::parser::parse_call
             at ./engine-q/crates/nu-parser/src/parser.rs:684:20
   6: nu_parser::parser::parse_expression
             at ./engine-q/crates/nu-parser/src/parser.rs:3162:9
   7: nu_parser::parser::parse_call
             at ./engine-q/crates/nu-parser/src/parser.rs:697:37
   8: nu_parser::parser::parse_expression
             at ./engine-q/crates/nu-parser/src/parser.rs:3162:9
   9: nu_parser::parser::parse_statement
             at ./engine-q/crates/nu-parser/src/parser.rs:3262:31
  10: nu_parser::parser::parse_block::{{closure}}
             at ./engine-q/crates/nu-parser/src/parser.rs:3405:35
  11: core::iter::adapters::map::map_fold::{{closure}}
             at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/core/src/iter/adapters/map.rs:84:28
  12: core::iter::traits::iterator::Iterator::fold
             at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/core/src/iter/traits/iterator.rs:2171:21
  13: <core::iter::adapters::map::Map<I,F> as core::iter::traits::iterator::Iterator>::fold
             at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/core/src/iter/adapters/map.rs:124:9
  14: core::iter::traits::iterator::Iterator::for_each
             at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/core/src/iter/traits/iterator.rs:737:9
  15: <alloc::vec::Vec<T,A> as alloc::vec::spec_extend::SpecExtend<T,I>>::spec_extend
             at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/alloc/src/vec/spec_extend.rs:40:17
  16: <alloc::vec::Vec<T> as alloc::vec::spec_from_iter_nested::SpecFromIterNested<T,I>>::from_iter
             at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/alloc/src/vec/spec_from_iter_nested.rs:56:9
  17: <alloc::vec::Vec<T> as alloc::vec::spec_from_iter::SpecFromIter<T,I>>::from_iter
             at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/alloc/src/vec/spec_from_iter.rs:33:9
  18: <alloc::vec::Vec<T> as core::iter::traits::collect::FromIterator<T>>::from_iter
             at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/alloc/src/vec/mod.rs:2517:9
  19: core::iter::traits::iterator::Iterator::collect
             at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/core/src/iter/traits/iterator.rs:1745:9
  20: <nu_protocol::ast::block::Block as core::convert::From<T>>::from
             at ./engine-q/crates/nu-protocol/src/ast/block.rs:61:20
  21: <T as core::convert::Into<U>>::into
             at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/core/src/convert/mod.rs:542:9
  22: nu_parser::parser::parse_block
             at ./engine-q/crates/nu-parser/src/parser.rs:3366:24
  23: nu_parser::parser::parse
             at ./engine-q/crates/nu-parser/src/parser.rs:3684:25
  24: <nu_cli::syntax_highlight::NuHighlighter as reedline::highlighter::Highlighter>::highlight
             at ./engine-q/crates/nu-cli/src/syntax_highlight.rs:17:30
  25: reedline::engine::Reedline::prepare_buffer_content
             at /Users/fdncred/.cargo/git/checkouts/reedline-e42026a78d91c510/afa83d9/src/engine.rs:951:32
  26: reedline::engine::Reedline::buffer_paint
             at /Users/fdncred/.cargo/git/checkouts/reedline-e42026a78d91c510/afa83d9/src/engine.rs:979:40
  27: reedline::engine::Reedline::repaint
             at /Users/fdncred/.cargo/git/checkouts/reedline-e42026a78d91c510/afa83d9/src/engine.rs:899:13
  28: reedline::engine::Reedline::run_edit_commands
             at /Users/fdncred/.cargo/git/checkouts/reedline-e42026a78d91c510/afa83d9/src/engine.rs:814:21
  29: reedline::engine::Reedline::handle_editor_event
             at /Users/fdncred/.cargo/git/checkouts/reedline-e42026a78d91c510/afa83d9/src/engine.rs:565:17
  30: reedline::engine::Reedline::handle_event
             at /Users/fdncred/.cargo/git/checkouts/reedline-e42026a78d91c510/afa83d9/src/engine.rs:427:13
  31: reedline::engine::Reedline::read_line_helper
             at /Users/fdncred/.cargo/git/checkouts/reedline-e42026a78d91c510/afa83d9/src/engine.rs:403:39
  32: reedline::engine::Reedline::read_line
             at /Users/fdncred/.cargo/git/checkouts/reedline-e42026a78d91c510/afa83d9/src/engine.rs:313:22
  33: engine_q::main
             at ./engine-q/src/main.rs:410:25
  34: core::ops::function::FnOnce::call_once
             at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/core/src/ops/function.rs:227:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

fixed by #713


Column and table comments for postgres/redshift (#2333)

resolves #2333
Description
This is very much based off the work being done by @snowflakeseitz in #2321
I intentionally copy+pasted the common adapter_macros to make merging easier.
With this PR, redshift and postgres now generate column and table comments during view and table creation. Their get_catalog macros also now include those comments in the output (instead of null) and the end up in the catalog itself.
I added tests as well, of course!
Redshift is a little special:

you can comment on late-binding views, but the comment isn't available anywhere as far as I can tell. I set it up so dbt still issues these commands, because maybe I just couldn't find them
you can't comment at all on late-binding view columns (it's an error!)

One annoying/weird quirk we might need to think about: When you do have comments, results lines show up as COMMENT in XXXs instead of CREATE TABLE in XXXs. That's a little goofy! Maybe comments should work like hooks do.
Checklist

[X] I have signed the CLA
[X] I have run this code in development and it appears to resolve the stated issue
[X] This PR includes tests, or tests are not required/relevant for this PR
[X] I have updated the CHANGELOG.md and added information about my change to the "dbt next" section.

One annoying/weird quirk we might need to think about: When you do have comments, results lines show up as COMMENT in XXXs instead of CREATE TABLE in XXXs. That's a little goofy! Maybe comments should work like hooks do.

I didn't think about this at all! That's kind of a big problem IMO. We're overdue for a rethink on how materializations work (especially w/r/t these create_X_as macros). I'm ok with this for the moment, but I think it would be good to prioritize materializations v2 in 0.18.0 :)
Reviewing this one now!


Snapshot Failure Handling

Right now, if rendering one snapshot throws an error (e.g. the render function of a component tries to reference a prop that wasn't passed in, or whatever it may be), we pretty much just bail out and don't try to run other test cases. Ideally, we should gracefully handle individual test case errors and still try to run as many tests as possible.

This is much less relevant now that we're client-rendering snapshots in Percy. A snapshot with a missing prop won't break other snapshots now, as it will only blow up when it renders in Percy, isolated from the other snapshots.


Fix noah36 runoff

Description
Correct a typo in noah36_lsm_ini to properly initialize fldsto.

Compiles w/o issue.  I accept.


Populate funding_activity_category_codes for all grants

Ticket #2408
Description
This PR does 3 things:

Adds a migration to populate the funding_activity_category_codes column from the raw body for grants that have not been ingested recently.
Enables the Category of Funding Activity feature flag in staging.
In preparation for dropping the column grants.raw_body in a future PR, performs a partial find-and-replace of raw_body to raw_body_json.

Regarding item 1, I think there is an opportunity to access the json body of a grant more directly in db calls instead of copying parts of it out into separate db columns. But, given that the separate column has already been set up in this case, populating it seems like the fastest way to get this functionality out the door. I'll think more about Postgres's JSON capabilities while I'm contemplating off-the-shelf search #2308.
Screenshots / Demo Video
No change in code functionality. This PR just fills in data that was missing.
Testing
To test the populate_funding_activity_category_codes_column migration, I ran the SQL locally against a variety of example grants:

Grant with non-null funding_activity_category_codes column - not updated.
Grant with null raw_body_json column - not updated.
Grant with invalid or missing funding_activity in raw_body_json - funding_activity_category_codes set to empty string.
Grant with valid funding_activity in raw_body_json (either single or multiple categories) - correct string produced.

As a final test, I loaded the staging snapshot provided by @TylerHendrickson here and ran all of the pending migrations against it. This resulted in:

28 grants where funding_activity_category_codes is NULL (these are all test grants)
289 grants where funding_activity_category_codes is the empty string (grants where the object passed by the ingestor had no funding activity categories)
74782 grants where funding_activity_category_codes is a non-empty string

These results match the numbers that @TylerHendrickson documented in the ticket.
Automated and Unit Tests

[ ] Added Unit tests

Manual tests for Reviewer

[x] Added steps to test feature/functionality manually

Checklist

[x] Provided ticket and description
[ ] Provided screenshots/demo
[x] Provided testing information
[x] Provided adequate test coverage for all new code
[x] Added PR reviewers

I'd be happy to postpone dropping raw_body if that would de-risk this PR.

@sanason Also adding a response to one of your comments in the OP:

Follow-up comment 1/16 - I'd also be happy to postpone dropping raw_body if that would de-risk this PR.

I think that might be a good idea. I'm not terribly concerned about losing this data altogether since we should always be able to get it out of the grants-ingest service if a need was identified. However, given that the continued presence of raw_body would mostly present a "problem" in the form of code organization, and considering the fact that this PR removes (almost?) all references to raw_body, there doesn't seem to be a huge amount of debt presented in keeping it around a bit longer.
If we went that route, then the remaining question would be: "if not now, when?" Something time-based could be a good approach here; maybe we create a follow-up issue to drop the raw_body column completely, perhaps after waiting 2 weeks (+/-) after the changes in this PR get deployed.
Thoughts?

Making a note here that I think this could cause (brief) service availability issues if deployed during a high-traffic period, given that this PR introduces code dependent on database constructs that may not yet exist.

All of the db columns that the code refers to are already in the production database (raw_body_json added here) so I don't think there will be any actual downtime. The 2 migrations will take a few minutes to run and, during that time, the Category of Funding Activity field will be visible but may not be populated correctly. I agree that's not the maximally correct behavior - on the other hand, it gets the feature out in one release instead of requiring two. @TylerHendrickson - up to you what matters more. I'll put the production flag back to false if you'd prefer.

Since this PR removes the only remaining client-side usage of raw_body, maybe it would be best to drop raw_body and raw_body_json from API responses altogether. Doing so might provide extra confidence leading up to the point where we do drop the legacy raw_body column.

I agree that this makes sense but I'm not sure how to easily identify all responses that contain raw_body or raw_body_json (I feel like I'd need API documentation or very complete API tests or Typescript). I've now changed the code to not return either field for following two endpoints, which are the ones I'm most familiar with:

/grants/next
/grants/:grantId/grantDetails

@adele-usdr
I'm thinking of cleaning up the response object that is returned from GET api/organizations/:orgId/grants/:grantId/grantDetails, so that it only returns fields that actually are needed by the caller. The change is here.
I believe that endpoint backs the new Grant Details page so could you look at the new response object and tell me if anything you need is missing? Thanks!
{
  "grant_id": "666656",
  "grant_number": "grant-number-666656",
  "title": "Test Grant 666656",
  "agency_code": "NSF",
  "cost_sharing": "No",
  "cfda_list": "47.050",
  "open_date": "2021-08-12",
  "close_date": "2024-01-29",
  "opportunity_category": "Discretionary",
  "opportunity_status": "posted",
  "description": "
Test Grant Description 666656
",
  "award_ceiling": "6500",
  "bill": null,
  "funding_activity_category_codes": "ST",
  "etitle": "Test Grant 666656",
  "viewed_by_agencies": [],
  "interested_agencies": [
    {
      "grant_id": "666656",
      "agency_id": 0,
      "agency_name": "USDR",
      "agency_abbreviation": "USDR",
      "user_id": 1,
      "user_email"<EMAIL_ADDRESS>      "user_name": "Alex Allain",
      "interested_code_id": 11,
      "interested_code_name": "Will Support",
      "interested_status_code": "Interested"
    }
  ],
  "funding_activity_categories": [
    "Science and Technology and Other Research and Development"
  ]
}

@TylerHendrickson In the interest of getting this merged, I made some changes to reduce the scope and hopefully de-risk the PR:

Only enabling the category of funding activity in staging - production can wait.
Not dropping the raw_body column
Not removing raw_body from the select set of any db queries (and, by extension, from any API responses) in case raw_body is being used somewhere that I didn't catch.


Create 0000-01-02-kancha21sri.md

check out the Commits 101 drop-down
Add kancha21sri's file

done


Error: cpu-features Command failed when installing db-migrate

db-migrate has been working fine up till today. Same M1 Macbook. Now for some reason all of a sudden it's barfing on me when I run yarn
OSX: Ventura Version 13.4.1
package.json
"db-migrate": "^0.11.12",
"db-migrate-pg": "^1.2.2",
 cpu-features
warning Error running install script for optional dependency: "/Users/daveschinkel/code/projects/we-do-tdd/node_modules/cpu-features: Command failed.
Exit code: 1
Command: node-gyp rebuild
Arguments:
Directory: /Users/daveschinkel/code/projects/we-do-tdd/node_modules/cpu-features
Output:
gyp info it worked if it ends with ok
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| darwin | arm64
gyp info find Python using Python version 3.11.4 found at \"/usr/local/bin/python3\"
gyp info spawn /usr/local/bin/python3
gyp info spawn args [
gyp info spawn args   '/Users/daveschinkel/.config/yarn/global/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/Users/daveschinkel/code/projects/we-do-tdd/node_modules/cpu-features/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/Users/daveschinkel/.config/yarn/global/node_modules/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/Users/daveschinkel/Library/Caches/node-gyp/20.5.1/include/node/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/Users/daveschinkel/Library/Caches/node-gyp/20.5.1',
gyp info spawn args   '-Dnode_gyp_dir=/Users/daveschinkel/.config/yarn/global/node_modules/node-gyp',
gyp info spawn args   '-Dnode_lib_file=/Users/daveschinkel/Library/Caches/node-gyp/20.5.1/<(target_arch)/node.lib',
gyp info spawn args   '-Dmodule_root_dir=/Users/daveschinkel/code/projects/we-do-tdd/node_modules/cpu-features',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.'
gyp info spawn args ]
gyp info spawn make
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
  ACTION Configuring dependencies /Users/daveschinkel/code/projects/we-do-tdd/node_modules/cpu-features/deps/cpu_features/build/Makefile
CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required):
  Compatibility with CMake < 3.5 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- The C compiler identification is AppleClang <IP_ADDRESS>30022
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Looking for dlfcn.h
-- Looking for dlfcn.h - found
-- Looking for getauxval
-- Looking for getauxval - not found
-- Configuring done (0.4s)
-- Generating done (0.0s)
-- Build files have been written to: /Users/daveschinkel/code/projects/we-do-tdd/node_modules/cpu-features/deps/cpu_features/build
  TOUCH Release/obj.target/config_deps.stamp
  ACTION Building dependencies /Users/daveschinkel/code/projects/we-do-tdd/node_modules/cpu-features/deps/cpu_features/build/libcpu_features.a
[ 11%] Building C object CMakeFiles/utils.dir/src/filesystem.c.o
[ 22%] Building C object CMakeFiles/utils.dir/src/stack_line_reader.c.o
[ 33%] Building C object CMakeFiles/utils.dir/src/string_view.c.o
[ 33%] Built target utils
[ 44%] Building C object CMakeFiles/unix_based_hardware_detection.dir/src/hwcaps.c.o
[ 55%] Building C object CMakeFiles/unix_based_hardware_detection.dir/src/unix_features_aggregator.c.o
[ 55%] Built target unix_based_hardware_detection
[ 66%] Building C object CMakeFiles/cpu_features.dir/src/cpuinfo_arm.c.o
In file included from /Users/daveschinkel/code/projects/we-do-tdd/node_modules/cpu-features/deps/cpu_features/src/cpuinfo_arm.c:15:
/Users/daveschinkel/code/projects/we-do-tdd/node_modules/cpu-features/deps/cpu_features/include/cpuinfo_arm.h:118:2: error: \"Including cpuinfo_arm.h from a non-arm target.\"
#error \"Including cpuinfo_arm.h from a non-arm target.\"
 ^
1 error generated.
make[3]: *** [CMakeFiles/cpu_features.dir/src/cpuinfo_arm.c.o] Error 1
make[2]: *** [CMakeFiles/cpu_features.dir/all] Error 2
make[1]: *** [all] Error 2
make: *** [/Users/daveschinkel/code/projects/we-do-tdd/node_modules/cpu-features/deps/cpu_features/build/libcpu_features.a] Error 2
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/Users/daveschinkel/.config/yarn/global/node_modules/node-gyp/lib/build.js:203:23)
gyp ERR! stack     at ChildProcess.emit (node:events:514:28)
gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:294:12)
gyp ERR! System Darwin 22.5.0
gyp ERR! command \"/Users/daveschinkel/.nvm/versions/node/v20.5.1/bin/node\" \"/opt/homebrew/bin/node-gyp\" \"rebuild\"
gyp ERR! cwd /Users/daveschinkel/code/projects/we-do-tdd/node_modules/cpu-features
gyp ERR! node -v v20.5.1
gyp ERR! node-gyp -v v9.4.0
gyp ERR! not ok"
success Saved lockfile.

db-migrate uses tunnel-ssh which uses ssh2 which uses cpu-features
This is the commit we need to bubble up the dependency tree:
https://github.com/mscdex/ssh2/commit/739a58976ca149aa852150501f08b92bc380650a
Luckily, it's already been bubbled up to tunnel-ssh so db-migrate really just needs to update that lib to ^5.1.1.
A simple fix for now is to add this line in your package.json if you're using yarn:
  "resolutions": {
    "db-migrate/tunnel-ssh": "^5.1.1"
  },

or this if you're using npm (I assume this will work the same... I don't use npm):
  "overrides": {
    "db-migrate": {
      "tunnel-ssh": "^5.1.1"
    }
  }


Support for scroll position stability

Resolves
Progress on https://github.com/LLK/scratch-blocks/issues/1406, which will also require a GUI PR.
Proposed Changes
Add some functions to support more stable scroll position behavior when switching sprites. These include:

get and set scaled position of the flyout
get name of the current category
get the scroll offset from the top of the current category
get position of a category by name

Out of curiosity: will there ever be a situation (microworlds? motion+stage?) where one sprite doesn't have the same categories as another?

@mrjacobbloom Good question. The GUI part of this change uses the assumption that the set of categories is always the same across sprites and stage- but there's no dependency on that fact here in   scratch-blocks (this PR just provides helper functions).


Workaround deprecated variant in idn_to_* functions & PHP 7.2 support

As discussed in #105.

Just a friendly ping 🏓

pong 🏓

Thanks for merging! :)


refactor Request#prepare!

  If anyone has better ideas on a convention for it, I'm all ears.  I recently added a Hurley::Response#complete! method too.  Both are intended to be called by internal hurley code or adapters, and not by users directly.

Of the build, setup, prepare usual suspects, I don't mind prepare here.


elaborate on the two makefiles in README.md?

see also

https://github.com/microbiomedata/nmdc-schema/pull/1210

Fixed in https://github.com/microbiomedata/nmdc-schema/pull/1213


MM-30493 Add support for English Australian

Adding English Australian to the languages after @enahum modified the language selector supporting language variations now.
This replaces https://github.com/mattermost/mattermost-mobile/pull/5237
Added support for English Australian

Hello @ctlaltdieliet,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

Do we have ghe translation file ready? Can it be included in the PR?

I see it is available in https://github.com/mattermost/i18n-wip/tree/master/mattermost-mobile
But @metanerd handles the merging of the translations

/update-branch

@enahum Let me know what I should review. This language is not yet in v5.36 (June) release.

@amyblais just making you aware and so that you can decide in which release this gets shipped ;)

I think this is fine for v1.45, I'm 0/5.

Building app in separate branch.

@enahum It keeps on failing to build iOS app.

@josephbaylon ha... npm 7 attacking us..
I do have an npm 7 PR ready for submission, but in the meantime I'm going to add something on master to force the CI to use npm 6, then we can update this branch and rebuild it.

/update-branch

Building app in separate branch.

@josephbaylon great catch.. @metanerd the file name is wrong, it should have a dash and not an underscore....

The file is generated by Weblate. I think it would be easier to adapt the code.

Building app in separate branch.

@ctlaltdieliet please can you resolve the conflicts ? basically remove package-lock.json from this PR


expressionProperties - Unexpected identifier

I'm submitting a ...  (check one with "x")
[ ] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[x] support request

Hi,
I am trying to set some templateOptions values based on formState using Expression Properties. I get the "unexpected identifier" when I use inline expression. However, when using an arrow callback function it works fine.
Here's a StackBlitz to see it.
Appreciate checking it out.
Thanks

please provide a valid StackBlitz example :pray:

@aitboudad I must have pasted wrong URL :-)
I need to set min on a DatePicker based on formState.
https://stackblitz.com/angular/ybqpjakdajx

I need a full example to avoid wasting my energy :smile: please!

Hi @aitboudad I did above, check the url please: https://stackblitz.com/edit/angular-xufvhd-5vznry

set today in formState:
export class AppComponent {
  form = new FormGroup({});
  model: any = {};
  options: FormlyFormOptions = {
    formState: {
      limitDate: true,
      today: new Date()
    }
  };
  fields: FormlyFieldConfig[] = [
    {
      key: 'Datepicker',
      type: 'datepicker',
      templateOptions: {
        label: 'Datepicker',
        placeholder: 'Placeholder',
        description: 'Description',
        required: true,
        datepickerOptions: {}
      },
      expressionProperties: {
        'templateOptions.datepickerOptions.min': `formState.limitDate ? formState.today : null`
      }
    },
  ];
}


PowerShell requires quotes around IDs

would be helpful to remind folks that {guid}  needs to be surrounded by single quotes in powershell

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

ID: c2e888de-16af-86ce-3844-b55b519aea27
Version Independent ID: 97cbb0fb-8c60-afe6-5170-0bfcc75a8613
Content: Adding Boot Entries
Content Source: windows-driver-docs-pr/devtest/adding-boot-entries.md
Service: unspecified
GitHub Login: @nabazan-microsoft
Microsoft Alias: windowsdriverdev

Thanks @sdwarwick for this idea.  I took a quick glance at the page, but I'm not familiar with this one.  I see a lot of possible places where we could put such a note, but since you ran into the issue yourself, is there a particular spot in there where you think it would be most useful?  You can submit a PR if you like.

Thanks @sdwarwick, I added a parenthetical with this tip to https://docs.microsoft.com/windows-hardware/drivers/devtest/adding-boot-entries.  Should be live in a few minutes.  To see it, just search for PowerShell.


SSL connection always disable

Commit 25 on repository adapters removes the ability to set SSL mode because is fixed to disable.
So, if I try to connect using SSL mode in require mode the following error is returned.
{
	"error": "pq: no pg_hba.conf entry for host \"xxx.xxx.xxx.xxx\", user \"foo\", database \"bar\", SSL off"
}

Feel free to send a pull request
Em sáb, 2 de dez de 2017 às 10:02, Tiago Temporin<EMAIL_ADDRESS>escreveu:

Commit 25 on repository adapters removes the ability to set SSL mode
because is fixed to disable.
So, if I try to connect using SSL mode in require mode the following error
is returned.
{
"error": "pq: no pg_hba.conf entry for host "xxx.xxx.xxx.xxx", user "foo", database "bar", SSL off"
}
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/prest/prest/issues/250, or mute the thread
https://github.com/notifications/unsubscribe-auth/AEpfGe7r_70o0f1KVPH1gQGNbKbS3hUpks5s8TxYgaJpZM4QzSBe
.


Your account will be suspended for two days

You will receive this message:
Your account has been suspended for scripting or otherwise initiating downloads against our web player APIs. We'd appreciate it if you would halt your script or disable any browser plugin responsible for the activity. Offline viewing is available through our iOS and Android apps.
To reactivate your account, you'll need to click the button below to visit the Frontend Masters site and re-accept our Terms of Service. After you've accepted, there will be a waiting period of up to two business days before your account will be restored.

I got suspended July 5. Havn't been restored up till now. What happened with you?

Got a warning on this too. Wondering if there's a way we can replicate how their Android App access the API 👀

Your account will open again after 2 or 3 days, but if you try to download again, your subscription will expire immediately.

@ahelmi365 Is their any work around to bypass this suspension???? I tried to download the video the breaks of 2-4 hours. Downloaded 10 videos. On the next day got a message of suspension...


beta = 0 behaviour

Currently beta = 0 is not handled as a special case. It should be. When beta = 0, the operation should be C = alpha*A*B and not C =  alpha*A*B + beta*C, which is different when nans are present.

FYI. We are seeing nans appear randomly for some convolutions. This could explain one possible cause.

This has been corrected in commit 62e247cbfb7b57f78fb0eb14d824d11c9cc913bf on master. I hope this fixes the nans in the convolutions.

Works on my end. Thanks.


Get information from other accounts in Google Chrome

Hi I have 3 accounts in Google Chrome and when I execute the BrowserAnalyzer it only gets the info of the main account. Is there any way to get the info of the other 2 accounts?
Thanks in advance.

Hello @EmilioCiber, thank you for using ForensicMiner. Currently, there is no feature to retrieve all logged-in users from Chrome. However, we can address this request. We will notify you once we begin working on it and keep you updated on the progress of integrating this feature into the new ForensicMiner update. Thank you for your patience.


How to build main app with several Cocoa Touch Frameworks?

Question Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

✅ fastlane environment ✅
Stack

Key
Value

OS
10.14.4

Ruby
2.2.4

Bundler?
false

Git
git version 2.21.0

Installation Source
~/.fastlane/bin/bundle/bin/fastlane

Host
Mac OS X 10.14.4 (18E226)

Ruby Lib Dir
~/.fastlane/bin/bundle/lib

OpenSSL Version
OpenSSL 1.0.2g  1 Mar 2016

Is contained
false

Is homebrew
true

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
10.2

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE
en_US.UTF-8
✅

fastlane files:
`./fastlane/Fastfile`
#    Fastlane documentation https://docs.fastlane.tools
default_platform(:ios)
platform :ios do

lane :match_test_develop do |options|
  match(
    app_identifier: options[:app_identifier],
    type: "development",
    readonly: true
  )
end

lane :match_test_appstore do |options|
  match(
    app_identifier: options[:app_identifier],
    type: "appstore",
    readonly: true
  )
end

lane :test_release do |options|
  increment_build_number(build_number: options[:build_number])
  enable_automatic_code_signing
  match_test_develop(app_identifier: options[:app_identifier])
  match_test_appstore(app_identifier: options[:app_identifier])
  gym(
    clean: true,
    include_bitcode: false,
    workspace: "PROJECT.xcworkspace",
    scheme: options[:scheme],
    configuration: options[:configuration]
  )
end

end

No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.120.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

slack-notifier
2.3.2

atomos
0.1.3

CFPropertyList
3.0.0

claide
1.0.2

colored2
3.1.2

nanaimo
0.2.6

xcodeproj
1.8.2

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

unicode-display_width
1.1.3

terminal-table
1.7.3

plist
3.5.0

public_suffix
2.0.5

addressable
2.6.0

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.6.5

tty-cursor
0.6.0

tty-spinner
0.9.0

babosa
1.0.2

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

excon
0.62.0

faraday
0.12.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20170404

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.1.5

gh_inspector
1.1.3

json
1.8.1

mini_magick
4.5.1

multi_json
1.13.1

multi_xml
0.6.0

rubyzip
1.2.2

security
0.1.3

xcpretty-travis-formatter
0.0.4

dotenv
2.6.0

bundler
1.14.6

faraday_middleware
<IP_ADDRESS>

naturally
2.2.0

simctl
1.6.5

uber
0.1.0

declarative
0.0.10

declarative-option
0.1.0

representable
3.0.4

retriable
3.1.2

mime-types-data
3.2018.0812

mime-types
3.1

jwt
2.1.0

signet
0.11.0

memoist
0.16.0

os
1.0.0

googleauth
0.6.7

httpclient
2.8.3

google-api-client
0.23.9

google-cloud-env
1.0.5

google-cloud-core
1.3.0

digest-crc
0.4.1

google-cloud-storage
1.16.0

emoji_regex
1.0.1

libxml-ruby
3.0.0

psych
2.0.8

generated on: 2019-04-16

Question Subject
How to "building" / "signing" / "provision profiling" the Cocoa Touch Frameworks when building the app? As I know the frameworks don't need a "Provisioning profile".
Question Description
I have an application with several Cocoa Touch Frameworks in it. Some code in frameworks and other in the project.
Folder and project structure:
...
FRAMEWORK1/framework1.xcodeproj
FRAMEWORK2/framework2.xcodeproj
project.xcworkspace
project.xcodeproj
...

All frameworks are linked, etc and work on simulator and devices when I build it.
I use match and git for certificate and provisioning profile.
When I try to build app with gym I got error.
Check dependencies
Code Signing Error: Provisioning profile "iOS Team Provisioning Profile: PROJECT.test" doesn't include signing certificate "iPhone Developer: USER (23##234#@$@#$)".
Code Signing Error: Code signing is required for product type 'Application' in SDK 'iOS 12.2'
Code Signing Error: Code signing is required for product type 'Application' in SDK 'iOS 12.2'
Code Signing Error: Code signing is required for product type 'Application' in SDK 'iOS 12.2'
Code Signing Error: Code signing is required for product type 'Application' in SDK 'iOS 12.2'
Code Signing Error: Code signing is required for product type 'Application' in SDK 'iOS 12.2'
Code Signing Error: Code signing is required for product type 'Application' in SDK 'iOS 12.2'
Code Signing Error: Code signing is required for product type 'Application' in SDK 'iOS 12.2'
Code Signing Error: Code signing is required for product type 'Application' in SDK 'iOS 12.2'
Code Signing Error: Code signing is required for product type 'Application' in SDK 'iOS 12.2'

Try to add export_options, but it's not help me on CI :(


Quick query about polygon([points])...

Googled this, but nothing came up. I have become so used to your attachment parameters anchor and spin which have proved indispensable for my parameter based work flow, finding it easier to comprehend and remember descriptive variables than actual measurements. I use the overrides of your replacement modules for 2D primitives like circle() and rect() etc. a fair bit. I was wondering how much work it would be to add these parameters to polygon(). I have also found that shell2d(), which I like to use for adjusting clearance rather than the global $slop variable, seems to only work on individual shapes and not as a group.
If I am being dense or missing the obvious, I would be grateful for a solution . The issue is trivial, so I can happily  live without the arguable convenience of the additional parameters.
Ciao
Dorian

Instead of polygon() use region() as a replacement that supports attachment parameters.
shell2d() works on the geometry that you give it as a unit, so I'm not sure what you mean.

Thanks, having a look at region, should fit the bill. I will have a go. I'm not sure, where or when I encountered this problem, I tried to recreated this quickly, but it worked as I originally expected. I will go through my files to see if I can find the example, when I return home to my desktop. Currently busy away on a quick adventure in Borneo. I am closing this ticket and if I encounter the badly worded issue above, I will file a new ticket...
Many thanks
Dorian


Adding spectrogram generation, autolabeling and training code

@monag-ucberkeley @anarkiwi This should possibly be in a separate repo to avoid licensing issues since multiple imports are AGPL. We should discuss our plan for this type of code today.

Closing. Code moved to different repo.


With noEmit: true the Compile failed but emit succeeded message should not show

Currently it does which is a bit misleading.

Have the same

Also getting this issue when trying to work on Angular 2/NativeScript project.
My tsconfig.json file looks like this:
{
    "compilerOptions": {
        "module": "commonjs",
        "target": "es5",
        "sourceMap": true,
        "experimentalDecorators": true,
        "emitDecoratorMetadata": true,
        "noEmitHelpers": true,
        "noEmitOnError": true
    },
    "exclude": [
        "node_modules",
        "platforms",
        "**/*.aot.ts"
    ]
}

Version of atom-typescript is 10.1.13. Of course, removing "noEmitOnError": true resolves the issue but it seems like there's enough traction here to warrant another look at this bug perhaps. Thanks for your help and effort @basarat.


Webpack template does not work with native modules on Windows

Pre-flight checklist

[X] I have read the contribution documentation for this project.
[X] I agree to follow the code of conduct that this project uses.
[X] I have searched the issue tracker for a bug that matches the one I want to file, without success.

Electron Forge version
6.0.0-beta.64
Electron version
v19.0.7
Operating system
Windows 10 (19044)
Last known working Electron Forge version
No response
Expected behavior
Webpack template should work with native modules on Windows
Actual behavior
Webpack template fails with native modules because it uses Linux paths on Windows
Steps to reproduce

As per steps on the documentation, run: npx create-electron-app my-new-app --template=webpack
Add a native module npmjs package, like this one: yarn add @nut-tree/nut-js
Package application using yarn package.

Received error:
WARNING in ./src/main.js
Invalid dependencies have been reported by plugins or loaders for this module. All reported dependencies need to be absolute paths.
Invalid dependencies may lead to broken watching and caching.
As best effort we try to convert all invalid values to absolute paths and converting globs into context dependencies, but this is deprecated behavior.
Loaders: Pass absolute paths to this.addDependency (existing files), this.addMissingDependency (not existing files), and this.addContextDependency (directories).
Plugins: Pass absolute paths to fileDependencies (existing files), missingDependencies (not existing files), and contextDependencies (directories).
Globs: They are not supported. Pass absolute path to the directory as context dependencies.
The following invalid values have been reported:
 * "G:/t2/new-app/node_modules/@babel/runtime/LICENSE"
 *<EMAIL_ADDRESS> *<EMAIL_ADDRESS> * and more ...

Additional information
Vercel webpack asset relocator loader v1.7.1 has a fix for Windows path handling. See commit: https://github.com/vercel/webpack-asset-relocator-loader/commit/38f839f36b6e80c925194cb8442b6b0f0f3f2e31
But the webpack template for electron is pinned to version 1.7.0 (see docs), therefore this fix is missing from there. The docs linked above say that:

Warning: Electron Forge needs to monkeypatch the asset relocator loader in order for it to work with Electron properly, so the version has been pinned to ensure compatibility. If you upgrade that version, you do so at your own risk.

Now I upgraded the package to 1.7.2 and still got the same error on packaging. I wonder if the monkeypatch is interfering with vercel's patch.
Would appreciate any quick workarounds to solve this, while a proper fix is implemented.

Issue description was updated 20 minutes after posting to reflect accurate steps on reproducing the issue.

Looks like the patch in question is here: https://github.com/electron-userland/electron-forge/blob/master/packages/plugin/webpack/src/util/AssetRelocatorPatch.ts Will see if I can get this to work with the newer version of the plugin

@GaurangTandon Sorry, I actually wasn't able to reproduce this issue on Windows using the steps you mentioned here:

Run: npx create-electron-app my-new-app --template=webpack
Add a native module npmjs package, I added this one: yarn add @nut-tree/nut-js
Package application using yarn package.

Packaging works fine for me on Windows 10 using forge beta.64. Does this failure happen on the package step for you, or after trying to open the app? Do you have a sample repo I could take a look at (although it sounds like this was happening in the template app for you)?

Hi @VerteDinde , I am very surprised as now I am also unable to reproduce the issue. Only Electron seems to have updated to v19.0.8 in the meantime, but the update seems irrelevant to this issue.
I apologize I don't have any more information. Feel free to close this ticket if you wish to.

@GaurangTandon No worries at all, really appreciate both the report and the fast response! Let us know if you have any issues in the future 🙂


missing layer output_shape using Theano backend

Is it a known issue that Theano backend does not return layer output_shape?
Using Theano backend.
Model loaded.
input_1 (None, 3, None, None)
block1_conv1 (None, 64, None, None)
...

No problem with Tensorflow.
Using TensorFlow backend.
Model loaded.
input_1 (3, 400, 400, 3)
block1_conv1 (3, 400, 400, 64)
...

Here is an example to verify
https://gist.github.com/ink1/eeb47f06d4726ae1c9674779d097e763
which is based on
https://github.com/fchollet/keras/blob/master/examples/neural_style_transfer.py
The difference is essentially
45a46
> import sys
125a127,134
>
> shape_dict = dict([(layer.name, layer.output_shape) for layer in model.layers])
>
> for layer in model.layers:
>     s = shape_dict[layer.name]
>     print( layer.name, s )
>
> sys.exit(0)

the output is still the same with keras 2.0.4 and theano 0.9.0


Add rendezvous mode ethernet in example chip-tool (#5733)

Problem
The example chip-tool doesn't support the rendezvous mode ethernet.
Summary of Changes
Add the ethernet mode.
Fixes #5733

This seems identical to softap - what is the long term plan for them? Will we start having different options between softap and ethernet?
I believe chip-tool is for testing only, so technically it looks like we only need 'ip-based' and `ble-based' provisioning (and let ip mean both softap and ethernet ... or even devices somehow already on wifi, like ones put on wifi through some legacy means).
Thoughts? Will be there differentiators or should we rename softap/ethernet to something common?

Signify Classified - Internal
Hello Andrei,
You are probably right.
From: Andrei Litvin @.>
Sent: donderdag 1 april 2021 15:51
To: project-chip/connectedhomeip @.>
Cc: Paul Zander @.>; Author @.>
Subject: Re: [project-chip/connectedhomeip] Add rendezvous mode ethernet in example chip-tool (#5733) (#5752)
CAUTION: This email is from outside the organization. Do not click on links or open attachments unless you trust the sender.
This seems identical to softap - what is the long term plan for them? Will we start having different options between softap and ethernet?
I believe chip-tool is for testing only, so technically it looks like we only need 'ip-based' and `ble-based' provisioning (and let ip mean both softap and ethernet ... or even devices somehow already on wifi, like ones put on wifi through some legacy means).
Thoughts? Will be there differentiators or should we rename softap/ethernet to something common?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/project-chip/connectedhomeip/pull/5752#issuecomment-811922549, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQSINL7557SO37CH55USFPDTGR233ANCNFSM42G6CIGQ.

The information contained in this email may be confidential and/or legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this email is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original email.

This seems identical to softap - what is the long term plan for them? Will we start having different options between softap and ethernet?
I believe chip-tool is for testing only, so technically it looks like we only need 'ip-based' and `ble-based' provisioning (and let ip mean both softap and ethernet ... or even devices somehow already on wifi, like ones put on wifi through some legacy means).
Thoughts? Will be there differentiators or should we rename softap/ethernet to something common?

They aren't the same; softap has to connect the local station to the softap.


Allow to add description to disable comment

I would like to be able to leave the intent of disable as a code comment.

ref: https://mysticatea.github.io/eslint-plugin-eslint-comments/rules/require-description.html

Consideration
What should happen if rule-b is further disabled on a line where rule-a has already been disabled with disable description?
Maybe it'll be like this?
// eslint-disable-next-line rule-a -- description for rule-a
  |||
  vvv
// eslint-disable-next-line rule-a, rule-b -- description for rule-a, description for rule-b