Expose the github.com/celogeek/go-comic-converter/internal/epub package

Hi @celogeek.
I want to integrate go-comic-converter with one of my projects.
I've looked at the codebase and figured out that the core epub conversion logic is nicely decoupled from the CLI and configuration logic on a github.com/celogeek/go-comic-converter/internal/epub package.
The problem is that this package lies on the internal package. As stated on the feature release notes, in this case, no packages outside of the root github.com/celogeek/go-comic-converter would be able to import what's within the internal package.
I don't know what's the design decision behind doing that, but it would be good to move the github.com/celogeek/go-comic-converter/internal/epub package to something like github.com/celogeek/go-comic-converter/pkg/epub.
Although I could integrate with it using something like os/exec, by exposing the package, go-comic-converter could also integrate at the code level with other Go packages, which is way better.
A good example of what I'm trying to describe here is github.com/golang-migrate/migrate, where the core package has a CLI but also supports being embedded by other packages.
Are there any concerns about doing that? I can spin up a quick PR with it if you wish, as I'll be forking the repo to implement this change anyway.

Hi,
I usually put my code in internal, as I move it a lot, and keep only the exposed part outside.
in that case the tools that will handle the properly call to ePub package with all the available options.
I have serals sub package that could be shared by putting it outside the internal.
The only issue is when I start doing it, I need to take care to avoid doing breaking changes or force a major update.
I will see if I can share the ePub api properly, without the risk of breaking stuff later. Keeping it clean.
Working on it.

I've start a branch.
I have a lot of subpackage, which I change a bit the struct
Can you take a look and let me know ?
I will keep working to improve the result.

Sure. I'll dedicate some time to take a look at the diff. Thanks!

here: https://github.com/celogeek/go-comic-converter/pull/27
I was thinking of creating a real interface for epub, with everything to plug hooks like progress, and everything.

Hi, I have the same request as @pinheirolucas, do you still work on it ? Do you need any help to do so ?
I did the necessary changes on a fork without issues, could I submit a PR ?

Sure. I create a pr but after a while I close it. I haven't got time to work on it.
Please do. I will check.

Sorry, I deleted my previous message by accident ...
I will do a PR soon, from my understanding, only moving the packages out of the pkg/external do the trick but I could be wrong (everything seems to work fine but I lack tests to validate that)

#40

Well. Internals may move a lot while public api remain stable.
Exposing everything this way, will make any changes harder, as we want to keep the interface.
I was thinking of a configurable api that can be used by external client or a command line provided like the one we have.
Like
New().WithOption(...)
Or
New(option1, option2...)
Like
New(WithTitle('test'), WithProfile('ks'),OnProgress(func(p){...}).Write('dest')

I understand you concerns about making everything public, I will try to have a deeper understanding of how things work in the repo, do you have any idea of what you would like to expose ?
If I had to choose from the options provided maybe New(option1, option2...) is better since we could create a global Options struct composed of multiple options struct parsed using a yaml or json file or with the flags provided which could give the opportunity to have maybe some presets for different scenarios


session.userData and session.send

I set data (more > 65K) in session.userData before sending message to user,
but session.send seems doesn't work without any error messages...
I know why but how to handle this situation?

max allowed is 32K as per the documentation

ok, but how to hanlde this error?

I believe in the Node version you can observe any errors in sending messages by calling "send batch".  But in general, you should send less data.

session.userData = [big data];
session.send("here message");
session.sendBatch(function(error) {
// am I right?
})

@vinnitu it looks right, but I'll leave it to @Stevenic to confirm.

@vinnitu that's correct... You can also enable gzip compression for your ChatConnector but in general we recommend treating the data bags (especially userData) more like cookie storage.  It's not a replacement for all storage.

You are right @Stevenic because with gzipData: true I see the UX lag on messenger. its almost as if there is some decompression going on for each message


[SPARK-40796][CONNECT][FOLLOW-UP] Improve README for proto generated files in Connect Python client

What changes were proposed in this pull request?

Improve README for how to install buf dependency and then run the proto generated file script.
Improve the message for out-of-sync check script.

Why are the changes needed?

Improve developer experience either when touching Connect proto files or not touch those files but having master branch out of sync with local branch.
Does this PR introduce any user-facing change?

No
How was this patch tested?

Existing checks.

R: @zhengruifeng @HyukjinKwon
cc: @HeartSaVioR @rangadi

merged into master, thank you @amaliujia


Blog website dx l rate

Hey I add 'blog website' mini project , please review and merge it and label it as Hacktoberfest 2022.

Please go thorough README.md of the project, and create your PR again.
Thank You.


[Feature Request] Add support for "global" middlewares

As per #11, it would be nice to have the equivalent of the following (snippet of an hypothetical index.ts)
app.use('/api/database', middlewareFunction);

via some files/folder structure
Why?
Right now, here's how my index.ts looks like:
app.use('/api/database', isLogged);
app.use('/api', await router({directory: path.join(__dirname, 'src', 'routes')}));

app.use(express.static(path.join(__dirname, 'public')));
app.use('*', async (request, response) => {
	response.sendFile(path.join(__dirname, 'public', 'index.html'));
});

app.use((error: Error, request: Request, response: Response, next: NextFunction) => {
	const prefix = `[${new Date().toISOString()}] [${request.ip}] [${request.method}] [${request.url}]`;
	console.error(prefix);
	console.error(error);

	response.status(500).json({error: isProduction ? 'Internal server error' : error.message});
});

It works correctly, however, what if I rename the database folder? The middleware won't be registered anymore.
IMHO this shouldn't be happening since one of the main purpose of file routing should be hassle-free route managing.
Possible implementation
Like there is index.ts (i.e. src/routes/database/index.ts would correspond to /api/database according to my example), there could be a middleware.ts with content similar to an Handler matching all methods:
const middlewares = [
  isLogged, hasPermissions
];

export default middlewares;

I think this would be a great feature to add considering that it would and reduce a lot of repetitive code result in better DX.

Thank you for filing a feature request, @R1D3R175. A while ago, I decided against implementing such a feature, but I will reconsider this decision in the near future. Meanwhile, I encourage everyone interested in this to upvote the head issue so I can gauge the demand for this feature.

Thank you for filing a feature request, @R1D3R175. A while ago, I decided against implementing such a feature, but I will reconsider this decision in the near future. Meanwhile, I encourage everyone interested in this to upvote the head issue so I can gauge the demand for this feature.
I might favor the implementation to not create a separate middleware.js file, but rather a named export like:
// routes/api/database
...

export const get = () => {}

export const put = () => {}

export const middlewares = [
  isLogged, hasPermissions
]

But I am open for a discussion.
First of all, thank you for considering my feature request. I can see why you would prefer implementing it as a named export and, it's indeed better for seeing which middlewares are bound certain route groups. However I think we should define the "middleware bounding priority" and the design to assign such "priority"; I'll explain what I mean by using an example scenario.

Example Scenario
Suppose we have a Twitter-like app that has the following endpoints:

/api/database, interacts with the database for storing or retrieving data, so we would have /user and /post.
Frontend routes such as /post that call the database API to fetch/insert posts and /user to get information about a user.
Generic routes to handle registration and login.

In our Twitter-like app, an user has to be logged in for seeing other posts in their feed, so we would use the following middlewares to protect the interested routes: isLogged, hasPermissions.
Let's now say that a user has decided to keep their profile private, we would have to add some logic to the hasPermissions endpoint. You can see how the hasPermissions is a pretty bad design since it breaks the single responsibility principle.
Because of that, we remove the hasPermissions middleware and break it into multiple middlewares such as canViewUser, canViewPost; we apply these using the already existing syntax.
But we still have the isLogged middleware on the parent folder. In which order would the middlewares be executed?
Consideration
If we view the routes as a tree, it's quite obvious that the parent middlewares gets "bound" before the child middleware. But what if we want to make an exception?
Let's say that I have the /api/database protected by the isLogged middleware since all APIs require a user id, however we also have the /user route which handles checking if an user exists or inserting one, thus, we don't want these routes to be protected.
Conclusion
What I'm saying could be quite obvious or kinda stupid, however, IMHO these are the things that could introduce the most bugs if not well-defined beforehand.

Thank you for the insight @R1D3R175. I think it takes some more clarification for me. My idea of a named middlewares export would be that those middlewares would only apply to the method exports inside that route file, not for sibling or child routes. For example:
// routes/api/database.ts or routes/api/database/index.ts
export const get = () => {}

export const post = () => {}

export const middlewares = [isLogged, canViewDatabase]

// routes/api/database/user.ts
export const get = () => {}

export const put = [canUpdateUser, () => {}]

export const middlewares = [isLogged, canViewUser]

The named middlewares export in this concept would only apply these middlewares to the method exports defined in that route file.
So the example would be equivalent to the following snippet, where the middlewares are called in their order/priority of definition:
app.get("/api/database", isLogged, canViewDatabase, () => {})
app.post("/api/database", isLogged, canViewDatabase, () => {})

app.get("/api/database/user", isLogged, canViewUser, () => {})
app.put("/api/database/user", isLogged, canViewUser, canUpdateUser, () = {})

In this concept, the middlewares export is just a shorthand for applying middlewares to all method exports, so it's not a truly global middleware.
For a truly global middleware that also matches all its subsequent child routes, the idea of a dedicated file feels like the right way.

Sounds good to me @matthiaaas . Thanks for considering this feature request. At this point I think we got everything all settled, IMHO a good starting point could be updating the docs accordingly and see if things make sense; if they do, it's a matter of implementing the feature according to what's written in the docs (something TDD, except it's docs driven).


Fix infinite hits

Fix <InfiniteHits /> that did not work without <Pagination />
Refactor code a bit to make it more readable.
Removed attributesToHighlight from client params as they were always equal to ['*'].
Also updated transformToMeiliSearchParams to fetch attributesToHighlight from instantsearch.js  to compare it with ours.
It is also never going to be used by instantSearch as it is not a requested option in a SearchClient (see below)
export declare type SearchClient = {
    addAlgoliaAgent?: (agent: string) => void;
    search: (requests: SearchRequest[]) => Promise<{
        results: SearchResponse[];
    }>;
    searchForFacetValues?: (requests: SearchForFacetValuesRequest[]) => Promise<{
        facetHits: SearchForFacetValuesResponse[];
    }[]>;
};

bors merge


replace raise StopIteration with return pep-0479

Needed for python 3.7 compatibility

Codecov Report

Merging #2300 into master will not change coverage.
The diff coverage is 50%.

@@          Coverage Diff           @@
##           master   #2300   +/-   ##
======================================
  Coverage    79.6%   79.6%
======================================
  Files          85      85
  Lines        8847    8847
  Branches     1892    1892
======================================
  Hits         7043    7043
  Misses       1544    1544
  Partials      260     260

Impacted Files
Coverage Δ

webapp/graphite/render/hashing.py
93.39% <0%> (ø)
:arrow_up:

webapp/graphite/render/datalib.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


[FBX] Importing to .mesh files fails if the FBX contains multiple meshes

Godot version
3.3.2.stable
System information
Windows 10
Issue description
Importing an FBX mesh in Godot with meshes/storage set to "Files (.mesh)" doesn't keep the names for the meshes. The side effect of this is that it only creates one file called .mesh, so if the FBX has multiple meshes there will be missing .mesh files.

Steps to reproduce

Export or download an FBX with multiple meshes (I got mine from Mixamo)
Create a new Godot project
Import the FBX with the meshes/storage setting set to Files (.mesh)
Importer only creates a single mesh file called .mesh

Minimal reproduction project
fbx-mesh.zip

I just stumbled across this one attempting to import an asset where all models were inserted into a single FBX file, and I wanted to instance them individually.
I was able to "fix" the issue in Godot 3.4.2 in the EditorSceneImporterFBX::_generate_scene method by adding the following lines:
                        // mesh node, mesh id
                        mesh_node = mesh_data_precached->create_fbx_mesh(state, mesh_geometry, fbx_node->fbx_model, p_compress_flags);
                        if (!state.MeshNodes.has(mesh_id)) {
                            state.MeshNodes.insert(mesh_id, fbx_node);
                        }
 +
 +                      // Ensure the mesh has a name for export purposes
 +                      if (mesh_node->get_mesh()->get_name().empty())
 +                          mesh_node->get_mesh()->set_name(fbx_node->node_name);

It may have worked in my case, but I'm not sure it's the correct technical solution. It may have been better if create_fbx_mesh could have named the mesh when it was creating it, but unfortunately it's not given the 'fbx_node' object containing the name.

This is probably fixed with the new FBX importer using FBX2glTF.
You can test it in Godot 4.0 alpha 6: https://godotengine.org/article/dev-snapshot-godot-4-0-alpha-6
This new importer might also be backported for the 3.x branch eventually.
If you still find issues with these models using the new importer, we suggest opening a new issue with details about the problems in Godot 4.0 alpha 6 or later.


Old link

This topic has a link which goes here: https://technet.microsoft.com/library/3fa9c316-9dc9-4b28-9abf-43a3fce5b01d.aspx and it ends up being routed to https://docs.microsoft.com/en-us/previous-versions/dynamicscrm-2016/administering-dynamics-365/dn946903(v=crm.8)?redirectedfrom=MSDN
I think it needs to go to https://docs.microsoft.com/en-us/power-platform/admin/enable-change-tracking-control-data-synchronization

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

ID: ae183946-fb2a-1b2f-e199-273eb9a68d54
Version Independent ID: 0cf78a90-f63b-af43-8075-c1cd4e934e7d
Content: Use change tracking to synchronize data with external systems (Microsoft Dataverse) - Power Apps
Content Source: powerapps-docs/developer/data-platform/use-change-tracking-synchronize-data-external-systems.md
Service: powerapps
GitHub Login: @JimDaly
Microsoft Alias: jdaly

@JimDaly  Link updated. Will be re-published later today. Thanks


Support SvelteKit

Add your vote for SvelteKit support by clicking the 👍 emoji below.

Thanks to all the contributors for their great work on this project. I was wondering how many more votes is it gonna need before it gets worked on?

Sveltekit support will be much appreciated 😄 !!

Tight integration with SvelteKit is not currently planned. However, you can still use Contentlayer with SvelteKit.
I've done this with other frameworks that aren't officially supported. It usually looks like this:

Use a tool like concurrently to run contentlayer dev and the dev server in parallel.
Run contentlayer build prior to running the framework's build command.

I could create a working demo of a Sveltekit - Contentlayer - MDX integration with simple and little code.
For those interested here is the git repositiory: sveltekit-contentlayer-example
I hope this supports the Contentlayer project and helps to enlarge the Svelte / Contentlayer community.

Can parse md, but SvelteKit doesn't have enough support for mdx

@Ahidada

Can parse md, but SvelteKit doesn't have enough support for mdx

Quite a statement. Maybe you can elaborate what support you are missing.

yes please

I could create a working demo of a Sveltekit - Contentlayer - MDX integration with simple and little code.
For those interested here is the git repositiory: sveltekit-contentlayer-example
I hope this supports the Contentlayer project and helps to enlarge the Svelte / Contentlayer community.

Given a repository that's prepared to import/render the contentlayer content, would a Vite plugin work? All it does is invoke contentlayer build and contentlayer dev during the Vite lifecycle.
// vite.config.js
// @ts-check

import * as core from '@contentlayer/core'
import { fs, errorToString } from '@contentlayer/utils'
import { E, OT, pipe, S, T } from '@contentlayer/utils/effect'
import { sveltekit } from '@sveltejs/kit/vite'
import { defineConfig } from 'vite'

export default defineConfig({
  plugins: [
    sveltekit(),
    contentlayer(),
  ],
})

/**
 * @typedef {{
 * clearCache?: boolean
 * configPath?: string | undefined
 * verbose?: boolean
 * isDev?: boolean
 * contentDirPath?: string
 * generatedDirPath?: string
 * }} ContentlayerOptions
 */

/**
 * Contentlayer Vite plugin.
 * @param {ContentlayerOptions?} options
 * @returns {import('vite').Plugin}
 */
function contentlayer(options = null) {
  const resolvedOptions = {
    generatedDirPath: '.contentlayer',
    contentDirPath: 'content',
    clearCache: false,
    configPath: undefined,
    verbose: false,
    isDev: true,
    ...options,
  }

  /**
   * @type {ReturnType<typeof startContentlayerDevelopmentWatch>}
   */
  let contentLayerWatcher

  /**
   * @see https://github.com/contentlayerdev/contentlayer/blob/main/packages/%40contentlayer/cli/src/commands/DevCommand.ts
   */
  const startContentlayerDevelopmentWatch = async () => {
    /**
     * Promise that runs in the background while the server is running.
     * TODO: terminate gracefully when the server is stopped.
     */
    pipe(
      pipe(
        S.fromEffect(
          T.gen(function*($) {
            if (resolvedOptions.clearCache) {
              const cwd = yield* $(core.getCwd)
              const artifactsDir = core.ArtifactsDir.getDirPath({ cwd })
              yield* $(fs.rm(artifactsDir, { recursive: true, force: true }))
              yield* $(T.log('Cache cleared successfully'))
            }
          }),
        ),
        S.chain(() => core.getConfigWatch({ configPath: resolvedOptions.configPath })),
        S.tapSkipFirstRight(() =>
          T.log(`Contentlayer config change detected. Updating type definitions and data...`),
        ),
        S.tapRight((config) =>
          config.source.options.disableImportAliasWarning ? T.unit : T.fork(core.validateTsconfig),
        ),
        S.chainSwitchMapEitherRight((config) =>
          core.generateDotpkgStream({
            config,
            verbose: resolvedOptions.verbose,
            isDev: resolvedOptions.isDev,
          }),
        ),
        S.tap(E.fold((error) => T.log(errorToString(error)), core.logGenerateInfo)),
        OT.withStreamSpan('@contentlayer/cli/commands/DevCommand:stream'),
        S.runDrain,
        OT.withSpan('@contentlayer/cli/commands/DevCommand:executeSafe'),
      ),
      core.runMain({
        tracingServiceName: 'contentlayer-cli',
        verbose: resolvedOptions.verbose || process.env['CL_DEBUG'] !== undefined,
      }),
    )
  }

  /**
   * @see https://github.com/contentlayerdev/contentlayer/blob/main/packages/%40contentlayer/cli/src/commands/BuildCommand.ts
   */
  const buildContentlayer = async () => {
    return pipe(
      pipe(
        T.gen(function*($) {
          if (resolvedOptions.clearCache) {
            const cwd = yield* $(core.getCwd)
            const artifactsDir = core.ArtifactsDir.getDirPath({ cwd })
            yield* $(fs.rm(artifactsDir, { recursive: true, force: true }))
            yield* $(T.log('Cache cleared successfully'))
          }
        }),
        T.chain(() => core.getConfig({ configPath: resolvedOptions.configPath })),
        T.tap((config) =>
          config.source.options.disableImportAliasWarning ? T.unit : T.fork(core.validateTsconfig),
        ),
        T.chain((config) => core.generateDotpkg({ config, verbose: resolvedOptions.verbose })),
        T.tap(core.logGenerateInfo),
        OT.withSpan('@contentlayer/cli/commands/BuildCommand:executeSafe'),
      ),
      core.runMain({
        tracingServiceName: 'contentlayer-cli',
        verbose: resolvedOptions.verbose || process.env['CL_DEBUG'] !== undefined,
      }),
    )
  }

  return {
    name: 'vite-plugin-contentlayer',

    /**
     * Add additional directories to the Vite server's file serving list.
     */
    async config() {
      return {
        server: {
          fs: {
            allow: [resolvedOptions.contentDirPath, resolvedOptions.generatedDirPath],
          },
        },
      }
    },

    /**
     * When development server starts, start contentlayer development watch.
     */
    async configureServer() {
      contentLayerWatcher = startContentlayerDevelopmentWatch()
    },

    /**
     * When build starts, build contentlayer.
     */
    async buildStart() {
      await buildContentlayer()
    },

    /**
     * TODO: When build ends, stop the contentlayer development watch.
     */
    async buildEnd() {
      if (contentLayerWatcher !== undefined) {
        contentLayerWatcher
      }
    },
  }
}


Combined fix for Mimemagic issue

This PR combines the commits from #853 and #854.
The intent is to resolve the CI and build issues as a result of the Mimemagic package yanking version 0.3.5. See Issue #849 for more information.

This should not be merged into the master branch until all of the CI tests pass.

@user12986714 In case it wasn't clear what happened, I combined your two commits into this single PR in order to be able to see what the overall result is of both commits combined, without having to merge them into the master branch. There are still issues with the rails-tests part of the CI testing. The CircleCI testing gets further than the GitHub Action CI testing, so you'll probably want to look at both.

There appears to be an issue with our github CI config Can't connect to MySQL server on '<IP_ADDRESS>'

@@ -29,6 +29,22 @@
     raise ActionController::RoutingError, 'Not Found'
   end

+  def after_sign_in_path_for(resource_or_scope)
+    if current_user.username.nil?
+      users_username_path
+    elsif current_user.stack_exchange_account_id.nil?
+      authentication_status_path
+    else
+      stored_location = nil
+      begin
+        stored_location = stored_location_for(resource_or_scope)
+      rescue # rubocop:disable Lint/HandleExceptions
+      end
+
+      request.env['omniauth.origin'] || stored_location || root_path
+    end
+  end
+
   def redis_log(_msg)
     # redis = redis(logger: true)
     # redis.multi do |m|
@@ -128,8 +144,4 @@
   def location_storable?
     request.get? && is_navigational_format? && !devise_controller? && !request.xhr?
   end
-
-  def after_sign_in_path_for(resource)
-    stored_location_for(resource) || super
-  end
 end

Looks like this patch will fix the issues

@user12986714 If that will fix the issues, then please submit a PR which does that. You should be able to do so against the branch which is used for this PR. Alternately, you can submit a PR with all three commits and we can discard this one. My intent with creating this PR wasn't to usurp you working on this, but only to put both of your commits in one PR, so we could see if there were still issues which needed to be resolved prior to merging into the master branch.

I am not aware of the ability to open a PR against another PR (hence the
patch, which you can apply using patch (1))... How can I actually do that?
On Sunday, April 11, 2021, Makyen @.***> wrote:

@user12986714 https://github.com/user12986714 If that will fix the
issues, then please submit a PR which does that. You should be able to do
so against the branch which is used for this PR. Alternately, you can
submit a PR with all three commits and we can discard this one. My intent
with creating this PR wasn't to usurp you working on this, but only to put
both of your commits in one PR, so we could see if there were still issues
which needed to be resolved prior to merging into the master branch.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Charcoal-SE/metasmoke/pull/855#issuecomment-817459683,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APTHWWFT3VBJVMC2525KLKTTIJU5TANCNFSM42YDBUKQ
.

@user12986714 You should be able to select the branch into which you desire to merge from among any existing branch within the repository. This PR is based on just another branch, as are all PRs. In this case, the branch is "Mak-combined-fix-for-mimemagic-issue".


Contact link

Stylistic update and layout suggestion*
Proposed fix: Suggest moving "Contact" from the main header and add it to the bottom of the website such as on the bottom right of this website: https://d-rev.org/
"Contribute" can also be repeated in the website bottom header if you need another link there...

Or, if easiest, underneath "Contribute." Right now, there's duplication of content between the two.


allow overriding of model_config parameters from the YML

This should allow users to update values in the model config without having to edit the JSON.
for example for the attention_dropout for #672
model_config:
    attention_dropout: 0.01

Should we deprecate the current rope configs and move them here also?

which rope configs are you referring to?

Ah, I meant rope_scaling. Since we now expect them in the model_overide, we should add it in our config validation check, so that it doesn't break old configs and warns user of deprecation.


Proxy aggregation does not terminate if you try and terminate the task via the UI

Child processes terminate but the parent task is waiting for completable futures to complete.

Stroom no longer aggregates


Add MultiIndex class

Codecov Report
Base: 54.18% // Head: 53.44% // Decreases project coverage by -0.74% :warning:

Coverage data is based on head (d011878) compared to base (195082d).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##             master      #76      +/-   ##
============================================
- Coverage     54.18%   53.44%   -0.75%
  Complexity      414      414
============================================
  Files            95       96       +1
  Lines          1731     1755      +24
  Branches        181      184       +3
============================================
  Hits            938      938
- Misses          752      776      +24
  Partials         41       41

Impacted Files
Coverage Δ

...va/seedu/waddle/commons/core/index/MultiIndex.java
0.00% <0.00%> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Argument of type '{ position: string; }' is not assignable to parameter of type 'CSSInterpolation'

I am not sure if this is specific to tss-react or another emotion issue, but I am finding this happens with the typings
import makeStyles from '@ui/utils/makeStyles';

export default makeStyles()((theme, _params, css) => {
  const s2 = {
    position: 'absolute',
  };

  return {
    s1: {
      [`&:hover .${css(s2)}`]: {
        color: 'red'
      }
    },
  };
});

TS error:
No overload matches this call.
  Overload 1 of 2, '(template: TemplateStringsArray, ...args: CSSInterpolation[]): string', gave the following error.
    Argument of type '{ position: string; }' is not assignable to parameter of type 'TemplateStringsArray'.
      Type '{ position: string; }' is missing the following properties from type 'TemplateStringsArray': raw, length, concat, join, and 17 more.
  Overload 2 of 2, '(...args: CSSInterpolation[]): string', gave the following error.
    Argument of type '{ position: string; }' is not assignable to parameter of type 'CSSInterpolation'.
      Type '{ position: string; }' is not assignable to type 'CSSObject'.
        Types of property 'position' are incompatible.
          Type 'string' is not assignable to type 'Position | Position[]'.ts(2769)

I can work around by casting to CSSObject but its not great.

Ah yes, here you have to add 'as const' for it to work.
I should document it.


useCookie does not set cookie

Environment

Operating System: Linux
Node Version:     v18.18.0
Nuxt Version:     3.7.4
CLI Version:      3.9.0
Nitro Version:    2.6.3
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      ssr
Runtime Modules:  -
Build Modules:    -

Reproduction
This reproduction requires an external navigation, at least as far as I can tell.
So the first environment is hosted here: https://stackblitz.com/edit/github-zyetwn?file=pages%2Findex.vue
The second is hosted here: https://stackblitz.com/edit/github-lqswyc?file=app.vue
Describe the bug
Clicking the first link will cause nuxt to use useCookie, set a value to the cookie and then navigate away.
The other app will simply navigate back to a callback where the cookie value is displayed.
Interestingly, there is no cookie value stored in the browser. As far as I can tell, the external navigation is required, as it causes nuxt to stop.
I suspect Nuxt ends before the cookie had a chance to be persisted, but this suspicion has no real investigation proof.
Additional context
No response
Logs
No response

stackblitz does exhibit this behaviour, yes, but I can't reproduce locally with this code:

<template>

Check the devtools

  <ClientOnly>

{{ cookie }}

  </ClientOnly>
  <button @click="cookie = null">
    clear
  </button>
</template>

So I've spent some more time on this, and my reproduction is simply flawed, as it depends on a race condition, which does not occur locally for whatever reason.
Instead of relying on navigateTo to stop execution of Nuxt, replacing the navigation with debugger; produces the expected result. No cookie is actually persisted to the browser.
So a relatively simple workaround for this would be to actually just call await nextTick() after you update the cookie value.
Though, I'd say that maybe a watcher for the cookie isn't an ideal solution?
Would it make sense to replace the value with a computed property instead? That way persisting the cookie could be done synchronously instead of waiting for a watcher.

I think maybe await nextTick() is the best approach so you ensure this occurs before navigating away from the page. This will be relevant for a lot more utilities and I'm not sure removing the reactivity (via watch) of useCookie is the right solution here.
What do you think?

That's all good with me, but it definitely feels like unexpected behavior. Maybe not a lot of people will run into this. We noticed this when starting an OAuth2 flow and persisting the state in a ssr compatible way.
Maybe this is something we should add to the docs in the utilities affected by this?

For sure we should add this to the docs, possibly both in useCookie and in a more general point in navigateTo.
I think useCookie might be the only core nuxt composable that uses watch apart from data fetching (which I don't think anyone would expect to resolve before navigating away from the page).
We might also consider waiting for nextTick when using navigateTo to an external URL 🤔

hey @danielroe   can you explain me how to approach this problem

I agree navigateTo should probably wait for nextTick, same with anything that could lead to stopping Nuxt' execution (though I can't think of anything else right now).
I think adding it to the navigateTo composable and mentioning it in useCookie would be a good idea. If we add it to navigateTo, I think we could safely omit mentioning it in its' docs.
On a different note, I've re-read your message:

not sure removing the reactivity (via watch) of useCookie

Wouldn't my proposed solution still maintain the same reactivity as before, just removing the watcher?
I think if it's really only useCookie using the watch based reactivity, it would be well worth it to introduce a breaking change, we could maybe maintain the same options contract without actually using watch?
watch == false would return no ref at all;
watch == true, would return the computed prop (Proxy)
watch == 'shallow', might be a bit more complex though

hey @danielroe can you explain me how to approach this problem

@Bhanuteja01 This composable would need to wait for nextTick https://github.com/nuxt/nuxt/blob/1e3d989ad90e672e5bcb1e9f944b27b13fc42f3d/packages/nuxt/src/app/composables/router.ts#L111

@hendrikheil  ok
is this beginner friendly or not

I'd say yes, but I'd wait with the implementation until the final approach is decided to avoid potentially wasting your time :)

@hendrikheil Thank you for your analysis on this, which I think is good.
I think we probably want to keep watch behaviour for now, as there is also the possibility of race conditions. By waiting for Vue's nextTick, we ensure the state is correct before we then trigger updates. (Although this is normally important to do before DOM updates, I think it's also important to do before - for example - posting a message to other tabs.)
So I suspect waiting on nextTick in navigateTo is right approach (possibly only in event of external navigation to reduce surface of change). The only issue we should check is what happens if using an external navigateTo to navigate away before the DOM updates.

I think with https://github.com/nuxt/nuxt/pull/23667 we can now set the cookie synchronously in onScopeDispose if it hasn't already been set - this should ensure it is set when navigating away, but not require a nextTick awaiting in navigateTo.


Unlock-SecretStore Password parameter string type

Why does this cmdlet have a -Password parameter with the type of [string]? It goes against the AvoidUsingPlainTextForPassword PSScriptAnalyzer rule. I'd rather have users use Read-Host -AsSecureString or ConvertTo-SecureString cmdlets to generate a secure string first to use the the secure store cmdlets.
https://github.com/PowerShell/PSScriptAnalyzer/blob/master/RuleDocumentation/AvoidUsingPlainTextForPassword.md

We debated about whether to include it, as you point out it is not good practice, but eventually decided to.  We can always remove it.  Also note that by default the cmdlet always prompts for secure string.

Thanks for the input, would love to leave this open for more community input

I'm convinced.  I'll remove it for the next preview release.  We can always add it back in if someone makes a compelling reason.  But I can't think of a scenario right now where plain text password parameter is a good idea.

Fixed for preview2


SVG extension

Tiny proof of concept at https://numbas.mathcentre.ac.uk/question/share/view/f396b97d-4bc5-40d2-8565-32842dbaaaf8
An extensions providing a library of functions for creating and working with SVG elements.
We already have an HTML data type, which might as well carry SVG elements (need to check that this is OK in IE)
A data type representing a list of attributes would be good, constructed like attr(["x",1],["y",2],...)

element + [List of elements] should append the right-hand list of elements to the left-hand parent.
element*attributes should apply the given attributes to the element.
attributes1*attributes2 should combine two lists of attributes, with the rightmost ones taking precedence.

This way, you can write something like svg(50,50)+[circle(20,15,5)*fill("orange")*stroke("black",0.2)]

I think it would be very awkward to create anything other than a completely basic diagram this way, so you might as well use JavaScript.
Porting eukleides might be better.


More than one terragrunt repository managing infrastructure in one AWS account?

The problem I'm trying to solve is providing a sandbox environment to developers who are new to terraform and terragrunt, while still managing that sandbox environment through terragrunt.
Currently we have one repository for managing the infrastructure for all of the sandbox accounts. I want to keep that repository unmodified, while giving a 'playground' repository to developers who are learning. That way, if they break something, I can go back in and restore it from my repository.
My question is, will terragrunt's S3 state management of these two repositories collide with each other?

Not sure I understand the question.
Generally, when using Terragrunt, we recommend having one repo, infrastructure-modules, where all the Terraform modules are defined, and a separate repo, infrastructure-live, that deploys specific version of the modules in infrastructure-modules across your various environments. See the repos mentioned at the end of the quick start guide for examples.
If you set things up this way, the sandbox environment would just be another set of subfolders in infrastructure-live. You could point those at a standalone set of AWS accounts and a totally separate S3 bucket for remote state, so it'll have no effect whatsoever on your environments. Under the hood, developers would be using versioned modules from infrastructure-modules, so at any time, you could revert to your "official" code.

Currently we are using your recommended structure. In training new users of Terraform and Terragrunt, I would like to give them a sandbox repository in which to develop their skills at building modules and configuring said modules, without prematurely allowing access to either modules that production environments rely upon, or the configurations for our environments that are stored in our infrastructure-live repo. I would prefer that the sudden but inevitable errors require less git surgery to correct. I've done enough of that fixing my own Terraform errors.
That said, after having looked to the terraform.tfvars in each of the environment directories, it looks like the s3 state between environments is isolated by bucket name. If two Terragrunt users are modifying the same AWS account using two different state storage bucket names, then as long as they don't try to manage the same resource in two places, they should operate independently, yes?

That said, after having looked to the terraform.tfvars in each of the environment directories, it looks like the s3 state between environments is isolated by bucket name. If two Terragrunt users are modifying the same AWS account using two different state storage bucket names, then as long as they don't try to manage the same resource in two places, they should operate independently, yes?

Yup!

Closing due to inactivity


Update hadoop to 3.3.4

Update hadoop to 3.3.4

@mneethiraj Any chance to land this before release-ing Ranger 2.5.0?

@kokosing  - this update will likely not be to be included in Ranger 2.5.0 release; release-candidate #3 is already out for voting. I suggest getting this merged in master branch for 3.0.0 release; if a maintenance release is necessary, 2.5.1 release can be considered.

@kokosing - later versions of Hadoop, 3.3.5 and 3.3.6, are available for a while. Any reason to not update to the latest version?

Patch merged via RANGER-4884.

@kokosing  @mneethiraj  - Any reason for not upgrading to Hadoop 3.3.5 / 3.3.6 ?
Does this (https://issues.apache.org/jira/browse/HADOOP-18515) have potential to break ranger-kms ?

@shameersss1 There is a follow up for this https://github.com/apache/ranger/pull/370


Edge Synchronization improvement

Pull Request description
Put your PR description here instead of this sentence.

Merged in master


Hardhat Cache Updates

Update hardhat cache to match better. pnpm hardhat compile will already check for changes.

/cib


reactpwa.com - host access Error 520

Hi,  it loks like reactpwa.com throws Error 520, at least as of today...

I will check this out today at highest priority.
On Wed, Aug 11, 2021 at 11:54 PM Shyran Systems @.***>
wrote:

Hi, it loks like reactpwa.com throws Error 520, at
least as of today...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Atyantik/react-pwa/issues/204, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACWDN7YCQWQ6XTUA7DZ2GBTT4K56NANCNFSM5B7FFNHQ
.

--
Tirth Bodawala
Founder
Atyantik Technologies
w: www.atyantik.com  e: @.***

@systems-shyran, apologies for the late reply, busy with many projects. the code for add_header X-Content-Type-Options: nosniff;  was not responding properly to Cloudflare's caching mechanism. We have solved it now.


Release 0.0.1

Releases in the 0.0.x sequence are for debugging our automated release process.

oh yeah, releases can't come from forks; need to release from a branch within the organization fork


Tone.Emitter.on() not responding to .emit()?

Hi!
I'm trying to use the Tone.Emitter(), and maybe i'm not understanding how the object exactly works. What i'm trying to do is create an Tone.Emitter() instance in a class that is emitting events, and another Tone.Emitter() in another class that is listening for those events and calling a function as callback. My code looks something like this:
this.emitter = new Tone.Emitter();
this.loop = new Tone.Loop((time) => {
  this.emitter.emit('myEvent', time);
}

Then somewhere else I have
this.emitter = new Tone.Emitter();
this.emitter.on('myEvent', (time) => console.log(time));

Based on the documentation it looks like this should be working, but I don't see anything logged to the console. Maybe i'm missing something. Any help would be appreciated!

I want to work on this , can you please assign it to me ?

Just checked, and this works fine for me:
const emitter = new Emitter();
emitter.on("test", (arg) => {
    console.log('emitted', arg)
});
emitter.emit("test", 100);

Maybe the Tone.Loop is never being started?

Yes, that works, true! But what I was trying to do is have 2 different classes with individual Tone.Emitter's and let the emitters send/receive from eachother. Like so:
import { Emitter } from "tone";

const receiver = new Emitter();
receiver.on("test", (msg) => {
  console.log("emit received!", msg);
});

const emitter = new Emitter();
emitter.emit("test", "send from other Emitter");

But it seems this is not a feature that is implemented? Or maybe I'm missing something. It was not super obvious to me based on the documentation.
Anyways, in the meantime I have created a workaround, which actually works quite well so far:
// in the emitter class passing the time of that class through the event to the receiver
let event = new CustomEvent("test", { detail: { value: 1, time: time } })
window.dispatchEvent(event)

// in the receiver class using the time value
window.addEventListener("test", (event) => {
    if (event.detail.value > 0){
        // trigger some Tone process with event.detail.time
    }
});

Emitter events are just on the single Emitter, not global to all Emitters. If you're looking for a global event, i think the way you're doing it looks great!


Cannot import classes via python modules

I am experiencing a weird problem when trying to use my own custom java classes in my python program.
import jpype
import jpype.imports
from jpype.types import *

# Add my library and system objects
pype.addClassPath("target/system-objects-1.0-SNAPSHOT.jar")
jpype.startJVM()

x = org.asdf.fdsa.MyClass() # this throws an ERROR

# The following lines work
MyClass = jpype.JClass("org.asdf.fdsa.MyClass")
x = MyClass()
x.sayHello() # --> prints smt to stdout

The following error is thrown by the indicated line:
Traceback (most recent call last):
  File "jpype-test.py", line 28, in <module>
    x = org.asdf.fdsa.MyClass()
NameError: name 'org' is not defined

I would appreciate any help.

Does this work?
pype.addClassPath("target/system-objects-1.0-SNAPSHOT.jar")
jpype.startJVM()

jpype.imports.registerDomain('org')
import org
x = org.asdf.fdsa.MyClass() # this throws an ERROR

There are several options.
You can use imports to import a class you would a Python module.
import jpype
import jpype.imports
jpype.addClassPath("target/system-objects-1.0-SNAPSHOT.jar")
jpype.startJVM()

from org.asjf.fdsa import MyClass
x = MyClass()

Or directly
import jpype
jpype.addClassPath("target/system-objects-1.0-SNAPSHOT.jar")
jpype.startJVM()
x = jpype.JClass("org.asjf.fdsa.MyClass")()

Hey, thanks for the quick replies. A mixture of both of ur answers turned out to be the solution:
My original
import org.asdf.fdsa.MyClass

obviously doesn't work (wouldn't work in most python packages as can be seen by trying import datetime.datetime.now). Guess I should have figured that out on my own.
But from org.asdf.fda import MyClass worked. (thanks @Thrameos )
To get my actual code working, I had to use the trick with jpype.imports.registerDomain('mydomain') from @theHamsta (since the top-level domain in my actual code doesn't seem to be among the "default" domains for jpype. I couldn't share the actual code though because it was work-related.
So for anybody with the same problem, here is the final code that worked:
import jpype
import jpype.imports
jpype.addClassPath("target/system-objects-1.0-SNAPSHOT.jar")
jpype.startJVM()

jpype.imports.registerDomain('mydomain')

from mydomain.asdf.fdsa import MyClass

x = MyClass()

Thanks a lot for the help.
(From my side, I consider the issue closed)


[UI-001] - Create project with all dependencies

Description:
Based on the need of using node/npm for version and dependency control we need to define the project package.json file with all the needed description and the expected dependencies for development and production.

ID
Description
Comments

AC1
As a developer I should see the package.json file with all the needed definitions and all partialy expected dependencies to make the project run
-

#1 Closed this issue


Fix false URL finds

Purpose/implementation Section
What changes are being implemented in this Pull Request?
On @carriewright11 's course: https://github.com/jhudsl/Data_Management_for_Cancer_Research/runs/5790229830?check_suite_focus=true There's a chapter that discusses http but is not a url per se. My URL checker script didn't know how to deal with that, so I had to adjust here.

Aren't you glad that I make so many weird use cases!? :P


Update to Swift 4.2

Why
I wanted to use this in a Swift 4.2 project, but this was the last dependency that had no update available yet.
I figured I might open this PR even though I'm not sure if you're planning on supporting Swift 4.2 right away.
What

[x] Updated RxSwift and RxCocoa pods for Swift 4.2
[x] Migrate the source code to Swift 4.2 with the help of Xcode's migration tool
[x] Update rx-coordinator.podspec with updated versions

Hey - thanks for the help! We support Swift 4.2 in XCoordinator 1.0.


//stats now shows if you are streaming or playing a game

I did not use if() :)

This'll need to have a few bug fixes, but I'll do that now.


Create new "Numbered Headline" blueprint

Jira
http://vjira2:8080/browse/BDS-2063
Summary
Adds a new Numbered Headline variation under Blueprints + basic docs / demo support.

Details
Since this isn't a full blown component, I had to get a little creative on how to get at least something to show up in the Pattern Lab menu + get some basic schema support in place.
Thoughts? Suggestions?
How to test

Review PL docs and demos

Separate note: the numbered circle is not perfectly centered because the Figure component outputs the caption element even when one is not present. Bug in Figure not in your code, but it's noticeable. Is this something we should fix now? cc: @mikemai2awesome

@danielamorse oh you mean this bugfix for Figure? 😇

I am concerned about this changing how a Blueprint was defined previously, which is assembled with existing components and utility classes. Now we are adding schema and specific CSS. I am still not sold on the concept of Blueprints: things are hard to find in the codebase and in PL, and it's not clear how many of them are being used as is (if not being used as is, why ship them? if we don't ship some of them, where do we put them?). Due to the uncertainty of Blueprints, I don't support evolving the concept of Blueprints at the moment.
Can we add this feature to the Headline component instead? Can we follow similar conventions with how icon data is passed?

@mikemai2awesome I'd push back a little and recommend we stick with flatter (non-nested) props like numberLabel (for easier web component support) however other than that I'm fine re-working this to be a built-in option for Headline vs having this live in some limbo state.
My biggest concern is really just making sure that whatever we produce and ship is at least minimally documented.

@sghoweri sounds good. flat prop it is then.

Why not make this a full component or enhancement to Headline? Was it the time crunch (which would be understandable)? Or is this intentionally not a full component? It seems a little odd having the hybrid component/blueprint. I think in the future we do want to have "templates" or "blueprints" with an API of their own but I realize we're still figuring out where such things live and what are the standards. Let's look at this example in next dev huddle. For now, I'm fine to ship it. Thanks again 🙏

Why not make this a full component or enhancement to Headline? Was it the time crunch (which would be understandable)? Or is this intentionally not a full component? I

@danielamorse it all comes down to the time crunch + not knowing enough about the rules that govern of this new "numbered headline" addition + us not having a 100% crystal clear standard on when something is or isn't "a component".
Purely as an example, could the work in this PR verbatim be it's own package (@bolt/components-numbered-headline), even though it's mostly just re-using Headline + Flag?

It seems a little odd having the hybrid component/blueprint. I think in the future we do want to have "templates" or "blueprints" with an API of their own but I realize we're still figuring out where such things live and what are the standards. Let's look at this example in next dev huddle. For now, I'm fine to ship it. Thanks again 🙏

I'd love to chat more about this during our next Dev Huddle.
We can't always cram new features into existing components. If that means we need to revisit the whole "atomic design" vs "design systems" organization debate, so be it :).

PR was released with v2.20.0


Use PostgreSQL 14.x

Tests were failing on 15

Had to manually update the pipeline with the new secure file docker-compose.ci.build.yml


Update reviewdog to v0.17.0 to allow use of github-pr-annotations reporter

Can you please update the version of reviewdog used from 0.15.0 to 0.17.0?
My goal is to use the newly added  github-pr-annotations reporter
Thanks.

done in #70


Stat struct on Darwin out of sync

I'm using this sample code:
const std = @import("std");
const warn = @import("std").debug.warn;

pub fn main() -> %void {
    var inc_allocator = %%std.heap.IncrementingAllocator.init(10 * 1024 * 1024);
    defer inc_allocator.deinit();

    const allocator = &inc_allocator.allocator;

    var file = %%std.io.File.openRead("some-file.txt", allocator);
    defer file.close();

    warn("{}\n", file.getEndPos());
}

And comparing its output with wc some-file.txt.
Stat struct in std/c/darwin.zig is out of sync.
Currently looks like:
pub const Stat = extern struct {
    dev: u32,
    mode: u16,
    nlink: u16,
    ino: u64,
    uid: u32,
    gid: u32,
    rdev: u64,

    atim: timespec,
    mtim: timespec,
    ctim: timespec,

    size: u64,
    blocks: u64,
    blksize: u32,
    flags: u32,
    gen: u32,
    lspare: i32,
    qspare: [2]u64,

};

I'll make a C file:
// file.c
#include <sys/stat.h>

...running zig parsec file.c results in this.
The appropriate direct equivalent would seem to be:
pub const Stat = extern struct {
    dev: c_int,
    mode: c_ushort,
    nlink: c_ushort,
    ino: c_ulonglong,
    uid: c_uint,
    gid: c_uint,
    rdev: c_int,

    atim: timespec,
    mtim: timespec,
    ctim: timespec,
    btim: timespec,

    size: c_longlong,
    blocks: c_longlong,
    blksize: c_int,
    flags: c_uint,
    gen: c_uint,
    lspare: c_int,
    qspare: [2]c_longlong,

};

But this breaks my test case.
Strangely enough though, omitting the new btim: timespec member and reducing ino to anything 32 bits wide or less results in the correct output from the sample.
Admittedly, this is not a very robust test, but the behavior is perplexing; similarly occurring when I convert the c_* types to my best understaning of the direct zig equivalents:
pub const Stat = extern struct {
    dev: i32,
    mode: u16,
    nlink: u16,
    ino: i64,
    uid: u32,
    gid: u32,
    rdev: i32,

    atim: timespec,
    mtim: timespec,
    ctim: timespec,
    btim: timespec,

    size: i64,
    blocks: i64,
    blksize: i32,
    flags: u32,
    gen: u32,
    lspare: i32,
    qspare: [2]i64,

};

I'm on OSX 10.12.6.

I think the answer is in sys/stat.h.
#if !defined(_POSIX_C_SOURCE) || defined(_DARWIN_C_SOURCE)
#include <sys/_types/_ino64_t.h>
#endif /* !defined(_POSIX_C_SOURCE) || defined(_DARWIN_C_SOURCE) */

I also see
#if !defined(_POSIX_C_SOURCE) || defined(_DARWIN_C_SOURCE)
/*
 * XXX So deprecated, it would make your head spin
 *
 * The old stat structure.  In fact, this is not used by the kernel at all,
 * and should not be used by user space, and should be removed from this
 * header file entirely (along with the unused cvtstat() prototype in
 * vnode_internal.h).
 */
...

This makes me think we should try defining _POSIX_C_SOURCE when we figure out what the struct should be.
When I use zig parsec foo.c with foo.c:
#define _POSIX_C_SOURCE 201711L
#include <sys/stat.h>

now I get:
pub const struct_stat = extern struct {
    st_dev: dev_t,
    st_mode: mode_t,
    st_nlink: nlink_t,
    st_ino: __darwin_ino64_t,
    st_uid: uid_t,
    st_gid: gid_t,
    st_rdev: dev_t,
    st_atime: time_t,
    st_atimensec: c_long,
    st_mtime: time_t,
    st_mtimensec: c_long,
    st_ctime: time_t,
    st_ctimensec: c_long,
    st_birthtime: time_t,
    st_birthtimensec: c_long,
    st_size: off_t,
    st_blocks: blkcnt_t,
    st_blksize: blksize_t,
    st_flags: __uint32_t,
    st_gen: __uint32_t,
    st_lspare: __int32_t,
    st_qspare: [2]__int64_t,
};

which, when I flatten out into types that depend only on the kernel and not C, results in this change to master:
diff --git a/std/c/darwin.zig b/std/c/darwin.zig
index 7ce29b50..433463fd 100644
--- a/std/c/darwin.zig
+++ b/std/c/darwin.zig
@@ -6,26 +6,28 @@ pub const _errno = __error;

 /// Renamed to Stat to not conflict with the stat function.
 pub const Stat = extern struct {
-    dev: u32,
+    dev: i32,
     mode: u16,
     nlink: u16,
     ino: u64,
     uid: u32,
     gid: u32,
-    rdev: u64,
-
-    atim: timespec,
-    mtim: timespec,
-    ctim: timespec,
-
-    size: u64,
-    blocks: u64,
-    blksize: u32,
+    rdev: i32,
+    atime: usize,
+    atimensec: usize,
+    mtime: usize,
+    mtimensec: usize,
+    ctime: usize,
+    ctimensec: usize,
+    birthtime: usize,
+    birthtimensec: usize,
+    size: i64,
+    blocks: i64,
+    blksize: i32,
     flags: u32,
     gen: u32,
     lspare: i32,
-    qspare: [2]u64,
-
+    qspare: [2]i64,
 };

 pub const timespec = extern struct {

I suspect this will fix the problem. I'll add a std lib test and then commit this if it passes.

I added a test in the darwin-stat branch. It passes on linux, fails on darwin. I'm looking into why.

Found this rust thread explaining everything: https://github.com/rust-lang/libc/issues/414#issuecomment-251246205
Fix on the way.

super awesome, thanks!


Support "point_in_time_recovery" for AWS DynamoDB

We need the "point_in_time_recovery" function for AWS DynamoDB.
https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/PointInTimeRecovery.html

Implement point_in_time_recovery

Any idea of when this is gonna be supported?


Changed Look & Feel of the Options Form

This pull request changes the look & feel of the Options form:

Decreases the size of the dialog form
Changed location and size of controls
Added borders to dropdownlist controls

:white_check_mark: Build ServiceBusExplorer 4.2.0-borders.58.build.656 completed (commit https://github.com/paolosalvatori/ServiceBusExplorer/commit/d6a68cde21 by @paolosalvatori)

I didn't realize that I had this folder. Let me remove it.

Please look at the PR now, thanks @ErikMogensen  for the heads up!

:white_check_mark: Build ServiceBusExplorer 4.2.0-borders.59.build.659 completed (commit https://github.com/paolosalvatori/ServiceBusExplorer/commit/9e89a84590 by @paolosalvatori)

:white_check_mark: Build ServiceBusExplorer 4.2.0-borders.60.build.661 completed (commit https://github.com/paolosalvatori/ServiceBusExplorer/commit/c920af8cae by @paolosalvatori)

:white_check_mark: Build ServiceBusExplorer 4.2.0-borders.61.build.663 completed (commit https://github.com/paolosalvatori/ServiceBusExplorer/commit/efdd048940 by @paolosalvatori)

:white_check_mark: Build ServiceBusExplorer 4.2.0-borders.62.build.665 completed (commit https://github.com/paolosalvatori/ServiceBusExplorer/commit/efdd048940 by @paolosalvatori)

:white_check_mark: Build ServiceBusExplorer 4.2.0-borders.63.build.667 completed (commit https://github.com/paolosalvatori/ServiceBusExplorer/commit/e1148242ea by @paolosalvatori)

:white_check_mark: Build ServiceBusExplorer 4.2.0-borders.64.build.669 completed (commit https://github.com/paolosalvatori/ServiceBusExplorer/commit/fed25a4d25 by @paolosalvatori)

:white_check_mark: Build ServiceBusExplorer 4.2.0-borders.68.build.671 completed (commit https://github.com/paolosalvatori/ServiceBusExplorer/commit/6604fa7426 by @paolosalvatori)

Thanks @ErikMogensen I had some old files in the folder :| Try now

:white_check_mark: Build ServiceBusExplorer 4.2.0-borders.68.build.673 completed (commit https://github.com/paolosalvatori/ServiceBusExplorer/commit/fc8c403f74 by @paolosalvatori)

:white_check_mark: Build ServiceBusExplorer 4.2.0-borders.68.build.675 completed (commit https://github.com/paolosalvatori/ServiceBusExplorer/commit/1e92cc248b by @paolosalvatori)


[1.21] Neoforge: Game crashes when tool breaks

Crashlog: crash-2024-06-26_19.27.25-client.txt
Accessories: accessories-1.0.0-beta.2+1.21-neoforge.jar
Neoforge: 21.0.39
LivingEntity.class
Whenever a tool breaks, the game crashes

Very odd, will investigate such.

Seems that the naming for a invoker mixin was conflicting within the name of the method leading to it being deleted somehow which I thought not possible. Will have a fix for such shortly

Fix has been pushed to modrinth and curseforge.


TS2345: Argument of type 'LooseRequired' is not assignable to parameter of type 'SkuStepperProps'.

Vue version
3.2x
Link to minimal reproduction
https://github.com/lixiaofa/fast-plus
Steps to reproduce
pnpm build
What is expected?
no error
What is actually happening?
build error

System Info
No response
Any additional comments?
No response

Please provide a minimal runnable reproduction. We can't debug full projects.

It cannot be reproduced, but errors will indeed be reported in the project.
What could be the problem, can you discuss it？


VCD files do not display glitches and can get extremely confusing

Self-contained but not quite minimal reproducer:
repro.zip

@wanda-phi has narrowed down the issue to the two underlying causes (thanks!). These are:

Circuits that provide combinational feedback from control to status signals, when used together with testbenches that use .get() and .set(), easily cause race conditions.
The VCD files do not display glitches that arise from these race conditions.

It is much easier to tackle (2) alone so that's what we should do.

In this particular case, the race condition is:

A posedge causes a status signal to be asserted.
A testbench samples it after the posedge using get() and manipulates a control signal. (This is violating Amaranth's execution model: the testbench is not acting like a synchronous circuit.)
The change to the control signal causes the status signal to be deasserted again.
On the next posedge, the circuit acts on the deasserted value of the status signal, missing an event.


Pydantic restricted to v1

Describe the bug
@benc-db, you mentioned that dbt asked you to not require Pydantic > 2, so you decided to restrict Pydantic to v1: https://github.com/databricks/dbt-databricks/pull/843
I am a bit confused as to why it was decided to constraint Pydantic to >=1.10.0, <2 instead of just >=1.10.0 which would have met dbt request. I am also confused about the reason for dbt request, as dbt itself does not publish any dependency on Pydantic.
Based on the date and other related issues/PR, I am guessing that it might be related to issues encountered with the release of Pydantic 2.10 and maybe its impact on Airflow:

https://github.com/pydantic/pydantic/issues/10910
https://github.com/apache/airflow/pull/44284
https://github.com/pydantic/pydantic/issues/10924

However, these were promptly resolved. For example, Airflow itself requires Pydantic v2 and decided to only blacklist the version 2.10.0 of Pydantic.
Making the version 1.9.0 of dbt-databricks effectively incompatible with any project requiring Pydantic v2 seems to be fairly extreme, would it be possible to get any context to the request form dbt?
As a general rule, every project should publish only its constraints. This package has no incompatibility with Pydantic v2, and it should therefore not publish any such constraint ;) If another project has an issue with Pydantic v2, they should publish this constraint themselves to not impact more users than necessary.
This has in turned caused further problems with other packages that were forced to constrain the version of dbt-databricks: https://github.com/astronomer/astronomer-cosmos/pull/1376

The restriction to < 2 was actually to silence a bunch of warnings related to my internal usage of pydantic.  Since I couldn't enforce that pydantic >= 2, I had to use v1 syntax, which in v2 leads to a bunch of warnings.  As for why dbt asked me to allow v1, I believe it has to do with the fact that in dbt Cloud (at least in the testing environment), they install all of the adapters, and one of them requires V1.  If anyone knows how to suppress the warnings, I would appreciate it.  In the meantime, I can remove the upper bound.

Thanks a lot for the reply and loosening the restriction 😊
A bit difficult to answer your question about the warnings without more context. I see that youæ're using Ruff, have you tried https://docs.astral.sh/ruff/settings/#lint_flake8-type-checking_runtime-evaluated-base-classes:
[tool.ruff.lint.flake8-type-checking]
runtime-evaluated-base-classes = ["pydantic.BaseModel"]

For mypy, you can check out the Pydantic mypy plugin: https://docs.pydantic.dev/2.10/integrations/mypy/#configuring-the-plugin


Image Vulnerabilities

I am hoping to understand the team's timeline on a new official release that will resolve the following CVEs listed for the current version (1.1.0) of github-exporter:
▶ docker scout cves githubexporter/github-exporter:1.1.0
    i New version 1.8.0 available (installed version is 1.5.0) at https://github.com/docker/scout-cli
    ✓ SBOM of image already cached, 35 packages indexed
    ✗ Detected 3 vulnerable packages with a total of 35 vulnerabilities

## Overview

                    │             Analyzed Image
────────────────────┼─────────────────────────────────────────
  Target            │  githubexporter/github-exporter:1.1.0
    digest          │  77c7ebf3bc78
    platform        │ linux/amd64
    vulnerabilities │    2C    14H    11M     0L     8?
    size            │ 11 MB
    packages        │ 35

## Packages and Vulnerabilities

   2C    13H     7M     0L     6?  stdlib 1.19.5
<EMAIL_ADDRESS>
    ✗ CRITICAL CVE-2023-24540
      https://scout.docker.com/v/CVE-2023-24540
      Affected range : <1.19.9
      Fixed version  : 1.19.9

    ✗ CRITICAL CVE-2023-24538
      https://scout.docker.com/v/CVE-2023-24538
      Affected range : <1.19.8
      Fixed version  : 1.19.8

    ✗ HIGH CVE-2023-29403
      https://scout.docker.com/v/CVE-2023-29403
      Affected range : <1.19.10
      Fixed version  : 1.19.10

    ✗ HIGH CVE-2023-45287
      https://scout.docker.com/v/CVE-2023-45287
      Affected range : <1.20.0
      Fixed version  : 1.20.0

    ✗ HIGH CVE-2023-45283
      https://scout.docker.com/v/CVE-2023-45283
      Affected range : <1.20.11
      Fixed version  : 1.20.11

    ✗ HIGH CVE-2023-39325
      https://scout.docker.com/v/CVE-2023-39325
      Affected range : <1.20.10
      Fixed version  : 1.20.10

    ✗ HIGH CVE-2023-24537
      https://scout.docker.com/v/CVE-2023-24537
      Affected range : <1.19.8
      Fixed version  : 1.19.8

    ✗ HIGH CVE-2023-24536
      https://scout.docker.com/v/CVE-2023-24536
      Affected range : <1.19.8
      Fixed version  : 1.19.8

    ✗ HIGH CVE-2023-24534
      https://scout.docker.com/v/CVE-2023-24534
      Affected range : <1.19.8
      Fixed version  : 1.19.8

    ✗ HIGH CVE-2022-41725
      https://scout.docker.com/v/CVE-2022-41725
      Affected range : <1.19.6
      Fixed version  : 1.19.6

    ✗ HIGH CVE-2022-41724
      https://scout.docker.com/v/CVE-2022-41724
      Affected range : <1.19.6
      Fixed version  : 1.19.6

    ✗ HIGH CVE-2022-41723
      https://scout.docker.com/v/CVE-2022-41723
      Affected range : <1.19.6
      Fixed version  : 1.19.6

    ✗ HIGH CVE-2022-41722
      https://scout.docker.com/v/CVE-2022-41722
      Affected range : <1.19.6
      Fixed version  : 1.19.6

    ✗ HIGH CVE-2023-29400
      https://scout.docker.com/v/CVE-2023-29400
      Affected range : <1.19.9
      Fixed version  : 1.19.9

    ✗ HIGH CVE-2023-24539
      https://scout.docker.com/v/CVE-2023-24539
      Affected range : <1.19.9
      Fixed version  : 1.19.9

    ✗ MEDIUM CVE-2023-29406
      https://scout.docker.com/v/CVE-2023-29406
      Affected range : <1.19.11
      Fixed version  : 1.19.11

    ✗ MEDIUM CVE-2023-39319
      https://scout.docker.com/v/CVE-2023-39319
      Affected range : <1.20.8
      Fixed version  : 1.20.8

    ✗ MEDIUM CVE-2023-39318
      https://scout.docker.com/v/CVE-2023-39318
      Affected range : <1.20.8
      Fixed version  : 1.20.8

    ✗ MEDIUM CVE-2023-45284
      https://scout.docker.com/v/CVE-2023-45284
      Affected range : <1.20.11
      Fixed version  : 1.20.11

    ✗ MEDIUM CVE-2023-39326
      https://scout.docker.com/v/CVE-2023-39326
      Affected range : <1.20.12
      Fixed version  : 1.20.12

    ✗ MEDIUM CVE-2023-29409
      https://scout.docker.com/v/CVE-2023-29409
      Affected range : <1.19.12
      Fixed version  : 1.19.12

    ✗ MEDIUM CVE-2023-24532
      https://scout.docker.com/v/CVE-2023-24532
      Affected range : <1.19.7
      Fixed version  : 1.19.7

    ✗ UNSPECIFIED CVE-2024-24785
      https://scout.docker.com/v/CVE-2024-24785
      Affected range : <1.21.8
      Fixed version  : 1.21.8

    ✗ UNSPECIFIED CVE-2024-24784
      https://scout.docker.com/v/CVE-2024-24784
      Affected range : <1.21.8
      Fixed version  : 1.21.8

    ✗ UNSPECIFIED CVE-2024-24783
      https://scout.docker.com/v/CVE-2024-24783
      Affected range : <1.21.8
      Fixed version  : 1.21.8

    ✗ UNSPECIFIED CVE-2023-45290
      https://scout.docker.com/v/CVE-2023-45290
      Affected range : <1.21.8
      Fixed version  : 1.21.8

    ✗ UNSPECIFIED CVE-2023-45289
      https://scout.docker.com/v/CVE-2023-45289
      Affected range : <1.21.8
      Fixed version  : 1.21.8

    ✗ UNSPECIFIED CVE-2023-45288
      https://scout.docker.com/v/CVE-2023-45288
      Affected range : <1.21.9
      Fixed version  : 1.21.9

   0C     1H     3M     0L     2?  openssl 3.0.10-r0
pkg:apk/alpine/openssl@3.0.10-r0?os_name=alpine&os_version=3.17

    ✗ HIGH CVE-2023-5363
      https://scout.docker.com/v/CVE-2023-5363
      Affected range : <3.0.12-r0
      Fixed version  : 3.0.12-r0

    ✗ MEDIUM CVE-2023-6129
      https://scout.docker.com/v/CVE-2023-6129
      Affected range : <3.0.12-r2
      Fixed version  : 3.0.12-r2

    ✗ MEDIUM CVE-2024-0727
      https://scout.docker.com/v/CVE-2024-0727
      Affected range : <3.0.12-r4
      Fixed version  : 3.0.12-r4

    ✗ MEDIUM CVE-2023-5678
      https://scout.docker.com/v/CVE-2023-5678
      Affected range : <3.0.12-r1
      Fixed version  : 3.0.12-r1

    ✗ UNSPECIFIED CVE-2024-2511
      https://scout.docker.com/v/CVE-2024-2511
      Affected range : <3.0.12-r5
      Fixed version  : 3.0.12-r5

    ✗ UNSPECIFIED CVE-2023-6237
      https://scout.docker.com/v/CVE-2023-6237
      Affected range : <3.0.12-r3
      Fixed version  : 3.0.12-r3

   0C     0H     1M     0L  google.golang.org/protobuf 1.28.1
<EMAIL_ADDRESS>
    ✗ MEDIUM CVE-2024-24786 [Loop with Unreachable Exit Condition ('Infinite Loop')]
      https://scout.docker.com/v/CVE-2024-24786
      Affected range : <1.33.0
      Fixed version  : 1.33.0

35 vulnerabilities found in 3 packages
  UNSPECIFIED  8
  LOW          0
  MEDIUM       11
  HIGH         14
  CRITICAL     2

Thanks for the report @KyleMasterson! Security Scanning isn't something I've had time to look into since taking over the project nor have I thought of an official policy.
I've just enabled Dependabot and Daily Trivy Container scanning so hopefully I can make any critical security updates more frequently.
I've just release v1.2.0 which resolves a big chunk of the issues. Will look into resolving the others when I get a bit more time as they involve some major version upgrades.


Fix PacketOut serialization.

OpenFlow13 specify :
uint16_t actions_len; /* Size of action array in bytes. */
This commit replace current implementation where actions_lens is the
number of actions by the number of bytes for action array.
Change-Id: Ic019455f8407f684aefa1cf25808881cca60b3ea

Thank you @oqu .
Please give me time to read and review your code 🙏

I'll merge your PR with some additional modification like this https://github.com/Kmotiko/gofc/commit/b6325b1220c16a9f16e947d296262e23d1b109d6.


duckdb server example has startup issue: cannot drop entry "pg_database" because it is an internal system entry

A container (see Dockerfile below) with official python 3.11.1 and buenavista installed complains with this message when started:
Using in-memory DuckDB database
Traceback (most recent call last):
  File "/src/buenavista/examples/duckdb_server.py", line 202, in <module>
    db.execute(
duckdb.CatalogException: Catalog Error: Cannot drop entry "pg_database" because it is an internal system entry

This issue can be replicated with this Dockerfile and running docker build -t buenavista . && docker run --rm buenavista:
# syntax=docker/dockerfile:1.4
FROM docker.io/python:3.11.1

ENV TZ=Europe/Stockholm
ENV DEBIAN_FRONTEND=noninteractive
RUN ln -snf /usr/share/zoneinfo/$TZ /etc/localtime && echo $TZ > /etc/timezone

RUN apt-get update -y && apt-get install -y --no-install-recommends \
	git

WORKDIR /src

# these seem to be requirements
RUN pip install duckdb pyarrow

RUN git clone --depth=1 https://github.com/jwills/buenavista.git

WORKDIR /src/buenavista

CMD PYTHONPATH=. python3 examples/duckdb_server.py

Ah, some of my upstream changes have made their way into 0.6.1! Okay, will get it fixed up


Incomplete URL escaping

Description
Raising this as a result of migration friction. My client is migrating from ADO to GitHub using the ado2gh CLI extension. They have a project name which contains brackets, e.g. Knowledge Management (KM). When parsing this project to ado2gh the migration fails with the following error:
[17:11] [ERROR] The source repository url https://dev.azure.com/digimangos/Knowledge%20Management%20(KM)/_git/test-repo is invalid. Please ensure the source url you gave is correct and properly formatted.

If you parse in the value to ado2gh with the project name URL escaped as Knowledge Management %28KM%29 then the migration completes successfully.
Presumably the fix is to change the logic in MigrateRepoCommandHandler.cs at line 101:
  private string GetAdoRepoUrl(string org, string project, string repo) => $"https://dev.azure.com/{org}/{project}/_git/{repo}".Replace(" ", "%20");

Although more pervasive changes might be required as other commands may be affected
Reproduction Steps

In Azure create a project name containing brackets i.e. Knowledge Management (KM)
Use this project name as an input to ado2gh.
See failure:➜  ~ gh ado2gh migrate-repo --ado-org digimangos --ado-team-project "Knowledge Management (KM)" --ado-repo test-repo --github-org digimangos-work-dev --github-repo com.digimangos.bracket-test-2 --wait --ado-pat xxx --github-pat xxx --verbose
\[10:53] [INFO] You are running the latest version of the ado2gh CLI [v0.31]
[10:53] [INFO] Migrating Repo...
[10:53] [INFO] ADO ORG: digimangos
[10:53] [INFO] ADO TEAM PROJECT: Knowledge Management (KM)
[10:53] [INFO] ADO REPO: test-repo
[10:53] [INFO] GITHUB ORG: digimangos-work-dev
[10:53] [INFO] GITHUB REPO: com.digimangos.bracket-test-2
[10:53] [INFO] WAIT: true
[10:53] [INFO] ADO PAT: ***
[10:53] [INFO] GITHUB PAT: ***
[10:53] [DEBUG] HTTP POST: https://api.github.com/graphql
[10:53] [DEBUG] HTTP BODY: {"query":"query($login: String!) {organization(login: $login) { login, id, name } }","variables":{"login":"digimangos-work-dev"}}
[10:53] [DEBUG] GITHUB REQUEST ID: 262A:A783:4CC359F:4DDC105:63BD439D
[10:53] [DEBUG] RESPONSE (OK): {"data":{"organization":{"login":"digimangos-work-dev","id":"O_kgDOBkvtQA","name":"digimangos-work-dev"}}}
[10:53] [DEBUG] HTTP POST: https://api.github.com/graphql
[10:53] [DEBUG] HTTP BODY: {"query":"mutation createMigrationSource($name: String!, $url: String!, $ownerId: ID!, $type: MigrationSourceType!) { createMigrationSource(input: {name: $name, url: $url, ownerId: $ownerId, type: $type}) { migrationSource { id, name, url, type } } }","variables":{"name":"Azure DevOps Source","url":"https://dev.azure.com","ownerId":"O_kgDOBkvtQA","type":"AZURE_DEVOPS"},"operationName":"createMigrationSource"}
[10:53] [DEBUG] GITHUB REQUEST ID: 262A:A783:4CC36EC:4DDC28C:63BD439D
[10:53] [DEBUG] RESPONSE (OK): {"data":{"createMigrationSource":{"migrationSource":{"id":"MS_kgDaACRiMjcwNjc4Yy04NGVkLTRkNDQtODM5Ni1jYTZmYTQyMGY4MTc","name":"Azure DevOps Source","url":"https://dev.azure.com","type":"AZURE_DEVOPS"}}}}
[10:53] [DEBUG] HTTP POST: https://api.github.com/graphql
[10:53] [DEBUG] HTTP BODY: {"query":"\n                mutation startRepositoryMigration(\n                    $sourceId: ID!,\n                    $ownerId: ID!,\n                    $sourceRepositoryUrl: URI!,\n                    $repositoryName: String!,\n                    $continueOnError: Boolean!,\n                    $gitArchiveUrl: String,\n                    $metadataArchiveUrl: String,\n                    $accessToken: String!,\n                    $githubPat: String,\n                    $skipReleases: Boolean,\n                    $lockSource: Boolean) { \n                startRepositoryMigration(\n                    input: { \n                        sourceId: $sourceId,\n                        ownerId: $ownerId,\n                        sourceRepositoryUrl: $sourceRepositoryUrl,\n                        repositoryName: $repositoryName,\n                        continueOnError: $continueOnError,\n                        gitArchiveUrl: $gitArchiveUrl,\n                        metadataArchiveUrl: $metadataArchiveUrl,\n                        accessToken: $accessToken,\n                        githubPat: $githubPat,\n                        skipReleases: $skipReleases,\n                        lockSource: $lockSource\n                    }\n                ) {\n                    repositoryMigration {\n                        id,\n                        migrationSource {\n                            id,\n                            name,\n                            type\n                        },\n                        sourceUrl,\n                        state,\n                        failureReason\n                    }\n                  } }","variables":{"sourceId":"MS_kgDaACRiMjcwNjc4Yy04NGVkLTRkNDQtODM5Ni1jYTZmYTQyMGY4MTc","ownerId":"O_kgDOBkvtQA","sourceRepositoryUrl":"https://dev.azure.com/digimangos/Knowledge%20Management%20(KM)/_git/test-repo","repositoryName":"com.digimangos.bracket-test-2","continueOnError":true,"gitArchiveUrl":null,"metadataArchiveUrl":null,"accessToken":"***","githubPat":"***","skipReleases":false,"lockSource":false},"operationName":"startRepositoryMigration"}
[10:53] [DEBUG] GITHUB REQUEST ID: 262A:A783:4CC3F83:4DDCB17:63BD439F
[10:53] [DEBUG] RESPONSE (OK): {"data":{"startRepositoryMigration":{"repositoryMigration":{"id":"RM_kgDaACQ2ODU2OTE5MS1mM2VkLTQ5YjItYmNjZi0zY2I3MTRiMWEzMGY","migrationSource":{"id":"MS_kgDaACRiMjcwNjc4Yy04NGVkLTRkNDQtODM5Ni1jYTZmYTQyMGY4MTc","name":"Azure DevOps Source","type":"AZURE_DEVOPS"},"sourceUrl":"https://dev.azure.com/digimangos/Knowledge%20Management%20(KM)/_git/test-repo","state":"QUEUED","failureReason":""}}}}
[10:53] [DEBUG] HTTP POST: https://api.github.com/graphql
[10:53] [DEBUG] HTTP BODY: {"query":"query($id: ID!) { node(id: $id) { ... on Migration { id, sourceUrl, migrationSource { name }, state, failureReason, repositoryName } } }","variables":{"id":"RM_kgDaACQ2ODU2OTE5MS1mM2VkLTQ5YjItYmNjZi0zY2I3MTRiMWEzMGY"}}
[10:53] [DEBUG] GITHUB REQUEST ID: 262A:A783:4CC4F24:4DDDB07:63BD43A2
[10:53] [DEBUG] RESPONSE (OK): {"data":{"node":{"id":"RM_kgDaACQ2ODU2OTE5MS1mM2VkLTQ5YjItYmNjZi0zY2I3MTRiMWEzMGY","sourceUrl":"https://dev.azure.com/digimangos/Knowledge%20Management%20(KM)/_git/test-repo","migrationSource":{"name":"Azure DevOps Source"},"state":"FAILED","failureReason":"The source repository url https://dev.azure.com/digimangos/Knowledge%20Management%20(KM)/_git/test-repo is invalid. Please ensure the source url you gave is correct and properly formatted.","repositoryName":"com.digimangos.bracket-test-2"}}}
[10:53] [ERROR] Migration Failed. Migration ID: RM_kgDaACQ2ODU2OTE5MS1mM2VkLTQ5YjItYmNjZi0zY2I3MTRiMWEzMGY
[10:53] [ERROR] OctoshiftCLI.OctoshiftCliException: The source repository url https://dev.azure.com/digimangos/Knowledge%20Management%20(KM)/_git/test-repo is invalid. Please ensure the source url you gave is correct and properly formatted.
   at OctoshiftCLI.AdoToGithub.Handlers.MigrateRepoCommandHandler.Handle(MigrateRepoCommandArgs args)
   at OctoshiftCLI.Extensions.CommandExtensions.<>c__DisplayClass1_0`3.<<ConfigureCommand>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Invocation.AnonymousCommandHandler.InvokeAsync(InvocationContext )
   at System.CommandLine.Invocation.InvocationPipeline.<>c__DisplayClass4_0.<<BuildInvocationChain>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass17_0.<<UseParseErrorReporting>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass12_0.<<UseHelp>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass22_0.<<UseVersionOption>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass19_0.<<UseTypoCorrections>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<UseSuggestDirective>b__18_0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass16_0.<<UseParseDirective>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<RegisterWithDotnetSuggest>b__5_0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass8_0.<<UseExceptionHandler>b__0>d.MoveNext()

Thanks for reporting this. This definitely looks like a bug to me. We should probably use proper URL encoding functions instead of the pretty naïve "replace spaces with %20" we're doing now. I count at least 13 places in the code where we do this now that should all be updated.

Hi @dylan-smith I did have a quick look in to this with the view to make PR fixing the issue, I think several of the cases are quickly fixed since they have the parameters which can be individually encoded. For example in:
        return $"{serverUrl}/{org}/{project}/_git/{repo}".Replace(" ", "%20");

You could just escape org, project and repo as part of the string interpolation and remove the Replace at the end. However... there are several other cases which have a URL already in them. e.g in AdoClient.cs at line 104.
            var updatedUrl = url.Replace(" ", "%20");

Because obviously trying to encode at this point with the HttpUtility methods will end up encoding the colons and slashes like:
http%3a%2f%2fdev.azure.com%2fmyorg%2fmyproject%2f_git%2fKnowledge%20Management%20%28KM%29
The changes will need to be thought about more carefully to unpick where the encoding is happening (of course some of this string replacement may be duplicated because applying it to a string which has %20 already isn't currently an issue.


runtime error: index out of range [0] with length 0

Describe the bug
runtime error: index out of range [0] with length 0 pops up after initiating the first user to send a message.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
I just want to run the bot, scrape usernames then DM them
Screenshots
If applicable, add screenshots to help explain your problem.
Error output
runtime error: index out of range [0] with length 0
Desktop (please complete the following information):
Windows
Additional context
Add any other context about the problem here.

Hi @ExoticBeing888
It's fixed on the new relese v0.4.2


daisy: properly set the container tag

We assumed that the format : was valid for concourses registry-image-resource, however tag needs to be specified with the tag field in the resources configuration.

/lgtm


How to get length of router?

Version
"dependencies": {
"react": "^15.1.0",
"react-native": "^0.27.2",
"react-native-drawer": "^2.2.2",
"react-native-router-flux": "^3.30.0",
"react-redux": "^4.4.0",
"redux": "^3.3.1",
"react-native-button": "github:ide/react-native-button"
}
Expected behaviour
I tried current path and length with "currentRouter" but, got "undefined"
here is capture of "Actions" in my component

What exactly do you expect to get? The number of routes you have?
One idea I have for this is maybe keep track of the stack in redux?

I expect get size of routes or list of routes.
Do I have to stack or track by myself?

I have a tangentially related question, is there a way to get the size of the stack before we do an Actions.pop()?

In my case i want the type PUSH_OR_POP on transitions. And i need to know the size of the stack to know if the action was a pop (and how many scenes it poped) or a push of a new scene.

Same question

+1


some questions

Is there any way to delete the pixels that have been drawn?

Guess that has been solved on discord.


withdraw unsold vẫn còn available token

Fix in contract: https://github.com/InkWhale-net/contracts/commit/137556e71ba9e2fa721b794a40531805948776af#diff-fb0a0328438cd070746a86a444909ea2ca46afec46046e84d7d73a30d923fd5fR1868
Need to update abi in FE.

Update new contract address both BE and FE
@vup2p @Shinie16


Making the Azure Pipeline task names a bit more descriptive

This is based off feedback from the product team I'm working with.

awesome. thanks


Send HTTP/2 SETTINGS_TIMEOUT.

It would be helpful to debug misbehaving clients, proxies & servers if gRPC closed connection with a  SETTINGS_TIMEOUT error if it didn't receive SETTINGS ACK frame in a reasonable amount of time (see: #13061).
This is especially important for the initial SETTINGS frame, where misbehaving clients might completely ignore SETTINGS frame which arrived upon successful connection, but before client sent its own SETTINGS frame.
From RFC7540, sec. 6.5.3. Settings Synchronization:

If the sender of a SETTINGS frame does not receive an acknowledgement
within a reasonable amount of time, it MAY issue a connection error
(Section 5.4.1) of type SETTINGS_TIMEOUT.

cc @ctiller @fengli79 @louiscryan

Effectively we'll need a timer in chttp2_transport that's armed whenever we send settings, cancelled when we get the ack, and fails the connection when it expires.
Care will need to be given to ensure that we don't start sending the next settings until the timer callback is actually made.


Unable to run librarian-chef if Cheffile contains any git repo

The exception
....rbenv/versions/2.0.0-p247/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:100:in `require': unable to find a version of 'chef' to activate (Gem::LoadError)
	from /home/leo/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/librarian-chef-0.0.2/lib/librarian/chef/manifest_reader.rb:27:in `compile_manifest'
	from /home/leo/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/librarian-chef-0.0.2/lib/librarian/chef/manifest_reader.rb:21:in `read_manifest'
	from /home/leo/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/librarian-chef-0.0.2/lib/librarian/chef/source/local.rb:57:in `fetch_manifest_data'
	from /home/leo/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/librarian-chef-0.0.2/lib/librarian/chef/source/local.rb:49:in `manifest_data'
	from /home/leo/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/librarian-chef-0.0.2/lib/librarian/chef/source/local.rb:28:in `fetch_version'
	from /home/leo/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/librarian-0.1.1/lib/librarian/manifest.rb:117:in `fetch_version!'
	from /home/leo/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/librarian-0.1.1/lib/librarian/manifest.rb:109:in `fetched_version'
	from /home/leo/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/librarian-0.1.1/lib/librarian/manifest.rb:55:in `version'
	from /home/leo/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/librarian-0.1.1/lib/librarian/manifest.rb:93:in `satisfies?'
...

Gemfile:
source "http://rubygems.org"

gem "chef"
gem "knife-solo"
gem "librarian-chef"
gem "foodcritic"

Cheffile
site "http://community.opscode.com/api/v1"

cookbook "apt"
cookbook "build-essential"
cookbook "chef_handler"
cookbook "deploy_wrapper"
cookbook "dmg"
cookbook "docker"
cookbook "firewall"
cookbook "git"
cookbook "golang"
cookbook "logrotate"
cookbook "lxc"
cookbook "modules"
cookbook "ntp"
cookbook "nginx"
cookbook "nodejs"
cookbook "openssl"
cookbook "redisio"
cookbook "runit"
cookbook "ssh_known_hosts"
cookbook "sudo"
cookbook "windows"
cookbook "yum"

cookbook "mongodb",
  git: "https://github.com/sourceindex/chef-mongodb.git"
cookbook "rbenv",
  git: "https://github.com/fnichol/chef-rbenv"
cookbook "ruby_build",
  git: "https://github.com/fnichol/chef-ruby_build.git"

If i comment out the last three cookbooks, I've no problem by running librarian-chef update however if there is any of these, it just crashes.
Any idea ? Thanks !

Should this line: git: "https://github.com/fnichol/chef-rbenv" be: git: "https://github.com/fnichol/chef-rbenv.git ?


Windows 10 IoT Enterprise support?!

Hi,
this documentation refers to services for Windows 10 IoT Core explicitly. Are they valid for Windows 10 IoT Enterprise as well? To which extent?
Thank you in advance!

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

ID: b27e43d1-43a6-1cc3-8a60-8c3efa256553
Version Independent ID: 631a1234-d235-37bf-aac2-c0c25527a76b
Content: Windows 10 IoT Core Services - Windows IoT
Content Source: windows-iotcore/commercialize-your-device/IoTCoreServicesOverview.md
Product: windows-iot
GitHub Login: @saraclay
Microsoft Alias: saclayt

Windows 10 IoT Enterprise is a different product - please see this article for more information: https://docs.microsoft.com/en-us/windows/iot-core/windows-iot-enterprise


Modified code samples to support Terraform AureRM 2.0 provider

For those examples that were more complex, I tied the example to previous versions. These examples that were tied to previous versions will be updated but require more testing to ensure all breaking changes.

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

@grayzu
Microsoft authors and contributors need to make content contributions through the private repository (azure-docs-pr) so the content can be staged and validated by the current validation rules.
After you review staging and fix all validation issues, you can add the sign-off comment to let PR reviewers know that the updates are ready to be merged.
For more information, see Should I work in a private or a public repo?
If you need help getting set up to work in the private repo, see Set up Git repository locally for documentation.
Would you create a pull request in the private repo to make these updates? We'll close this PR. Let us know if you need help moving the commits in this PR.
Thank you.


Deprecate repository

Pull requests:

https://github.com/senzing-garage/entity-search-web-app-console/pull/283


Button click throws Bunit.ElementNotFoundException

Describe the bug or question
Triggering a click event on a button results in a 'Bunit.ElementNotFoundException' exception. I have a form component with an edit button, after a click on the button it then is removed from the DOM. The form then shows a cancel and submit button. I can see that the click is being handled, so I think it's being referenced after being removed from DOM.
I've made a small project to reproduce the exception: XUnitTestProject1.zip
Example:
Testing this component:
<form>
    @if (State.IsReadonly)
    {
        <button class="editbutton" @onclick="EditHandler">Edit</button>
    }
    <div>
        @ChildContent
    </div>
    @if (!State.IsReadonly)
    {
        <button class="cancelbutton">Cancel</button>
        <button class="submitbutton">Submit</button>
    }
</form>

@code {
    [CascadingParameter] public FormState State { get; set; }
    [Parameter] public RenderFragment ChildContent { get; set; }

    private void EditHandler()
    {
        State.Edit();
    }
}

With this test:
public class UnitTest1 : TestContext
{
    [Fact]
    public void Test1()
    {
        var state = new FormState();
        var cut = RenderComponent<Form>(parameters => parameters
            .AddCascadingValue(state));

        cut.Find("button.editbutton").Click();

        Assert.False(cut.Instance.State.IsReadonly);
    }
}

Results in this output:
Bunit.ElementNotFoundException
Exception of type 'Bunit.ElementNotFoundException' was thrown.
   at Bunit.ElementFactory`1.AngleSharpWrappers.IElementFactory<TElement>.GetElement() in /_/src/bunit.web/Extensions/Internal/ElementFactory.cs:line 30
   at AngleSharpWrappers.Wrapper`1.get_WrappedElement()
   at AngleSharpWrappers.ElementWrapper.HasAttribute(String name)
   at Bunit.GeneralEventDispatchExtensions.TriggerEventAsync(IElement element, String eventName, EventArgs eventArgs) in /_/src/bunit.web/EventDispatchExtensions/GeneralEventDispatchExtensions.cs:line 49
   at Bunit.MouseEventDispatchExtensions.ClickAsync(IElement element, MouseEventArgs eventArgs) in /_/src/bunit.web/EventDispatchExtensions/MouseEventDispatchExtensions.cs:line 304
   at Bunit.MouseEventDispatchExtensions.Click(IElement element, Int64 detail, Double screenX, Double screenY, Double clientX, Double clientY, Int64 button, Int64 buttons, Boolean ctrlKey, Boolean shiftKey, Boolean altKey, Boolean metaKey, String type) in /_/src/bunit.web/EventDispatchExtensions/MouseEventDispatchExtensions.cs:line 286
   at XUnitTestProject1.UnitTest1.Test1

Expected behavior:
Click of the button should work without an error. As a workaround I now use cut.FindAll("button.editbutton")[0].Click();
Version info:

Library version: v1.0.0-beta-11

Ohh my.. two in one day. Thanks for reporting.

I figured out the root cause and there is a fix on the way to the nightly channel now. I really appreciate the effort you put in to creating small repro samples. It makes my bug finding much easier. Thanks again!

Sure no problem!


Analyze and tree shaking not working

The package.json analyze command is not working:

Also treeshaking is not working:

Analyze is working - just wasn't using the documented command: yarn analyze public-api --function=graphql


feat(agrement): add agrement informations on organisme, update datefn…

… to dayjs

:tada: This PR is included in version 1.10.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Fix bold formatting

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

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


Improve animation documentation

Context
F3D doc has a short paragraph about animation: https://f3d.app/doc/user/USAGE.html#animations
While informative, it doesn't convey the full complexity of interacting with animation in F3D and animations in 3D formats in general.
Let's expand this doc in its own page
Suggested solution

Add a dedicated markdown file to cover how are animations defined in 3D models and how to interact with them in F3D
Move the short paragraph there as well
Add links wherever needed

Skills

Markdown

discussed here initially: #1242

@kathleenhang wanna take this one ?

@kathleenhang wanna take this one ?

Hi Mathieu, sure thing! Let me know if there are any best practices I should know about for writing F3D documentation. Otherwise, I will go ahead and add my notes as I see best fit !

For now animation is just a single paragraph.
I we want to expand this doc, we may be better adding a dedicated .md file for it, which means it should be listed in the index.


Create script for testing cloud functions

We decided to use following structure

Input json file that represents test that should be run against Cloud Functions:

    [
        {
            "name": "test example 1", # OPTIONAL
            "type": "EXACT_MATCH", # OPTIONAL (DEFAULT = EXACT_MATCH, OPTIONS = [EXACT_MATCH])
            "cf_package": "<CLOUD FUNCTIONS PACKAGE NAME>", # OPTIONAL (could be provided directly to script, at least one has to be specified, test level overrides global script one)
            "cf_function": "<CLOUD FUNCTIONS SPECIFIC FUNCTION TO BE TESTED>", # --||--
            "input": <OBJECT> | <@PATH/TO/FILE>, # payload to be send to CF (could be specified as a relative or absolute path to the file that contains json file, e.g. "input"<EMAIL_ADDRESS>            "outputExpected": <OBJECT> | <@PATH/TO/FILE>, # expected payload to be return from CF (--||--)
        },
        {
            "name": "test example 2",
            ...
              rest of the test definition
            ...
        }
    ]

Output that extends input json file by results from CFs and evaluation.:

    [
        {
            "name": "test example 1",
            ...
              rest of the input test definition
            ...
            "outputReturned": <OBJECT>, # returned payload from CF
            "result": <0 - test passed, 1 - test failed>
            "diff": <OBJECT> # if test passed then "diff" is Null, else contains object that represents differences
        }
    ]

Merged. Connected with #299


[Storage] [DataMovement] Fix to send directory storage resource when listing blobs; Tests for Blob to Share Directory

Added tests for Block Blob Directory to Share Directory Tests
Added tests for Page Blob Directory to Share Directory Tests
Added tests for Append Blob Directory to Share Directory Tests
Added fix to BlobStorageResourceContainer.GetStorageResources where it was not sending back the directory names

This is because Blobs is a flat namespace while the rest of the storage resource types (e.g. local, share files) are hierarchical and will actually return the directory names

Added unit tests for testing directory name discovery in BlobStorageResourceContainer.GetStorageResources

API change check
API changes are not detected in this pull request.

/azp run net - storage - tests

/azp run net - storage - tests


Advertise mocha test adapter extension

As me @tomaciazek and @priyamsahoo we are already using this extension to run and debug tests on ALS project, it makes
sense to list it inside recommendations. That is not affecting any users.

are already using this extension to run and debug tests on ALS project

Could you convert this into something that would be informative in a Git commit message?