DOTJ022F with no filters specfied - document is missing XML schema.

Expected Behavior
I've got a program that creates a bunch of .dita files and I wanted to see them formatted.
So, I downloaded dita-ot 4.0.1 and Java JDK 17.
I had to patch the dita.bat file because my system has to be set up to run an older JDK (just hardcoding a value for the _JAVACMD variable because the built in code wasn't finding the JDK 17 installation).
Then I ran:
dita -i CP_EVENT_TYPE.dita -f html5
...at this point I expected it to write out a nice .html file I could examine in a web browser to review the results of my programmatically generated markup.
Actual Behavior
What I got was:
'Error: Failed to run pipeline: [DOTJ022F][FATAL] Failed to parse the input file 'file:/D:/xxx/dita/DRLxx/CP_EVENT_TYPE.dita' because all of its content has been filtered out. This will happen if the input file has filter conditions on the root element, and a ditaval excludes all content based on those conditions.'
What? I don't have any filters or a ditaval file (even if I knew what one of them was).
Creating and using a .ditamap to reference the .dita file:
<map>
  <title>CP EVENT TYPE MAP</title>

This is the table.

  <topicref href="CP_EVENT_TYPE.dita"/>
</map>

...still the same error.
I then created a fake.ditaval file:
<val>
<prop action="include"/>
</val>

...which, as I read the docs, should tell it to include everything (not that I think I should need to create it).

It's also worth nothing that dita is searching for it relative to the dita installation directory, not the directory where I'm issuing the dita command (which is where my .dita and .ditamap files are and are resolved relative to).

Ran it as:
dita -i CP_EVENT_TYPE.ditamap -f html5 --args.filter=fake.ditaval
Still the DOTJ022F error.
The filtering appears to be broken.
Possible Solution
If it's broken, fix it.
If it isn't broken, make the error messages more helpful.
Steps to Reproduce

Clean install of Dita-OT 4.0.1 and Java JDK 17 onto a windows 10 box.
Create a simple.dita file
From the windows command line, try and convert it to html5.
Create a .ditamap file with a topicref to the .dita file.
Same problem.
Create a fake.ditaval (in the dita installation directory)
Same problem.

Copy of the error message, log file or stack trace
Error: Failed to run pipeline: [DOTJ022F][FATAL] Failed to parse the input file 'file:/D:/xxx/dita/DRLxx/CP_EVENT_TYPE.ditamap' because all of its content has been filtered out. This will happen if the input file has filter conditions on the root element, and a ditaval excludes all content based on those conditions.
Environment

DITA-OT version: 4.0.1
Operating system and version:
Windows 10
How did you run DITA-OT?
Windows command line
dita -i CP_EVENT_TYPE.dita -f html5 --args.filter=fake.ditaval
Transformation type:
html5, but I don't think it's getting that far

@mikc-21csw all DITA topics and map must have references to the DITA DTDs or schemas.
How does your "CP_EVENT_TYPE.dita" topic look like?
A minimal DITA topic should have a DOCTYPE declaration before the root element:
<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
<topic id="topic_a3g_xmx_xvb">
   <title></title>

and a minimal DITA Map also a map-specific DOCTYPE declaration:
<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd">
<map>
    <title></title>
</map>

The DTD/schema references for edited DITA content are required because the schemas provide default attribute values necessary for publishing. So in this case as those default attribute values are missing from the root elements, the processing engine does not know the processed content is actually DITA so it returns that confusing error message.
There are other error messages complaining about not recognizing the elements as DITA further up in the console output though, they state:
  [gen-list] [DOTJ030I][INFO] No 'class' attribute for was found for element '<topic>'. The element will be processed as an unknown or non-DITA element.

About the DITAVAL filter file, by default everything is included so indeed a ditaval filter file which includes everything is not useful.
About this remark:
   just hardcoding a value for the _JAVACMD variable because the built in code wasn't finding the JDK 17 installation

Like most scripts starting a Java VM, the script looks for the value of the "JAVA_HOME" environmental variable. So maybe you can manually set that in your operating system to be the Java 17 installation folder.

Thanks, that was enough to get it basically working.
Dita went through the file to indicate that a /p was missing, but never said anything about the DOCYPE not being defined.  The only error messages I got was the DOTJ022F error, which was completely misleading.
LaTex was so much simpler :-(

 Thanks, that was enough to get it basically working.

With pleasure, there is a Learning DITA course which may help you further:
https://learningdita.com/
Most people using the DITA XML standard use it with a commercial visual editor tool which incorporates the DITA Open Toolkit. I work for Oxygen XML Editor, if you want to see videos about how people use our tool to visually edit DITA content, there are a bunch of videos here: https://blog.oxygenxml.com/topics/learnDita.html
   Dita went through the file to indicate that a /p was missing, but never said anything about the DOCYPE not being defined. The only error messages I got was the DOTJ022F error, which was completely misleading.

I agree, the publishing engine should have a more specific error message in such cases. I would propose something like:
   [ERROR] No 'class' attribute for was found for root element '<topic>'. Usually this means that a DTD or schema was not associated to the file.

and ideally such an error should break the processing.
  LaTex was so much simpler :-(

For me DITA is easier as I do not know LaTex :) I think one big difference is that DITA XML has lots of reuse capabilities, the possibility to use the same element in multiple places, to apply filters and obtain multiple publications from the same input files, it's more useful for technical documentation than LaTex which I would consider (and I may be wrong) more appropriate for scientific publications and obtaining PDFs.

I have also been confused by this behavior.
It might be nice to repurpose this issue into an enhancement request. Given three topics:

topic_filtered_global.dita - filtered out by DITAVAL global filtering
topic_filtered_branch.dita - filtered out by DITAVAL branch filtering
topic_unknown.dita - bad/missing schema

the messages are as follows:
 [gen-list] [DOTJ021E][ERROR] File 'file:topic_filtered_global.dita' will not generate output because because all content has been filtered out by DITAVAL "exclude" conditions, or because the file is not valid DITA.
 [gen-list] [DOTJ021E][ERROR] File 'file:topic_unknown.dita' will not generate output because because all content has been filtered out by DITAVAL "exclude" conditions, or because the file is not valid DITA.
[topic-fragment] Failed to process XML filter: Failed to transform file:temp/dita/topic_filtered_branch.dita: Premature end of file.
[move-meta] file:map.ditamap:6:50: [DOTX023W][WARN]: Unable to retrieve navtitle from target: 'topic_filtered_global.dita'.
[move-meta] file:map.ditamap:6:50: [DOTX027W][WARN]: Unable to retrieve linktext from target: 'topic_filtered_global.dita'.
[move-meta]  Error reported by XML parser: Premature end of file.
[move-meta] Error reported by XML parser processing file:temp/dita/topic_filtered_branch.dita: Premature end of file.
Error: Failed to run pipeline: Failed to transform document: Error reported by XML parser processing file:temp/dita/topic_filtered_branch.dita: Premature end of file.

Maybe inside gen-list and topic-reader, the ordering of @class attribute checks and filtering could be adjusted to improve the messaging.
Testcase is here: 4087.zip
To run: dita --project project.xml

@mikc-21csw - maybe you could change the issue title to something like "Issue a clearer message for files with bad/missing XML schema" now that the issue is better understood?
In your original situation, would a message like this have helped you better understand the issue?
 [gen-list] [DOTJ???E][ERROR] File 'file:topic_unknown.dita' will not generate output because the file has a bad or missing XML schema.

I've updated the title, but left the observable symptom in it.
The message you propose would certainly be a lot better than the message we're currently getting.
I'd almost expect a rejection much earlier - document has no doctype specified, it is not a valid dita document and cannot be processed.
That would point me directly to the problem - no DOCTYPE - rather than let me think it's a valid document that dita, for whatever reason, is not processing properly.
Also worth nothing that the Oxygen error for the document doesn't indicate that the document is invalid either - only the inline 'tag' view complains.

@mikc-21csw From what I tested if I open in Oxygen an XML file which does not have the DOCTYPE declaration and use the toolbar "Validate" button Oxygen reports this validation problem:
  There is no schema or DTD associated with the document. You can create an association either with the Associate Schema action or ....


Full Screen Lightbox scrolls page back to top on open

Describe the bug
Whenever I open an image into the full screen lightbox the page just scrolls to the top.
https://github.com/igordanchenko/yet-another-react-lightbox/assets/30993234/030e4bc5-3d48-4f52-b607-dc2060a3edd2
<Lightbox
            slides={uploadedImages.map((image) => {
              return !image.isDemoImage
                ? {
                    src: "https://storage.googleapis.com/${
                      import.meta.env.VITE_BUCKET_URL
                    }/${eventId}/${image._id}",
                  }
                : {
                    src: image._id,
                  };
            })}
            open={index >= 0}
            index={index}
            close={() => setIndex(-1)}
            reactModalProps={{ shouldReturnFocusAfterClose: true }}
            plugins={[Fullscreen, Slideshow, Thumbnails, Zoom]}
          />

Expected behavior
Not to scroll anywhere keep the page at the scroll level it is.
How to reproduce
Seems only replicable on my end I tested on the website and it doesn't seem to do that.
Screenshots / Logs
No response
Additional context
No response

After some debugging I can tell that line 1324 from index.js "node.scrollTop" does the scrolling is there a prop that stops doing that, maybe I missed it.

I have the same issue, please let me know if you manage to solve it. I'll do the same :raised_hands:

@BogdanFalk @eloyra are you able to share a live demo or provide a sandbox with reproducible example?

Well I retried the with void(node.offsetHeight); and its the same I will try and create an example in sandbox today and post it here.

I didn't have time to create an example yet, but after trying different stuff I'm no longer sure it's because of that line.
In my case it seems related to the yarl__no_scroll class that is added to the body when opening the lightbox. However, I got very erratic behavior when I tried to fix it.
If I add these CSS lines to my body directly, I no longer get the "scroll to top" error:
  overflow: inherit !important;
  overscroll-behavior: inherit !important;
  height: 100% !important;
  padding-right: 0 !important;

However, if I try to override the yarl__no_scroll class or add my own (to apply said styles) at the same time, I get some erratic behavior like there is a race condition when adding the different styles, and it doesn't work all the time, it's very strange.
In any case, the issue seems related with the fact that by setting overflow to hidden you basically remove the the scrollbar and reset the scroll to the top.

Thank you both for the updates! I think we are on the right track. When the lightbox opens, it adds the yarl__no_scroll class to the document <body> to hide the vertical scrollbar and prevent document body underneath the lightbox from scrolling on iOS. There is an escape hatch that lets you completely disable this functionality:
<Lightbox
  plugins={[({ remove }) => remove("no-scroll")]}
  // ...
/>

However, I'd love to reproduce this issue on my end and come up with a proper fix.
Can you post your CSS styles that you apply to your <html> and <body> tags?

I think this is everything being applied to the html and body.

Thank you for providing your CSS styles. I'm able to reproduce this issue now.
Can you please test the following patch-package patch and see if it resolves the issue in your case?
https://gist.github.com/igordanchenko/00e603c5c12014896f3ace8962899f55

Thanks for the quick work! Very cool.
I'm on holidays this week, but I'll check it asap when I come back.

@igordanchenko I was able to test your patch.
It looks like you are on the right track, and now the scroll position is preserved, however there is still something going wrong.
As you can see in the screenshots, there is a bad interaction with the header and sidebars, which is somewhat worse in the third screenshort, where you can see part of them on the top of the screen:

Screenshots

They are all sticky elements, so that's probably the issue.

CSS

The left sidebar styles:
    position: sticky;
    top: 0;
    display: flex;
    flex-direction: column;
    width: var(--sidebar-width-open);
    min-height: 100vh;
    background: #151719;
    box-shadow: inset -1px 0 0 #383d42;

The right sidebar styles:
    top: var(--desktop-header-height);
    height: calc(100dvh - var(--desktop-header-height) - 1px);
    position: sticky;
    border-left: 1px solid #383d42;

The header styles:
    position: sticky;
    top: 0;
    z-index: 6;
    -webkit-backdrop-filter: blur(5px);
    backdrop-filter: blur(5px);

Let me know if I can do anything else to help.

@eloyra thank you for testing the patch and following up.

Let me know if I can do anything else to help.

To eliminate the guesswork on my side, do you mind creating an isolated demo on codesandbox.io that replicates your layout? That would help a lot.

Sure, it might take me a few days to find the time, but I'll get it done.

@eloyra as you pointed out, there are additional issues with sticky elements, and fixing their position seems too intrusive within the scope of this library. With that being said, I'm not inclined to proceed with the above patch.
At this point, I can suggest the following solutions to the original issue:

Disable the no-scroll module with plugins={[({ remove }) => remove("no-scroll")]} (I'll probably add a config option to make it more straightforward)

Get rid of the html, body { height: 100% } as some sources recommend

https://greggod.medium.com/css-do-not-put-height-100-on-the-body-html-e36bda3551b3
and replace with either
body {
  min-height: 100vh;
  min-height: 100dvh;
}

or
html {
    min-height: 100%;
    display: flex;
    flex-direction: column;
}

body {
    flex-grow: 1;
}

https://dev.to/fenok/stretching-body-to-full-viewport-height-the-missing-way-2ghd

@BogdanFalk please let me know if you have any feedback

Hello there @igordanchenko!
I'm so sorry that I never got around to that Sandbox, and the latest replies got lost in mail.
I've updated the code to use the new configuration option, works great :muscle:
I've also explored the two approaches you suggest and they made no change whatsoever relative to our current CSS setup, but they were interesting reads nontheless, thanks for the suggestions.

Thank you for the feedback @eloyra

I have the same problem, I tried the fixes mentioned here, but sometimes the screen scrolls to the top when I open the image.
This is my component. I'm using MantineUI.
"react": "^16.12.0"
"yet-another-react-lightbox": "^3.15.5"
"mobx": "^5.15.0",
"mobx-react": "^6.1.4",
const GallerySection = observer(({ imagens, identificador }: GallerySectionProps) => {
const { classes, theme } = useStyles();
const [index, setIndex] = React.useState(-1);
const slides = imagens.map((photo: LandpageGaleriaDadosDto) => {
return {
src: photo.linkImagem,
title: photo.legenda,
};
});
return (
<>

Galeria

    <SimpleGrid
      cols={3}
      mt={50}
      breakpoints={[
        { maxWidth: '62rem', cols: 3 },
        { maxWidth: '48rem', cols: 2 },
        { maxWidth: '36rem', cols: 1 },
      ]}
    >
      <GalleryCards
        imagens={imagens}
        setIndex={(i: number) => {
          setIndex(i);
        }}
      />
    </SimpleGrid>

    <Lightbox
      noScroll={{ disabled: true }}
      plugins={[Captions]}
      index={index}
      slides={slides}
      open={index >= 0}
      close={() => setIndex(-1)}
    />
  </Container>
</>

);
});


Bugfix/101/sp 1 write unit test for categories page

Created unit tests for the component

The code in this PR and PR #114 seems to be the same, or at least quite similar 😅 Could there be something wrong with the commits? Also, remember to link the issue.

There are 2 tests: one for the language container, 1 for the Categories container. Maybe they has been "connected" comehow.


CSS

CSS
User Story
As a boot camp student
I want the prework notes to be structured on a webpage
So that I can easily find and read the information
Acceptance Criteria
GIVEN a Prework Study Guide website
WHEN I view the Study Guide
THEN I see a dark blue header and footer, and four boxes with a shadow

added feature/add-css


Webpack fails to build superset-frontend for production build

Done npm ci
Node version v16.20.2
Machine : Windows 11
Tried to run npm run build
Observation : Build hangs at 94%

<EMAIL_ADDRESS>build
cross-env NODE_OPTIONS=--max_old_space_size=8192 NODE_ENV=production BABEL_ENV="${BABEL_ENV:=production}" webpack --mode=production --color

[Superset Plugin] Use symlink source for @superset-ui/chart-controls @ ./packages/superset-ui-chart-controls
[Superset Plugin] Use symlink source for @superset-ui/core @ ./packages/superset-ui-core
[Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-calendar @ ./plugins/legacy-plugin-chart-calendar
[Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-chord @ ./plugins/legacy-plugin-chart-chord
[Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-country-map @ ./plugins/legacy-plugin-chart-country-map
[Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-event-flow @ ./plugins/legacy-plugin-chart-event-flow
[Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-heatmap @ ./plugins/legacy-plugin-chart-heatmap
[Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-histogram @ ./plugins/legacy-plugin-chart-histogram
[Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-horizon @ ./plugins/legacy-plugin-chart-horizon
[Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-map-box @ ./plugins/legacy-plugin-chart-map-box
[Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-paired-t-test @ ./plugins/legacy-plugin-chart-paired-t-test
[Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-parallel-coordinates @ ./plugins/legacy-plugin-chart-parallel-coordinates
[Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-partition @ ./plugins/legacy-plugin-chart-partition
[Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-rose @ ./plugins/legacy-plugin-chart-rose
[Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-sankey @ ./plugins/legacy-plugin-chart-sankey
[Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-sankey-loop @ ./plugins/legacy-plugin-chart-sankey-loop
[Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-sunburst @ ./plugins/legacy-plugin-chart-sunburst
[Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-world-map @ ./plugins/legacy-plugin-chart-world-map
[Superset Plugin] Use symlink source for @superset-ui/legacy-preset-chart-deckgl @ ./plugins/legacy-preset-chart-deckgl
[Superset Plugin] Use symlink source for @superset-ui/legacy-preset-chart-nvd3 @ ./plugins/legacy-preset-chart-nvd3
[Superset Plugin] Use symlink source for @superset-ui/plugin-chart-echarts @ ./plugins/plugin-chart-echarts
[Superset Plugin] Use symlink source for @superset-ui/plugin-chart-handlebars @ ./plugins/plugin-chart-handlebars
[Superset Plugin] Use symlink source for @superset-ui/plugin-chart-pivot-table @ ./plugins/plugin-chart-pivot-table
[Superset Plugin] Use symlink source for @superset-ui/plugin-chart-table @ ./plugins/plugin-chart-table
[Superset Plugin] Use symlink source for @superset-ui/plugin-chart-word-cloud @ ./plugins/plugin-chart-word-cloud
[Superset Plugin] Use symlink source for @superset-ui/switchboard @ ./packages/superset-ui-switchboard
22% building import loader ./node_modules/js-yaml-loader/index.js- Processing: C:\Users\trias\superset-forked\superset-frontend\packages\superset-ui-chart-c
\ Processing: C:\Users\trias\superset-forked\superset-frontend\src\visualizations\TimeTable\transformProps.ts

I have a similar experience before. LIkely it is in the webpack stage.
Suggest to have 8GB ram at least for the compliation.

I have a similar experience before. LIkely it is in the webpack stage. Suggest to have 8GB ram at least for the compliation.

Thanks for the reply .
Currently im running it on docker WSL .
This is my memory stats in WSL
total        used        free      shared  buff/cache   available
Mem:           9.7Gi       642Mi       8.1Gi       3.0Mi       1.0Gi       8.8Gi
Swap:          3.0Gi        59Mi       2.9Gi
Memory stats during [lean  6/10] RUN --mount=type=bind,target=./requirements/local.txt,src=./requirements/local.txt
total        used        free      shared  buff/cache   available
Mem:           9.7Gi       2.2Gi       136Mi       4.0Mi       7.4Gi       7.3Gi
Swap:          3.0Gi        62Mi       2.9Gi
Memory stats while npm run build
total        used        free      shared  buff/cache   available
Mem:           9.7Gi       4.9Gi       177Mi       4.0Mi       4.7Gi       4.5Gi
Swap:          3.0Gi        70Mi       2.9Gi
           total        used        free      shared  buff/cache   available

Mem:           9.7Gi       5.5Gi       310Mi       4.0Mi       3.9Gi       3.9Gi
Swap:          3.0Gi        70Mi       2.9Gi
After it used some swap memory
total        used        free      shared  buff/cache   available
Mem:           9.7Gi       5.8Gi       3.6Gi       3.0Mi       334Mi       3.7Gi
Swap:          3.0Gi       960Mi       2.1Gi
Then it struct at this process and the memory are released
=> [superset-node 7/7] RUN npm run build                                                                                400.1s
=> => # - Processing: src/visualizations/TimeTable/index.ts
=> => # \ Processing: src/visualizations/TimeTable/transformProps.ts
=> => # | Processing: src/visualizations/dashboardComponents/DashboardComponentsRegistry.ts
=> => # / Processing: src/visualizations/dashboardComponents/ExampleComponent/ExampleComponent.tsx
=> => # - Processing: src/visualizations/dashboardComponents/ExampleComponent/index.ts
=> => # \ Processing: src/visualizations/presets/dashboardComponents.ts
           total        used        free      shared  buff/cache   available

Mem:           9.7Gi       4.0Gi       5.3Gi       3.0Mi       420Mi       5.4Gi
Swap:          3.0Gi       868Mi       2.2Gi
Solutions or alternatives are appreciated !!

When i set my heap to     "build": "cross-env NODE_OPTIONS=--max_old_space_size=1120 NODE_ENV=production BABEL_ENV="${BABEL_ENV:=production}" webpack --mode=production --color",
The Build failed with error message at  233178 ms as follows
234.4 [26:0x5e495e0]   233178 ms: Scavenge 876.2 (1143.9) -> 874.4 (1147.9) MB, 7.2 / 0.0 ms  (average mu = 0.966, current mu = 0.648) task
234.4 [26:0x5e495e0]   233193 ms: Scavenge 880.4 (1147.9) -> 876.0 (1157.7) MB, 8.0 / 0.0 ms  (average mu = 0.966, current mu = 0.648) task
234.4 [26:0x5e495e0]   233712 ms: Mark-sweep 885.6 (1157.7) -> 878.6 (1172.7) MB, 508.4 / 0.0 ms  (average mu = 0.933, current mu = 0.243) allocation failure scavenge might not succeed
234.4
234.4
234.4 <--- JS stacktrace --->
234.4
234.4 FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
234.4  1: 0xb090e0 node::Abort() [webpack]
234.4  2: 0xa1b70e  [webpack]
234.4  3: 0xce1a20 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [webpack]
234.4  4: 0xce1dc7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [webpack]
234.4  5: 0xe99435  [webpack]
234.4  6: 0xea90fd v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [webpack]
234.4  7: 0xeabdfe v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [webpack]
234.4  8: 0xe6d072 v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [webpack]
234.4  9: 0xe65684 v8::internal::FactoryBasev8::internal::Factory::AllocateRawWithImmortalMap(int, v8::internal::AllocationType, v8::internal::Map, v8::internal::AllocationAlignment) [webpack]
234.4 10: 0xe676e1 v8::internal::FactoryBasev8::internal::Factory::NewRawTwoByteString(int, v8::internal::AllocationType) [webpack]
234.4 11: 0xe6f19c v8::internal::Factory::NewStringFromUtf8(v8::base::Vector const&, v8::internal::AllocationType) [webpack]
234.4 12: 0xcf0615 v8::String::NewFromUtf8(v8::Isolate*, char const*, v8::NewStringType, int) [webpack]
234.4 13: 0xbe8e81  [webpack]
234.4 14: 0xbe8f9d node::StringDecoder::DecodeData(v8::Isolate*, char const*, unsigned long*) [webpack]
234.4 15: 0xbe95b2  [webpack]
234.4 16: 0xd3df8e  [webpack]
234.4 17: 0xd3f3af v8::internal::Builtin_HandleApiCall(int, unsigned long*, v8::internal::Isolate*) [webpack]
234.4 18: 0x15d9f39  [webpack]
234.5 ✔ Lint done...
Dockerfile:48
46 |     COPY ./superset-frontend ./
47 |     # This seems to be the most expensive step
48 | >>> RUN npm run ${BUILD_CMD}
49 |
50 |     ######################################################################

Closing this since Superset doesn't officially support windows. If anyone wants to open PRs to support scripts/packages/docs to make Windows supported, you're welcome to open PRs and SIPs to chip away at this incrementally.

this exact issue is happening to me on macOS. Any ideas anybody?

If you're experiencing this in Docker, it's likely that you need to throw more RAM at it. I have mine set to 16GB.

It's not. I have 16GB allocated. Something definitely goes wrong toward the end of npm run build step in my docker build script, but it doesn't even give an error, it just hangs

It's not. I have 16GB allocated. Something definitely goes wrong toward the end of npm run build step in my docker build script, but it doesn't even give an error, it just hangs

We could not  able to find the root cause of the issue . It seems that when we zip download superset the build works fine but yes with some hang or delay but when we clone and run npm build it hangs forever on both docker and local webpack build stage.
Can you try for zip build and share the observation. Thanks

Didn't seem to change anything unfortunately. It gets stuck at the same file:
=> => # | Processing: src/visualizations/presets/dashboardComponents.ts

Update: build completed just fine with a complete uninstall/reinstall of docker on my machine


Investigate whether it's possible to make some of the knn indices picklable

It is possible to mmap within a pickle: https://github.com/UniNE-CHYN/mmappickle so there might be hope

Neuraxle has support for custom saving e.g. https://github.com/Neuraxio/Neuraxle-TensorFlow . Unfortunately it reinvents quite a lot of sklearn stuff. Not sure if it's possible to support this as an optional extra while staying mainly on sklearn.

Neuraxle has support for custom saving e.g. https://github.com/Neuraxio/Neuraxle-TensorFlow . Unfortunately it reinvents quite a lot of sklearn stuff. Not sure if it's possible to support this as an optional extra while staying mainly on sklearn.


build(deps): bump lru-cache from 7.18.3 to 11.0.1 in /web/ui

Bumps lru-cache from from 7.18.3 to 10.0.1.

replace LRUCache import -> { LRUCache }, see changelog
help  dependabot #14916
follow-up #12768

labels

https://github.com/prometheus/prometheus/labels/dependencies
https://github.com/prometheus/prometheus/labels/javascript
https://github.com/prometheus/prometheus/labels/component%2Fui

Hi @Nexucis, @juliusv could you take a look at the PR?
We looked at this in our bug scrub.

Hello again from the bug-scrub!  We need someone familiar with JS to review.

@arukiidou Sorry for ignoring! Looks good, happy to merge, just needs a merge conflict resolution first?

@juliusv
thankyou. I will try again

Passed. please take a llok?


fix removal of gpus from base-instance-type agg filter

Issue #, if available:
N/A
Description of changes:

base-instance-type should filter out gpu instance types if the instance-type passed in is not a gpu instance-type.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

Merging #22 into master will decrease coverage by 0.21%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #22      +/-   ##
==========================================
- Coverage   90.04%   89.82%   -0.22%
==========================================
  Files           8        8
  Lines         874      875       +1
==========================================
- Hits          787      786       -1
- Misses         57       58       +1
- Partials       30       31       +1

Impacted Files
Coverage Δ

pkg/selector/aggregates.go
92.45% <100.00%> (+0.14%)
:arrow_up:

pkg/selector/selector.go
84.36% <0.00%> (-0.95%)
:arrow_down:

Continue to review full report at Codecov.

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


linear size for block compressed dds files is calculated incorrectly

Description
This page on the DDS_HEADER structure states that dwPitchOrLinearSize is 'the total number of bytes in the top level texture for a compressed texture.', however dwPitchOrLinearSize is currently calculated based on the texture width and block size, which is incorrect.
https://github.com/baldurk/renderdoc/blob/795d7e0910056bf1971dbb8752581dc5bfa06fdf/renderdoc/common/dds_readwrite.cpp#L771-L777
Instead, it should be something like:
header.dwPitchOrLinearSize = RDCMAX(1U, ((header.dwWidth + 3) / 4)) * blockSize * depth * height / 4;

This issue is not a huge deal, because the library I am using does not use dwPitchOrLinearSize when reading files.

Steps to reproduce
Save a texture to a dds file and use a tool or library to display the header. For a 128x128x128 BC6H compressed texture I get the following:
  Header:
    flags: CAPS | HEIGHT | WIDTH | PIXELFORMAT | LINEARSIZE | DEPTH
    height: 128, width: 128, depth: Some(128)
    pitch: None  linear_size: Some(512)
    mipmap_count: None
    caps: COMPLEX | TEXTURE, caps2 VOLUME
    Pixel Format:
      flags: FOURCC
      fourcc: Some(FourCC(808540228))
      bits_per_pixel: None
      RGBA bitmasks: None, None, None, None

where linear_size should instead be 128 * 128 * 128 = 2097152.

Environment

RenderDoc version: QRenderDoc v1.13 (795d7e0910056bf1971dbb8752581dc5bfa06fdf)
Operating System: Arch Linux x86_64 5.10.16-arch1-1
Graphics API: OpenGL 4.6

That is an extremely stupidly specified field. Indeed I looked at what DirectXTex does and it seems like it calculates the slice pitch for block compressed textures, so the linear size you were expecting is also apparently wrong at least for 3D or array textures. Most likely every DDS reader will just ignore that field (at least for compressed textures) as uselessly unreliable.

@baldurk okay, thanks!


Event Dragging & Event Resizing from top

Hi Antoni
You built a very coll component and I'd like to implement in my project.
In order to do so, I'd like to know if :

When the "Event Drag" will be completed.
Indeed this is one of the most important things. If the event cannot be dragged then the VueCal
could be in certain case useless.

Will it be possible to add resize the event from the top.

I believe you must be pretty much busy and working on that component but I'm ready to donate or compensate or simply hire you to complete add some new features in your component.
Please let me know
Regards
David

Hi @PatDav,
Thank you for your feedback and interest.
Indeed I am quite busy with this lib and all the feature requests.
There are a couple of things I need to finish before implementing drag & drop:

At the moment I am refactoring the way multiple-day events work (https://github.com/antoniandre/vue-cal/commit/43e35ad0d3b000e6efc08fd5c6d7421cad45fa89), and this is very important for the future recurring events and the overall good functioning of all "segmented" events. This will also fix #78.
It needs to be done before moving to a more complex code.
Externalizing locales is already done but I need to activate it and it will change the way the lib is used, so I will release a v2.0.0 at this point along with v-slots syntax update which will require<EMAIL_ADDRESS>
Dragging events from the top will come later.
Regarding your proposition, let's discuss it via email, my email can be found in this file in the author field: https://github.com/antoniandre/vue-cal/blob/master/package.json, I will be glad to help you.
Cheers.

Any update about resizing top, please?


Fix lint issue

Description
Running the command pnpm run lint does not exit successfully because of some linting errors in the client.

Action items

Fix all errors identified from running pnpm run lint
Verify that the Client CI workflow runs successfully

Can I please be assigned to this issue @princeibs

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am fullstack blockchain developer and  I have experience in Javascript ,Typescript,React, Go, Rust.  This is my first contribution to the starknet ecosystem. So really i want to work on this issue.
How I plan on tackling this issue

Identify lint errors by running pnpm run lint.
Read the error messages.
Fix the code based on error messages.
Verify the fixed errors.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
hello @princeib please let me work on this issue

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am Om Santoshwar,
Final year btech UG at IIT Dhanbad,
i have a strong background in web development and blockchain development particularly in Ethereum and Starknet with 3 years of software development experience.
My Technical Skills-
Languages: Typescript, Javascript, Solidity, Rust, Cairo, C++
Frameworks and tools: Scaffold-eth/Stark, Nextjs, MERN, Ethersjs, Hardhat, Foundry, Openzeppelin contracts, Defi, AWS
Experience-
Participated in EthGlobal and other blockchain hackathons
Internships as Blockchain and Fullstack web developer
How I plan on tackling this issue
these lint issue are mainly due to assignment of a variable but not using it,
i will remove all such and check for logs for any other CI workflow checks or errors

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
hey @princeib can i take on this issue
How I plan on tackling this issue
Fix Linting Errors:
Resolve all errors identified when running pnpm run lint.
Verify CI Workflow:
Ensure that the Client CI workflow completes successfully after fixes.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I'm a Web and Systems Software Engineer, with extensive experience in writing softwares with performance and memory safety guarantess using systems programming languages such as Rust, GoLang; and TypeScript. I have experience working with linters such as clippy and writing idiomatic programs.
How I plan on tackling this issue

I'd ensure I go through every errors reported by the linter one at a time, and testing every fix to ensure I don't break the software, introduce bugs.
Assert the client CI workflow runs successfully.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am a Full Stack Developer with extensive experience in blockchain development, specializing in Next.js, TypeScript, Node.js, and Rust. With over 18 contributions across projects in the OnlyDust ecosystem, I’ve developed a strong proficiency in delivering high-quality solutions and tackling complex issues under tight deadlines. My experience spans frontend, backend, smart contract development, and a deep understanding of optimizing and maintaining scalable codebases.
How I plan on tackling this issue
I’d start by running the command pnpm run lint to identify all the linting errors in the client code. After reviewing the output, I would proceed to fix each of the errors one by one to ensure the code adheres to the established linting rules. Once all the errors are resolved, I would verify that the Client CI workflow runs successfully to ensure everything is functioning as expected.
I expect this task to take about 1 day to complete. This includes time for addressing the linting errors and running the CI workflow to confirm that there are no further issues.


Update Ecto.Repo calls to work with Ecto 3.8

Hi there! Thanks for maintaining this great library.
While trying to use ExAudit with Ecto 3.8 I noticed that it wasn't working as intended so I had to do the changes I'm submitting as part of this PR.
Options are now a tuple with adapter metadata instead of just the repo options. I think it was first introduced here: https://github.com/elixir-ecto/ecto/commit/0cf1800056fb30a4fdef7277fe6d27cac8567770
Let me know if I should change it to do something else. Cheers!

@narrowtux Any progress getting this reviewed and merged? ex_audit isn't compatible with newer Ecto versions til this gets released.

@narrowtux Is this project still maintained?

@narrowtux Can you check this out when you get a chance? I would love to be able to use this library. 🙏

@narrowtux Any updates on this? Is this library still maintained?

Thanks, @narrowtux !


Training Time with 8 NVIDIA RTX 3090 GPUs

Hi Haoning,
I noticed that you utilized 8 NVIDIA RTX 3090 GPUs for training your model. Could you please share how much time was spent training the model with these resources?
Thank you for your time and assistance.

Since our model is built upon pre-trained Stable Diffusion, the training is actually quite fast.
Sometimes we only use 4 * 3090 with a larger number of gradient accumulation.
The first stage may only take half a day to adapt the self-attention layers.
The second stage needs to extract context features to train our context module, which will be a little bit slower.
But it should take about one day to train with a single previous frame as context, and maybe another half day to further fine-tune with more contexts.


Invalid classNames in current master branch (bcd2120)

Version
styled-components: master (bcd2120)
babel-plugin-styled-components: 1.3.0

Reproduction
Just run sandbox in current master branch
Steps to reproduce

Checkout to current master branch
Follow instructions in the CONTRIBUTING.md to bootstrap sandbox

Ignore react-live warnings, Button.example is a little bit broken right now, but this doesn't make a difference for the end result

Inspect Header, Title, Subtitle on the page. className generated by styled-components is an invalid character - number:

Inspect Code and Button component. They have the same className (this may be react-live issue, but I'm not sure)

To confirm that this wasn't an issue before, you can check out to 3.1.4 tag and run sandbox again
Expected Behavior
Generated classNames should be valid CSS class names and not repeating themselves
Actual Behavior
See n.3 and n.4 above
I think that this could be somehow connected to https://github.com/styled-components/styled-components/pull/1516 but I don't have enough knowledge about hashing algorithms to confirm this 😅
/cc @kitten

You need to update your version of the babel plugin.
On Wed, Feb 14, 2018 at 11:21 AM Sergey<EMAIL_ADDRESS>wrote:

Version
styled-components: master (bcd2120
https://github.com/styled-components/styled-components/commit/bcd212065f87b5b3a68cfdb158af504e46a4ceb8
)
babel-plugin-styled-components: 1.3.0
Reproduction
Just run sandbox in current master branch
Steps to reproduce

Checkout to current master branch
Follow instructions in the CONTRIBUTING.md to bootstrap sandbox

Ignore react-live warnings, Button.example is a little bit broken right
now, but this doesn't make a difference for the end result

Inspect Header, Title, Subtitle on the page. className generated by
styled-components is an invalid character - number:

[image: image]
https://user-images.githubusercontent.com/5036933/36214569-15b5d51e-11aa-11e8-844c-b3ede3aa0684.png

Inspect Code and Button component. They have the same className
(this may be react-live issue, but I'm not sure)

[image: image]
https://user-images.githubusercontent.com/5036933/36215015-2c15a0f4-11ab-11e8-81fe-4ca1346449e5.png
To confirm that this wasn't an issue before, you can check out to 3.1.4
tag and run sandbox again
Expected Behavior
Generated classNames should be valid CSS class names and not repeating
themselves
Actual Behavior
See n.3 and n.4 above
I think that this could be somehow connected to #1516
https://github.com/styled-components/styled-components/pull/1516 but I
don't have enough knowledge about hashing algorithms to confirm this 😅
/cc @kitten https://github.com/kitten
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/styled-components/styled-components/issues/1521, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAiy1jYVqvgnULIm1wDGSzr7vVeV8jo7ks5tUwfXgaJpZM4SFlTZ
.

@probablyup Actually that's not quite right
The bug was introduced lately and will be fixed by #1514

@kitten thanks for a quick update! I don't mind if you close the issue if you want because it is not in the latest stable release 😸

@gribnoysup I'd just like to keep this issue up top for anyone who's looking to build master right now :wink:


Hide previous notifications or update their content when updated?

After an issue is created and shown in the channel -  Ideally we would either keep the same "view" of the post once the status is modified OR remove the visual elements from the previous post once a new post with a more current view of the ticket is made.
One drawback with the current design (MM-17816) is that previous instances of the "view" in the ephemeral post stay visible and you can manipulate the drop-down. This seems like a broader issue with how plugins make ephemeral posts.
Originally posted by @DHaussermann in https://github.com/mattermost/mattermost-plugin-jira/pull/454#issuecomment-603855704

We could (should?) remove the post-action from the ephemeral message upon performing a selection.

Closing issues due to inactivity. This issue can be re-opened with more interest from our community.


[BUG] The coordinates of the panel cannot exclude the location of bar in x11

Checklist before submitting an issue

[X] I have searched through the existing closed and open issues for eww and made sure this is not a duplicate
[X] I have specifically verified that this bug is not a common user error
[X] I am providing as much relevant information as I am able to in this bug report (Minimal config to reproduce the issue for example, if applicable)

Description of the bug
But when I used waybar in hyprland, the y coordinate of the eww panel was relative to the y coordinate below the waybar, but in x11 it was relative to the entire monitor
Reproducing the issue
my eww config:

eww  version:
eww 0.4.0 a9a35c1804d72ef92e04ee71555bd9e5a08fa17e

dwm(x11):
https://github.com/elkowar/eww/assets/30348075/f557cdcf-1457-4be2-ae3d-ff4055ab758f

It could be because of the exclusive property in waybar.


⚠ Bofrost.fr has degraded performance

In 2d685de, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1149 ms

Resolved: Bofrost.fr performance has improved in d96d2c7 after 19 minutes.


AutoTokenzier.from_pretrains needs setting with trust_remote_code inside load_module_map

System Info
lorax main
Information

[X] Docker
[ ] The CLI directly

Tasks

[ ] An officially supported command
[ ] My own modifications

Reproduction

using a model type not registered in the Transformers
place the tokenizer config file and related files inside the adapter checkpoint folder
inference with adapter info pointed to this adapter folder
the tokenizer loading will go into the resolve_trust_remote_code logic inside the Transformers, where it will require user input to confirm if trust_remote_code is not set

Expected behavior
loading the tokenizer directly if it is existed inside adapter.

The fix is easy, will prepare a PR for review soon.

Thanks @thincal!


melonDS: 0.9.5-unstable-2024-09-18 -> 0.9.5-unstable-2024-09-29

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for melonDS is: Work in progress Nintendo DS emulator
meta.homepage for melonDS is: https://melonds.kuribo64.net/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.9.5-unstable-2024-09-29 in filename of file in /nix/store/x4xfbafp9nwhpkk13pzsg6nggy5qxqc6-melonDS-0.9.5-unstable-2024-09-29

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

melonDS

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/x4xfbafp9nwhpkk13pzsg6nggy5qxqc6-melonDS-0.9.5-unstable-2024-09-29 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A melonDS https://github.com/r-ryantm/nixpkgs/archive/5dad232a986458775fc3e03debc5e5781faf1d76.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/5dad232a986458775fc3e03debc5e5781faf1d76#melonDS

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/x4xfbafp9nwhpkk13pzsg6nggy5qxqc6-melonDS-0.9.5-unstable-2024-09-29
ls -la /nix/store/x4xfbafp9nwhpkk13pzsg6nggy5qxqc6-melonDS-0.9.5-unstable-2024-09-29/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

melonDS

Maintainer pings
cc @AndersonTorres @artemist @benley @SCOTT-HAMILTON for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

@NixOS/nixpkgs-merge-bot merge


Docs.MS CI Updates for Azure.Template

CI Update for release of Azure.Template

Docs Build status updates of commit 431927c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

bundlepackages/azure-dotnet-preview.csv
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Handle repos with no README.md

Great library! Found it very handy.
Currently breaks when the base repo has no README.md, or has an empty README.md
changing line 83 in frontend/lib/docs.js from
this.docVue.$destroy( true );

to
this.docVue && this.docVue.$destroy( true );

seems to fix it.
Not sure if you prefer checking with && or try/catch or a bigger if block so I'll not be submitting PR for this

I think an if statement to check would be the best readable option. Thanks man!

On Feb 23, 2015, at 8:14 PM, Chang Wang<EMAIL_ADDRESS>wrote:
Great library! Found it very handy.
Currently breaks when the base repo has no README.md, or has an empty README.md
changing line 83 in frontend/lib/docs.js from
this.docVue.$destroy( true );
to
this.docVue && this.docVue.$destroy( true );
seems to fix it.
Not sure if you prefer checking with && or try/catch or a bigger if block so I'll not be submitting PR for this
—
Reply to this email directly or view it on GitHub.


Gii: overriding default ActiveRecord methods

Hi.
We've run into scenario today that made Gii will override default ActiveRecord method (table attribute => getAttributes() has overriden default \yii\db\ActiveRecord::getAttributes() method), and Gii could not create CRUD because of strict standards that prevent from dwindling method signature. This, of course, is not a bug (Gii is working just as expected), but, i guess, Gii should prevent users whenever they are going to override a method they probably don' want to override.

I think @yii-bot should move this to yii2-gii and this seems like an easy fix.


Typescript2Fable - Function names

In typescript definition file there may exist functions with not valid F# name. For such functions name should be enclosed into double ticks.

Fix in #24


Add Support for Laravel, Leaf, Slim, Symfony & CodeIgniter PHP Frameworks

This will allow for the addition of a PHP + Laravel Example Application which is currently in development at https://github.com/andrewdmaclean/example-php-laravel

I have just transferred them @laurawarr

This PR now adds support (along with the relevant repositories) for the following PHP Frameworks

Leaf
Laravel
CodeIgniter
Slim
Symfony

@andrewdmaclean you'll also need to update the section at the bottom that specifies which port should be opened in the browser

I'm getting this error when running the php-laravel example

The php-codeigniter example also fails to load, it looks like the repo needs to be made public

The php-codeigniter example also fails to load, it looks like the repo needs to be made public

I am unable to change any settings about those repositories with my current permissions. It looks like either Emma or yourself will need to make those change.

@andrewdmaclean you'll also need to update the section at the bottom that specifies which port should be opened in the browser

Are you referring specifically to the Laravel example app? php artisan serve automatically serves on port 8000

@andrewdmaclean you'll also need to update the section at the bottom that specifies which port should be opened in the browser

Are you referring specifically to the Laravel example app? php artisan serve automatically serves on port 8000

At the bottom of the script you need to specify which port should be opened in the browser (it seems like most of these use 8000). By default the browser won't be opened, since some of the client apps do this automatically

@laurawarr made that change at the bottom of the script!


Fix OS detection and download OS-native archive extension

Switch from os.type() to os.platform()
Download tar.gz archives on non-Windows platforms

Fixes #111
Fixes #119

@OliverMKing , @davidgamero
pls, review

@bfoley13 , maybe you can review?

thx for this fix, when do you think this can be merged and released?

releasing in #134


Performance improvements in SDWebImage

Set maxBufferSize to 1MB to improve GIF loading
Add SDWebImageScaleDownLargeImages by default

I think this change is neccessary. Why did you close?

hi @ngochiencse, I did these specific changes for a project I was working on that is now deprecated. I agree, a similar change is necessary (not sure if something like this was added since 2019, haven't checked the repo in a while) but it would need to be configurable, I would also check is something similar could be done for Android, etc. I might work on this again in the future, but not for now. If you need these specific changes in your project you can always apply them using patch-package (which I didn't know about back then).


Remove code under "Up and Down methods"

From the code listed above, I see:
.Annotation("SqlServer:ValueGenerationStrategy", SqlServerValueGenerationStrategy.IdentityColumn),
When I follow this tutorial using Microsoft Visual Studio Community 2019 Version 16.4.4, I get:
.Annotation("SqlServer:Identity", "1, 1"),
I am assuming the former line of code means the same thing to SQL Server as the latter, which I'm more familiar seeing, but I'm just not as sure in Visual Studio, which is the reason I'm working through the tutorial.

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

ID: 145343de-9267-9171-b6c9-718703b7544d
Version Independent ID: 2c2f791f-d41c-f995-a941-2461151a7db4
Content: Razor Pages with EF Core in ASP.NET Core - Migrations - 4 of 8
Content Source: aspnetcore/data/ef-rp/migrations.md
Product: aspnet-core
Technology: aspnetcore-data
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

The scaffolder changes over time, so we shouldn't be showing code. Change this to examine the up and down methods.

This will be fixed in the next update.


Candle's pickle library does not currently function on Windows due to Candle bug

Describe the bug
When using PyTorchFileRecorder on Windows, it throws an error. This is caused by https://github.com/huggingface/candle/issues/1454 bug.
To Reproduce

Uncomment these lines in pytorch-import example
Build and run pytorch-import example.

Expected behavior
Build should not break on windows.
NOTE: After the fix, the following should be enabled:

[x] - these lines in pytorch-import example
[x] - pytorch-tests in burn-import

This should be fixed now via #1382


What's the intent of the "cc-brand" class?

In the sample project, there's a "cc-brand" class
[]
What's the purpose of it? I was hoping it would show the appropriate image based on the card type - but it doesn't and I was wondering it's intent.. Please let me know.

I updated the demo project, and now it shows cc schema in this field.
Also there is a feature request to extend ccDirective and allow retrieving parsed ccType from it https://github.com/nogorilla/angular-cc-library/issues/45


suggestions are messed up

I noticed this problem some days ago, before that it worked well. Say I have a variable call "distance". If I type the beginning of it, "di", Tabnine suggests "distance". If I hit Enter on it, the result becomes "didistance", so I need to jump back and correct it manually.

Sorry about that, I'll try to get this fixed ASAP. What version of VS Code and what OS are you running?

It doesn't happen all the time though, just rarely. Now I tried again and couldn't reproduce it in 5 minutes. It's a mysterious thing.
VSCode: 1.29.1, x64
OS: Manjaro Linux

Darn. The completion mechanism was changed around a week ago, so that probably caused it. But the changes were necessary to support bracket pairing (where if the suggestion contains a ( then a ) is added after the cursor).
Let me know if you notice a pattern in when this occurs.

Thanks for the quick reply. Yes, it appeared around a week ago. I will keep an eye on it and let you know.

I can't recognize a pattern but I caught a case on video: https://www.dropbox.com/s/wvpeso1cnj0573c/tabnine.mp4?dl=0 . Here, "parseInt" is inserted by Tabnine as "pparseInt" after an Enter.

Thanks. I was able to reproduce the bug by typing 2 characters at the same time and then pressing Tab. (The delay before pressing Tab doesn't matter, only the delay between the characters.) I'm working on a fix.

This should be fixed in 1.0.4. Thanks for the report, and let me know if it's not.

Thanks for the fix. I've tested it for a few days and this problem hasn't come back.

Tabnine looks great, but can we look at re-opening this issue. I am having the same problem using version 1.1.0 of tabnine (on the nightly insiders version of VS code)
Typing

After tab or enter


signalstyle seems to have broken in 0.39.0

In 0.36.0 SignalStyle wanted you to use 'fail' for exceptions and 'raise' for re-throwing.
In 0.39.0 it complains about 'fail' saying "Always use raise to signal exceptions."
I tried to set Style/SIgnalStyle to 'semantic' in my config, but was told it was an unrecognized cop.
Expected behavior
fail is the preferred way to signal exception.
Actual behavior
raise is the preferred way to signal exception.
Steps to reproduce the problem
Use 'fail', run rubocop 0.39.0.
RuboCop version
Include the output of rubocop -V:
$ bundle exec rubocop -V
0.39.0 (using Parser <IP_ADDRESS>, running on ruby 2.0.0 x86_64-linux)

The cop's name is Style/SignalException. The default was changed a few versions ago to reflect a change we've made to the Ruby style guide.


[DOC] Fixing groupby_topk.py doctest whitespace normalization.

Fixes stuff leftover from #1077.

🚀 Deployed on https://deploy-preview-1095--pyjanitor.netlify.app


add oidc identity provider to eks

What problem are you facing?
Currently the only way to login to an eks cluster which was provisioned by provider-aws is via IAM user.
Recently AWS added the feature to login to an eks cluster via oidc, but it's not yet supported by provider-aws
How could Crossplane help solve your problem?
The eks resource in provider-aws should be updated with the oidc configuration options<EMAIL_ADDRESS>Depends on https://github.com/crossplane/provider-aws/issues/383

Yeah that makes sense. I believe you can generate the resource with codegen, as @MisterMX did it in #863

for CodeGenerator we need first https://github.com/crossplane/provider-aws/pull/801 because  OIDC identity Provider calls are available since 1.37.10 ... ..
https://github.com/aws-controllers-k8s/community/issues/883


Vision updates

Closes #58

@nickfrisch I see the build failed on this one.  Please update and then I'll review it.  Thanks


Remove dead code and fix warnings in the http2 module

Motivation:
Opportunities for clean up found while working on a different PR.
Modification:

Dead code has been removed.
Unnecessary parenthesis, qualifiers, etc. removed.
Unused imports removed.
Override annotations added where missing.

Result:
Cleaner code

@normanmaurer Comments addressed

Ship it


Allow Target-based actions to stay selected when on cooldown or misclicking

Asked for by @Zumorica , we should add flags to the action prototypes that allows the action to remain selected even when it goes on cooldown or you click something that isn't an entity.
IMO, the default should be changed as well to reflect the most common use cases:

target point/entity actions - default to remain selected when on cooldown
target entity actions - default to remain selected when you don't click an entity (you basically never want to deselect the action if you are trying to click a moving target but you "missed")

The above defaults can be overridden per-action if needed.

fyi @Zumorica , working on this now

fyi @Zumorica , working on this now

ah nvm, I see there's already a PR for this

ah nvm, I see there's already a PR for this


Add synchronized to getInstance method

Without the synchronized keyword, I feel the statement :

always use DatabaseHelper.getInstance(context), as it guarantees that only one database helper will exist across the entire application's lifecycle"

is false or at least misleading, due to thread safety concerns.
I'm a bit new to the "singleton pattern" as my major was physics not computer science, and after reading in the API documentation that There is normally no need to subclass Application. In most situation, static singletons can provide the same functionality in a more modular way., I've been trying to move a bunch of code out of Application and into singletons.
One of the objects has a built-in SQLiteDatabase, so having a single instance across all threads is a big issue (it's a port of a python library to java, so for maintainability we can't really wrap the db itself in a ContentProvider), and I was having trouble finding a kind of "standard" way of implementing the Singleton pattern on Android, recommended by Google. I almost used your pattern here, which another project member mentioned isn't a very good singleton pattern.
e.g. I've since found the following, written by Dianne Hackborn:

This is my preferred approach for implementing a singleton that needs a Context:

static final Object sLock = new Object();
static MySingleton sInstance;

static MySingleton getInstance(Application app) {
    synchronized (sLock) {
        if (sInstance == null) {
            sInstance = new MySingleton(app);
        }
        return sInstance;
    }
}

Since your blog is called Android design patterns, and you refer to this as the singleton pattern, it would be good if you could use a more standard thread safe one (e.g. see the above link, or here). Or even better, write a whole post about the singleton pattern, as this is a pretty interesting issue with most of the Android specific information scattered around various unofficial places.

OK, your argument convinced me enough. :)
I'll merge your pull request... thanks for the suggestion!


pull request for e2e test at 01/07/2017 12:45:11

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


New config value added, not documented

A new field was added cache.path which is not documented and does not have a default value in application.yaml, causing failed startups when running off the latest master.

Thank you! #187 merged.


🐛 [flutter_ui] SignInScreen not usable through integration tests

Bug report
Describe the bug
When writing integration tests, I need to go through the AuthGate, but I can't target the EmailInput field or PasswordInput field.
Making it impossible to test, and then to use !
Expected behavior
I expect both EmailInput and PasswordInput to have keys.

I have a quickfix where I put keys on a fork, but could be better if we get keys to use

@fodil-a
By I need to go through the AuthGate, do you mean the native dialog box that asks you to enter your email and password ?
That seems to be coming from native and not Flutter and when you are using integation_test, I think it still doesn't interact with native UI elements.
See this similar issue: https://github.com/flutter/flutter/issues/86295 and you may need to track it in this issue because it's not flutterfire_ui issue but underlying integration_test package's current limitation.

I try to use the 'SignInScreen', which is a flutter widget from your UI library (not native), I forked the project, added 2 keys, and now my integration tests work.

This one https://github.com/FirebaseExtended/flutterfire/blob/master/packages/flutterfire_ui/lib/src/auth/screens/sign_in_screen.dart

I see. Thanks for the details.

/cc @lesnitsky

Yes please keys so we can more easily integration test 👍

Adding a whole bunch of properties just to pass keys down. the widget tree would be very cumbersome and pollute constructor arguments. Instead you can used find.byType()


brew extract produces unusable target names from already-versioned names

Please note we will close your issue without comment if you delete, do not read or do not fill out the issue checklist below and provide ALL the requested information. If you repeatedly fail to use the issue template, we will block you from ever submitting issues to Homebrew again.

[x] ran brew update and can still reproduce the problem?
[x] ran brew doctor, fixed all issues and can still reproduce the problem?
[x] ran brew config and brew doctor and included their output with your issue?

What you were trying to do (and why)
Extract the defunct python@2 formula into a new tap, as a test for my answer to a related question on Discourse.
What happened (include command output)
I created a new tap, then extracted the python@2 formula to it.
$ brew tap-new gromgit/python2
==> Created gromgit/python2
/usr/local/Homebrew/Library/Taps/gromgit/homebrew-python2

$ brew extract python@2 gromgit/python2
==> Searching repository history
==> Writing formula for python@2 from revision 86a44a0 to /usr/local/Homebrew/Library/Taps/gromgit/homebrew-python2/Formula/python<EMAIL_ADDRESS>
Now, python<EMAIL_ADDRESS>is a rather bizarre formula name, and it turns out even Homebrew itself chokes on it.
$ brew search python@2
==> Formulae
gromgit/python2/python<EMAIL_ADDRESS>
$ brew info gromgit/python2/python@2
Error: No available formula with the name "gromgit/python2/python@2"
==> Searching for a previously deleted formula (in the last month)...
Error: No previously deleted formula found.

What's worse, the actual formula generated seems to be invalid.
$ brew info gromgit/python2/python<EMAIL_ADDRESS>Error: gromgit/python2/python<EMAIL_ADDRESS>/usr/local/Homebrew/Library/Taps/gromgit/homebrew-python2/Formula/python@2@2.7.17.rb:1: `@2' is not allowed as an instance variable name
/usr/local/Homebrew/Library/Taps/gromgit/homebrew-python2/Formula/python@2@2.7.17.rb:1: syntax error, unexpected end-of-input
class PythonAT2@2717 < Formula
               ^

What you expected to happen
I expected brew extract to create a valid formula file that's usable as either gromgit/python2/python@2 or<EMAIL_ADDRESS>Step-by-step reproduction instructions (by running brew commands)
See What happened section above.
Output of brew config and brew doctor commands

$ brew config
HOMEBREW_VERSION: 2.2.6-18-g5b126ec
ORIGIN: https://github.com/Homebrew/brew.git
HEAD: 5b126ec850b688cba57a9cf17be08d321ad4d10f
Last commit: 23 hours ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 0492536b0c6b60a57463a7d82380e8dc156d09f2
Core tap last commit: 15 hours ago
HOMEBREW_PREFIX: /usr/local
HOMEBREW_DEV_CMD_RUN: 1
HOMEBREW_NO_ANALYTICS_THIS_RUN: 1
HOMEBREW_NO_AUTO_UPDATE: yes
CPU: quad-core 64-bit haswell
Homebrew Ruby: 2.6.3 => /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby
Clang: 11.0 build 1100
Git: 2.25.0 => /usr/local/bin/git
Curl: 7.54.0 => /usr/bin/curl
macOS: 10.14.6-x86_64
CLT: <IP_ADDRESS>.1.1576735732
Xcode: 11.3.1
XQuartz: 2.7.11 => /opt/X11

$ brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: Putting non-prefixed coreutils in your path can cause gmp builds to fail.

Warning: Unbrewed header files were found in /usr/local/include.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected header files:
  /usr/local/include/libpgtcl.h

Warning: You have unlinked kegs in your Cellar.
Leaving kegs unlinked can lead to build-trouble and cause brews that depend on
those kegs to fail to run properly once built. Run `brew link` on these:
  fuse4x
  moreutils
  scheme48
  cvs

Fixed by https://github.com/Homebrew/brew/pull/7066, thanks @alebcay!


Only write good span timestamp guesses at ingest

Previously, Zipkin wrote the wrong timestamp when receiving spans that
are missing timestamp data. It is still the case that instrumentation
libraries aren't updated to add this. Until then, we have to guess a
little more smartly so as to not record incorrect timestamps.
This does the following when Span.timestamp is missing:

If there is a "cs", use that (because client always is authoritative)
If there is an "sr" in a root span, use that
Otherwise, return null instead of choosing an arbitrary low value.

This also is more careful when updating timestamps, for example, in
MySQL, we only update if the span's timestamp is set.
This change has some impact, notably that duration queries now require
instrumentation to update to actually set Span.duration. Also,
elasticsearch "timestamp_millis" field is now used directly for queries.
To facilitate better instrumentation, I've added more documentation:
https://github.com/openzipkin/openzipkin.github.io/pull/46
Fixes #1281

If there is a "cs", use that (because client always is authoritative)

Does this mean that if client sends a request at t0, and the server starts receiving at t100, then the span will be rendered from t0?

yep
On Fri, Sep 9, 2016 at 7:37 PM, Roger Johansson<EMAIL_ADDRESS>wrote:

If there is a "cs", use that (because client always is authoritative)
Does this mean that if client sends a request at t0, and the server starts
receiving at t100, then the span will be rendered from t0?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/openzipkin/zipkin/pull/1282#issuecomment-245889615,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAD61-r4eR_oyQBBm6FQtIaKvburwHqTks5qoUTcgaJpZM4J48Jf
.

one broken test.. looking into it.

ok I think I got the fix now.

alright I'll plan on merging this and cutting a release tomorrow morning my time (+~12hrs) unless someone says don't.


Okx exchange GET trade fills

Describe the bug
I was running a xemm strategy with 2 trading pairs on okx exchange and noticed order fills not being updated. When my maker trades got filled, it was not being updated in the order tracker and hence no taker orders being submitted. This led to an accumulation of maker trades without any hedging on the taker side. Which led to a skew in my inventory and failure of strategy execution.
Upon investigating the logs, I realised that the UserStream websocket was disconnected multiple times occasionally and API request to update order status constantly failed. I was only able to discover the error when adding logging statements to ExchangePyBase._api_request in connector/exchange_py_base.py. Here are the technical issues:
Issues:

When okx exchange object calls _request_order_fills to GET api/v5/trade/fills, it is constantly receiving a 401 response Error: {"msg":"Invalid Sign","code":"50113"}

When ExchangePyBase._api_request() fails even after 2 retries, no error message is found in logs

Steps To Reproduce

Go to connector/exchange_py_base.py (here) and add 2 logging statements for both successful and failed api requests (see screenshot)
Start the bot and run a strategy using okx exchange (I used cross exchange market making)
Let the strategy run for a while
Check the logs by grep -RI 'trade/fills' <logfile>, this shows that all calls to api/v5/trade/fills fails

Screenshots
Log statements:

Error logs:

Release version
v1.8.0
Optional: your discord username:
huatahhhh#5633

Hi @huatahhhhh Could you please tell your machinetype (AWS/local) OS and installation type (Source/Docker)?
Could you please also send your config and log files? it could help a lot to triage the issue.
I tried to reproduce using AVAX-USDT Pair, but can't reproduce the issue

@nikspz Do follow the steps to reproduce and add the logging statements in the code.

@nikspz API calls for api/v5/trade/fills is crafting the digital signature wrongly. This leads to hummingbot order tracker not capturing trade fills when web socket is disconnected as well as triggering the throttle limit (when a api call fails, hummingbot will reattempt synchronising of clock).
Please follow my above steps - adding logging lines to source code to verify the issue. I would like apply to fix this and potentially get the bounty :)

Severity: P3
Bounty: 10000 (https://hummingbot.org/maintenance/bugs/)
Rationale:  Bug related to OKX, certified connector

Assigning this issue to @huatahhhhh . Thank you for your contribution!

thank you @nikspz

@JeremyKono The PR is not for this issue. I will be submitting a PR for this soon

@JeremyKono  please unlink this issue from PR #5828

Hi @huatahhhhh do you have any updates on this issue?

@JeremyKono I have submitted a PR for this issue #5900 . Awaiting for someone on the team to review the code

Issue was fixed in #5900
@huatahhhhh please fill up & submit the AML Policy Form via this link: https://forms.gle/ZeSRvWUU3gBeHPbH6
This is a one-time process for each ETH Address used to receive HBOT bounty.

Closing this bounty as paid


PR: Refuse to import on Windows 7

Fixes #59.
Workaround for https://github.com/spyder-ide/pywinpty/issues/59 since we can't pin down the source of the problem on Windows 7.  This prevents other libraries (like the Jupyter notebook) from attempting to use this library only to later find that it does not work.

It seems we need to skip the import error in Appveyor for our tests to run.

Double-checking the version number that we get there.

Okay, it seems we might need to rethink this strategy if we were already successfully using this library on Windows 7 on Appveyor.

I'll make a simple example with named pipes that will hopefully trigger the access error and we can do that at startup instead.

I'll make a simple example with named pipes that will hopefully trigger the access error and we can do that at startup instead.

Ok, that sounds better. Thanks!

Closing in favor of #90.


Unable to run dev script with static target and modern client

Version
v2.13.0
Reproduction link
https://github.com/hannes-k/nuxt-modern
Steps to reproduce
Create new nuxt project
add target: 'static' and modern: 'client' to nuxt.config.js
npm run dev
ctrl + c
npm run dev
What is expected ?
Developer mode should be started.
What is actually happening?
 ERROR  Cannot read property 'filter' of undefined                                                                                14:27:24

  at node_modules/@nuxt/webpack/dist/webpack.js:176:12
  at runMicrotasks (<anonymous>)
  at processTicksAndRejections (internal/process/task_queues.js:97:5)

Additional comments?
The error does not always occur. Sometimes it works, but the next time it does not.

This bug report is available on Nuxt community (#c10805)

I have same problem in SSR mode.

I'm getting the same error here since Nuxt 2.13. Also, navigation from page to page is not working anymore. When I click a nuxt-link, the whole page reloads instead of just updating the content.

We have discussed this here also:
https://cmty.app/nuxt/nuxt.js/issues/c10826#comment-5ef328c011200fb6dea89a4b

On my build the issue is modern browsers can't open the build but legacy one can.
I suppose modern build is failing.
I observe this issue on yarn dev but not on yarn build && yarn export (for production).
So I am cheating a little and setting modern: process.env.NODE_ENV === 'production' in nuxt.config.js

fwiw this has impacted us as well. we don't have target: static defined in our nuxt.config.js, just modern: client (per initial description)
2.13.1 +2.13.2, same Cannot read property 'filter' of undefined webpackish looking error. build fails
2.13.3, build succeeds but render pinwheels in browser
so this is half-fixed in our use case. 😕

@kreig303 Can you please provide us more details about your problem? It would be great if you can create a minimal reproducible repo as well.


nixos/nginx: allow recommended proxy settings to be enabled per location

Description of changes
This allows the recommended proxy settings to be enabled on a per-location basis, in cases where you'd want to enable them for only some locations, or disable them for some problematic locations.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/909

Idea sounds good to me but I can't comment to much on the design.

@ofborg test nginx

Seems like a flaky test since it succeeded on aarch64-linux :/
@aanderese Since you approved the changes, do you mind merging, or do you want someone else to review them first? Thanks!

Thanks everyone! Should we be concerned about flakey test, though?


Fixing https://github.com/beautify-web/js-beautify/issues/1658

Fixing https://github.com/beautify-web/js-beautify/issues/1658
First we need to verify whether there is another input before matching its value.

@asteinha
Excellent, thanks.  Can you add a test for this?

Done.

@asteinha Please modify the data file test/data/javascript/tests.js and run the build to generate the tests.

Done


Powershell script for configuring ML services on SQL

The script allows configuring ML services on SQL Server
Assumption is that SQL server is already installed with ML services.
You should copy this script on the SQL server machine and run it in admin mode.
This script does the following
1. Enable external script execution on SQL Server
2. Restart SQL server and related services
3. Ensure that launchpad service is running and it set to automatic mode
4. Tries to create login for SQLRUserGroup if not present already.

Thanks.
From: Sheri Gilley<EMAIL_ADDRESS>Sent: Thursday, April 12, 2018 10:38 AM
To: Microsoft/SQL-Server-R-Services-Samples<EMAIL_ADDRESS>Cc: Jitendra Kulshreshtha<EMAIL_ADDRESS>State change<EMAIL_ADDRESS>Subject: Re: [Microsoft/SQL-Server-R-Services-Samples] Powershell script for configuring ML services on SQL (#29)
Merged #29https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2FSQL-Server-R-Services-Samples%2Fpull%2F29&data=02|01|jitenk%40microsoft.com|7885720db91445bcf54e08d5a09c222c|72f988bf86f141af91ab2d7cd011db47|1|0|636591514812145680&sdata=OF%2Flywl6liZ7%2FMlMsjfxEIIWoSiC1B4GXkQUuqhILMI%3D&reserved=0.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2FSQL-Server-R-Services-Samples%2Fpull%2F29%23event-1571570889&data=02|01|jitenk%40microsoft.com|7885720db91445bcf54e08d5a09c222c|72f988bf86f141af91ab2d7cd011db47|1|0|636591514812145680&sdata=a5uaoRx4UrGmaTIsEbkAQ%2By%2F8YZtft7zYN0vom09ldE%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAZYHdwvo6H2_VDC30qHRAkb8dwbmv3ITks5tn5D2gaJpZM4TKngQ&data=02|01|jitenk%40microsoft.com|7885720db91445bcf54e08d5a09c222c|72f988bf86f141af91ab2d7cd011db47|1|0|636591514812145680&sdata=wr%2FEg8TACrVoHJW%2BHafF3n2Q6aUjt4Rs47uUIdGEyTU%3D&reserved=0.


Example usage with SolidJS (jsx)

Do you have an idea on how to use it with SolidJS (jsx)?

Could you provide more information on your project? Are you trying to set up SSR? SolidJS is a frontend tool and dynohot is a backend tool. We personally do use dynohot to implement hot reloading of an SSR React project but I suspect this isn't what you're trying to do.

Sure. Yes, for static site generation (SolidJS is only used for static site generation). I am reimplementing refo (A static site and resume example with styled components.) using dynohot and a (Node.js) loader (that I am writing) (instead of using Astro).
I was able to import a (Node.js) module (which is handled by dynohot) from the loader that I am writing, but I was unable to set it up in a way that I am getting an up to date module when importing from my loader. Is this somehow possible?
What I currently have and is working so far is the following:
In my loader modules ending with .html.js are handled.
Their result is written into a .html file (in a static folder) with the same name and path as the handled module.
I am transforming the code of modules ending with .html.js using Babel like this:
import {transformFileSync} from '@babel/core'

const {code} = transformFileSync(/*path*/, {
	presets: [
		['solid', {generate: 'ssr'}]
	]
})

I am evaluating the transformed codde and writing it's result (into a .html file (in the static folder)) like this:
import {renderToString} from 'solid-js/web'

import {writeFileSync} from 'fs'

const module = new SourceTextModule(code) // source: https://stackoverflow.com/questions/72130595/how-to-link-the-imported-dependencies-of-module-created-by-vm-sourcetextmodule-t/73282303#73282303

await module.link(async identifier => {
	const module = await import(identifier)
		var imported = new SyntheticModule(
		Object.keys(module)
		, () =>
			Object.entries(module).forEach(
				([key, value]) =>
					imported.setExport(key, value)
			)
		, {identifier}
	)
		return imported
})

await module.evaluate()

writeFileSync(
	//target // '.html'
	, renderToString(() => module.namespace.default)
)

Would be nice if I could just import the transformed module (Which I can and it works, but I couldn't get hot module reloading working for this case like this. So the imported module is always outdated here in this case.) like this:
writeFileSync(
	//target // '.html'
	, renderToString(() => (await import(/*path*/)).default)
)

Is there a way I can use the dynohot loader for the loader I am writing as well? (Currently I am only able to use it for the main code that are handled by the loaders.)

My first guess is that your resolve hook is resolving to the html file, and therefore dynohot doesn't know what to watch.
I actually just open sourced our TypeScript loader which is a good place to get started: https://github.com/braidnetworks/loaderkit/blob/main/packages/ts/loader.ts
The key takeaway is that resolve should always return url as the source file (in your case .html.js) and not something else. url is the file which dynohot will watch for changes. In the load hook you can set responseURL to whatever you want, it doesn't exist or even be unique.
That's kind of a shot in the dark without more information. I can also take a look at the project if you want to host it somewhere. It sounds like a cool use case.

No. My resolve hook just calls and returns nextResolve(specifier, context) and in my load hook I return the transformed source (of the .html.js module). Writing (generating) the .html file (in the static directory) is just a side effect of importing a .html.js module. Example: import 'index.html.js'
So this part is working and dynohot watches it properly I think.
I am not sure if I need to set responseURL. Currently I am not setting it.

Yes, I am planning to update the refo project once I finished the reimplementation and share it with you here. So far overall dynohot seems to work really well.

So basically what I would like to do I think is to use dynohot for my loader as well. So do something like this if somehow possible:
node --loader $(node --loader dynohot ./myLoader.js) --loader dynohot index

Currently I have this:
node --loader ./myLoader.js --loader dynohot index

So I would like dynohot to watch my loader as well if somehow possible.

That way instead of the evaluation script I could just import the module as usual in my loader as well.

This also means that right now if I make a change in my loader then my loader is not hot reloaded. So it would be nice to somehow have hot module reloading for my loader as well.

Do you have an idea how to do that?

I don't think it will be possible to hot reload another loader. It would invalidate the entire module graph which would be more expensive than simply restarting nodejs.

I see. So I guess I can't import a (hot reloadable) module from the loader itself in a way that I get the up to date module (I can import the module, but it is always the version when I started the project and not the up to date one.).

An update to a loader would invalidate the entire module graph since all modules implicitly have a dependency on the loader chain. Loaders should, in general, be pretty lightweight and stable. Once you get yours working you shouldn't need to be modifying the loader all that much right? Just transform the incoming source and pass it along. For reference the actual loader part of dynohot only includes the source transformation, and is entirely stateless.

Yes. I also thought that it works like you describe.
Thank you for the help!
Now I had the idea to just add the code that writes the file into the source code of the module that I am handling with the loader where I can just import the module itself and write it's result into the file. So I don't need the previously shared evaluation script that relies on the experimental-vm-modules feature.
This seems to also work well and I can just use a normal import.
I am planning to share a minor issue here or maybe in a new one.

Actually this is even better. Unlike the module evaluation solution this covers an edge case as well by design.

Do you know any raw (Node.js) loader? (Similar to for example this one: https://vitejs.dev/guide/assets.html#importing-asset-as-string)

I don't know of a raw loader. The ecosystem is still very new so there's a lot of territory that's open for staking. If you build this I would recommend a new URL scheme instead of a query param like Vite. import file from "content:./module"
I'd also recommend not performing the file write operations in your development tool and have a separate "production" build step.

As far as I know Vite supports a query parameter (https://vitejs.dev/guide/assets.html#importing-asset-as-string) only. So you mean you recommend a new URL scheme (instead of a query parameter (like Vite supports)).
The way I implemented it right now is that the write operations are performed by the (imported) modules themselves (my loader adds the writing script into their source codes).
I think there should be no difference. The only main difference is that when I am developing I keep the process running using setInterval(() => {}, 2 ** 31 - 1).
So there is only the script that generates a static site and if I keep this script's process running then as I make changes to the imported modules they are writing their output into the static folder and also removing their output if they are no longer imported.


Add page audit log

Closes #19.

@tmaybe mind reviewing and merging when the tests pass?

@migurski looks good to me!


feat: automate releases and changelogs

@mrlubos  would you up to adding https://github.com/changesets/changesets to the project? They are a great tool for managing changesets and releases. Provided we add a NPM token to the repositories secrets.
I think it would be good to get back to updating the changelog (I can backtrack the current releases not included in it).
I can also setup changesets in the repository and CI if you would like.
Let me know your thoughts and I can implement this (or assign it to me). Also if possible could you add a NPM_TOKEN secret for use in actions (so that the release portion will work)

This is on my radar, as well as adding semantic versioning. I didn't want to do it just yet to avoid diverging too much from the original repository. Besides, I think there'd be too many breaking changes initially with some of the features I want to add, so it might make sense to just release it as v2 or a separate project when we get around to adding this.

This is on my radar, as well as adding semantic versioning. I didn't want to do it just yet to avoid diverging too much from the original repository. Besides, I think there'd be too many breaking changes initially with some of the features I want to add, so it might make sense to just release it as v2 or a separate project when we get around to adding this.

Ya, the version is still < 1 so we could continue to have breaking changes in minor version until 1.0.0 is released

Oh yeah sorry, meant v1. I suspect that despite this project being pre-v1, many people might be already depending on it, and making sweeping changes might not be easy to migrate, hence the hesitation on my part


why use arguments object?

Note: for support questions, please use one of these channels: Chat: AngularClass.slack or Twitter: @AngularClass

I'm submitting a ...
question about the decisions made in the repository

Do you want to request a feature or report a bug?
Requesting to raise a pull request.
It may be a minor patch; but wanted to confirm before doing so.

The following line uses arguments object rather than using args variable passed to the respective function root. Is there a specific reason for doing so, or is this redundant?
https://github.com/AngularClass/angular2-webpack-starter/blob/master/config/helpers.js#L18
function root(args) {
  args = Array.prototype.slice.call(arguments, 0);
  return path.join.apply(path, [ROOT].concat(args));
}

P.S. Thanks for building this starter project!

I believe the reason was to facilitate compatibility with older versions of NodeJS, this matters because it isn't being transpiled by TypeScript.
That said, the code style is abysmal. Assigning to a parameter is a terrible practice and also completely unnecessary.

It works, but not good coding. If somebody can re-write this in a better way that works with Node 5 then go for it!


ephemeral-disk-utils: add few harmless tests and rename RemoveFile

Introduce a few tests to document RemoveFile and FileExists; simplify RemoveFile and rename it.
Signed-off-by: Dan Kenigsberg<EMAIL_ADDRESS>NONE

@dankenigsberg I think you can push the err = os.Remove(path) into the if statement, If you think it will be less clear that's fine as well.
/lgtm

@dankenigsberg I think you can push the err = os.Remove(path) into the if statement, If you think it will be less clear that's fine as well.
/lgtm

I think you can push the err = os.Remove(path) into the if statement, If you think it will be less clear that's fine as well.

Thanks. I know it's idiomatic, but to my untrained eyes it is less clear
   if err = os.Remove(path); err != nil && !os.IsNotExist(err) {

I think you can push the err = os.Remove(path) into the if statement, If you think it will be less clear that's fine as well.

Thanks. I know it's idiomatic, but to my untrained eyes it is less clear
   if err = os.Remove(path); err != nil && !os.IsNotExist(err) {

A single test failed
[Fail] [rfe_id:609]VMIheadless [rfe_id:609]Creating a VirtualMachineInstance with headless [It] [test_id:713]should have more memory on pod when headless

in this run, but it passed locally.


More info needed for Tooltip - "Submit for Review"

Comment/concern from one of our researchers:
They did not know who was reviewing the DMP. At 1st they thought the funder?

Suggestion to change the wording on the tooltip:
Submit your plan for an informal review from your institution.

This appears to have been a tool tip that was on the DMP Preview page.  However there is no longer a tool tip here.  So not sure if this is still an issue.

tooltip exists on DMP Preview page. other open issues pertain to customizing auto-generated emails to notify researchers about who is conducting reviews and when to expect a response #139 #159


Backend time availability

New features:

Added column to attendees table for time segment availability
Time segments is a JSON in the form of: {
"Aug 10": [],
"Aug 11": [
{
"beginning": "09:00",
"end": "10:00",
"type": "Preferred"
},
{
"beginning": "11:00",
"end": "12:00",
"type": "Regular"
}
],
"Aug 12": [],
"Aug 15": []
}
Can store by either days of the week or specific days
Can retrieve data to get a user and their associated time segments for a given event

Please run prettier :)
Also, for API's to work off of CloudFlare, we need to have them as edge functions.  You can't see the logs in cloudflare unfortunately but here's the relevant lines:

10:32:20.932
⚡ ERROR: Failed to produce a Cloudflare Pages build from the project.

10:32:20.932
⚡

10:32:20.933
⚡ 	The following routes were not configured to run with the Edge Runtime:

10:32:20.933
⚡ 	  - /api/attendees/create

10:32:20.933
⚡ 	  - /api/attendees

10:32:20.934
⚡

10:32:20.934
⚡ 	Please make sure that all your non-static routes export the following edge runtime route segment config:

10:32:20.934
⚡ 	  export const runtime = 'edge';

10:32:20.934
⚡

10:32:20.934
⚡ 	You can read more about the Edge Runtime on the Next.js documentation:

10:32:20.935
⚡ 	  https://nextjs.org/docs/app/building-your-application/rendering/edge-and-nodejs-runtimes

The fix is as simple as adding that export in the two files.  You can see examples in /api/user/create
@AlanaDubie @Jean-LucMartel - Mentioning you here because I forgot to mention this requirement for deploying.


[terra-clinical-data-grid] Fixed axe violation for keyboard accessibility of scrollable content

Summary
Fixes #583

This accessibility violation is also applicable to the element pass to the graph prop on terra-clinical-detail-view. This violation can be seen on any of the Detail View tests. Can we also fix this violation in terra-clinical-detail-view.
I don't necessarily think we need to set the tabIndex=0 when rendering the graph. Perhaps, we can just set the tabIndex=0 only on the tests to satisfy this rule.

@saket2403 In addition to terra-clinical-data-grid, the ItemView in terra-clinical-item-view has has this accessibility violation. You can take a look at this comparison to see the change. Can you also pull this into this PR?

Can you also pull this into this PR?

Branch Merged in ff2e485

After discussing the implications of the changes on this PR for addressing this rule introduced in axe-core-3.3.0, we decided to hold off on these changes and disable this new rule for now in terra-toolikit. We will revisit this rule once we have a better plan on how to address it. I will close this PR after I disable the rule to ensure the violations no longer appear.

Closing this and we will visit how to properly handle accessibility with scrollable content when we tackle #602.


Webstorm autocomplete + pug does not work

Is this a bug or am I missing something?

Can you provide more context? Thanks

@antfu on Webstorm autocomplete of classes does not work at all like it used to with old tailwind implementation.
I'm also using pug and I assume webstorm needs to find the tailwind classes somewhere compiled to provide autocomplete.
Is there anything like IntelliSense for visual studio code that can work with webstorm?
Do I need to do something else or am I missing an option within the plugin?
Tried with the following options that didn't make any change:
      transformCSS: 'pre',
      preflight: {
        enableAll: true
      }


Support boost approval and commissions

Checklist:

This will need to have some unit tests added to it. Also, ClaimHolderPresigned test is failing - not sure why.

Description:
Please explain the changes in this PR:
Supports https://github.com/OriginProtocol/origin-dapp/pull/491
Adds two new methods to the token API:

approveContract()
getAllowance()

Closing this in favor of #475 😅


(WIP) Improve MarketWrapper documentation

TODO:

[ ] Add "Writing a MarketWrapper" section to README

[ ] Link to Nouns example PR
[ ] Explain how to integrate with unit tests - add external contracts to repo, write deploy for external contracts, add to test cases JSON, add to MARKET_NAMES array, add external function calls

[ ] Improve NatSpec documentation on IMarketWrapper.sol
[ ] Refactor tests to move external-specific functions to their own file
[ ] Add #dev channel to PartyBid section
[ ] Link to PartyDAO Discord for questions, collaboration, reviews


Rearrange and update footer

It would look better if the NSF logo wasn't the right most feature of the footer and the footer was in general better organized.

[ ] Swap position of links and NSF footer
[ ] Change name of "services" section
[ ] Add in NSF disclaimer

For NSF disclaimer, something like this:
"Any opinions, findings, conclusions or recommendations expressed in this material are those of the developers and do not necessarily reflect the views of the National Science Foundation."


chore Rename some functions name in variant type subcolumns

Proposed changes
Issue Number: close #xxx

run buildall

run buildall

run p0


upgrade isogram test suite  to spec of 1.7.0 version

test set is replenished according to the specification

LGFM :)


Add skip test options [skip ci]

Signed-off-by: Peixin Li<EMAIL_ADDRESS>To support separate build and test in different build stages

build